I am attempting to follow the FAQ's instructions to set up the server vault of a 1.69 server for migration to EE, but am having difficulty getting it to actually copy over old vaults to new as described, and would appreciate any insight or assistance. We have:
- Created an "oldservervault.2da" following the guidelines in the FAQ and Bioware's 2da spec, and placed it in the server's override folder
- Copied the 1.69 server vault to the new server's data folder alongside the new, and named the folder "oldservervault"
- Had testers (myself included) copy their 1.69 nwncdkey.ini file into their /Documents/Neverwinter Nights folder alongside the EE cdkey.ini.
- Verified the public CD key and player name pairs in oldservervault.2da match testers' nwncdkey.ini
- Had testers try logging into the server
Something appears to be missing, because characters are not transferred and do not become selectable. I verified that the 2da is readable by the server, with a test script that writes the contents out to the log. I have tried both creating the 2da manually, and using a script to generate it from stored player name/CD key pairs. The EE servervault directory is empty, and the 1.69 "oldservervault" directory contains the old server vault, with the characters for every tester.
There is a slight pause on login before "New Character" becomes clickable, as if the server were indeed checking something, but nothing comes of it.
Server vault by player name and sticky player names are both disabled (enabling them did not work, either).
The question, then, is what am I missing? Is there some other .ini setting that must be set?
Additionally, the FAQ mentions that "...we will also provide (if the user has moved their nwncdkey.ini into their ~/nwn folder) the 1.69 key to the server, at startup, along with the player’s name." Is there a way to access the 1.69 key via scripting, or does this only happen behind the scenes, so to speak?