Hmm... It may be a unique and creative invention, Brain, but do you really think edible spellbooks will catch on?
Edit: According to testing, the GroupIndex is not correctly imported; fixing it put the spellbook in the correct tab. Other problematic areas may be: drawOrder, playerTextureArchive, playerTextureRecord, and currentVariant, which did not match the values for a spellbook created by Daggerfall Unity.
In addition, no spells were imported, but that is probably a known bug.
Build #132/Windows 10: After importing a classic save, the spellbook has moved to the Ingredients tab [RESOLVED]
-
- Posts: 833
- Joined: Mon Nov 30, 2015 6:32 pm
Build #132/Windows 10: After importing a classic save, the spellbook has moved to the Ingredients tab [RESOLVED]
Previous experience tells me it's very easy to misunderstand the tone, intent, or meaning of what I've posted. If you have questions, ask.
- Interkarma
- Posts: 7247
- Joined: Sun Mar 22, 2015 1:51 am
Re: Build #132/Windows 10: After importing a classic save, the spellbook has moved to the Ingredients tab in the invento
Thanks for report. If a spellbook was incorrectly instantiated from classic save, this will be nuked and replaced with a proper spellbook on next load. Loading spellbook from classic save was using template index 0 (ruby) instead of the correct template.
Importing player spells from classic hasn't been implemented yet, but this is ready to do any time.
Importing player spells from classic hasn't been implemented yet, but this is ready to do any time.