Archtype - changing caster types

[Muspellsheimr]

I am looking for a way to change a class from a prepared caster to a spontaneous caster, etc through archtypes. There does not appear to be an interface option for this, so I have been trying an eval script of

First / 500

perform hero.delete[CasterType.MemBook]
perform hero.assign[CasterType.SpontBook]

This does not appear to work (though does not return any error messages), so either the tags are wrong and I have no idea what to change them to, or the archtype system does not currently support this change. I do not believe it to be a priority issue, as I have tried running it at First, Post-Levels, Post-Attributes, and Final Phase with no luck.

Additionally, even if the tag replacement is a success, I am uncertain how the system will handle differences in spells known/prepared & spells per day.

Suggestions or fixes?

 

[ShadowChemosh]

You have to change the tags on the "Class" not the hero.

perform linkage[varies].delete[CasterType.MemBook]
perform linkage[varies].assign[CasterType.SpontBook]

I didn't actually test anything else so I assume you have the right tags to change and just added the linkage[varies] part. linkage[varies] is how the Archetype transitions from itself to the class its attached too.

 

[Muspellsheimr]

Running at Post-Levels (500 or 10500), on the class tab I get the usual notice of 'Spells must be added to your Spellbook before you can prepare them', with the spellbook icon available. As soon as I add any spells to said spellbook, the notice changes to 'No more spells can be prepared.' The 'spells per day' segment under the spellbook icon displays correctly, but immediately changes to redtext 'none!' for any spell level I try to prepare spells for, along with the usual redtext 'Excess level X spells' in the preparation window.

Using 'SpontKnow' (sorcerer/bard/etc) in place of 'SpontBook' (arcanist) retains the spellbook, and adds every spell in the spellbook to the list of 'spells known'. Apart from the spellbook, it gives the 'No more spells can be learned' notice, which I assume could be fixed by adding spells known through the archetype interface, but have not yet tested.

This shows me I am using the correct tags, and timing appears to also be correct, but Hero Lab is not correctly pulling and resigning the CasterType tags.

If anyone else wants to test it, I was using an archetype for the Magus class. I have not tried to change a spontaneous caster into a prepared caster. I also have not tried running the delete & assign tags in two separate eval scripts. My current assumption is that Hero Lab does not support this; if anyone can find a way to make it work, I would appreciate knowing how.


Even if we can get this to work, the (possible) issue of discrepancies between spells known, spells prepared, & spells per day remains.

 

[ShadowChemosh]

Even if we can get this to work, the (possible) issue of discrepancies between spells known, spells prepared, & spells per day remains.

Well I know this can work but I don't have allot time to look into it last night. For the spells stuff you will need to setup the Prepared/Known spells stuff on the archetype so that info gets pushed to the class. Its going to take a few small steps to get this to work. Plus this sounds exactly like an archetype someone already did for the magus....

If this is the Cabalist archetype I would advise looking at the existing thread about it.

 

[Muspellsheimr]

I did not know that existed (archetype or thread), thank you. It did not fix the issue entirely, but it did help me get much closer, and will undoubtedly prove useful in the future. It also helps that I am not nearly as tired as I was last night as well

Now I just need to figure out a solution to simple interface issues (still giving me the arrows to prepare a single spell multiple times). If you know what tag to delete to remove that, without also removing the spellbook, that would be greatly appreciated.

Edit: Additional minor interface issues - if there is an error (such as preparing to many spells, or not enough), the error will be marked in red normally on the class tab, but the tab title and validation alert remain neutral.