Reply to thread

Message

<blockquote data-quote="elrichwizard" data-source="post: 317429" data-attributes="member: 1946">Cergorach:I am woking on a module to alter the db programatically.&nbsp; I should be done tonight or tomorow.&nbsp; I will send it to you as soon as I have it ready.I would love a copy of the decompile.&nbsp; I think it violates the licence to alter the code and use it, but I would guess Fluid would not mind any suggestions we can come up with from studying the code.shadoe:I tried that approach.&nbsp; Unfortunately, when you do this you end up needing the prerequisites for all of the PrCs to to add a level and get all of the abilities of all of the PrC when you do take the level.The Guid is the field that the front end uses to join all of the data from the info class... tables.&nbsp; If you use the same Guid multilple times, you just end up with one gian PrC that combines them all.&nbsp; This is why it is a shame that Fluid used the Guid to activate this feature in the front end.&nbsp; They may have a reason that I don't know about, but if they included another Y/N field for +1 caster level in the info class table and used that instead of the Guid, it would make all of our lives a LOT easier.Eric Noah:Any chance on asking Fluid to add a +1CasterLevel (Y/N) field to &quot;info Class&quot;? and using that instead of Guid to activate this feature in the front end/calculation machine?</blockquote>

[QUOTE="elrichwizard, post: 317429, member: 1946"] Cergorach: I am woking on a module to alter the db programatically. I should be done tonight or tomorow. I will send it to you as soon as I have it ready. I would love a copy of the decompile. I think it violates the licence to alter the code and use it, but I would guess Fluid would not mind any suggestions we can come up with from studying the code. shadoe: I tried that approach. Unfortunately, when you do this you end up needing the prerequisites for all of the PrCs to to add a level and get all of the abilities of all of the PrC when you do take the level. The Guid is the field that the front end uses to join all of the data from the info class... tables. If you use the same Guid multilple times, you just end up with one gian PrC that combines them all. This is why it is a shame that Fluid used the Guid to activate this feature in the front end. They may have a reason that I don't know about, but if they included another Y/N field for +1 caster level in the info class table and used that instead of the Guid, it would make all of our lives a LOT easier. Eric Noah: Any chance on asking Fluid to add a +1CasterLevel (Y/N) field to "info Class"? and using that instead of Guid to activate this feature in the front end/calculation machine? [/QUOTE]

Verification