How to Migrate 1.69 Server Vault to 74
Grizzled_Dwarflord
Member Posts: 168
It was mentioned in the EE Readme that the instructions could be found on the Beamdog Forums, but I've searched high and low and can't find nary a mention of it. Does anyone have some insight on how to transfer the servervaults from 1.69 to 74 (EE)? Thank ye.
1
Comments
We’ll see what we can do regarding publishing instructions on our forum about transferring servervaults from 1.69 to Neverwinter Nights: Enhanced Edition.
http://blog.beamdog.com/2018/05/may-18-livestream-recap.html
Not sure where to find everyone's public cdkeys if they haven't logged in, or how to make that transfer if they already did. The instructions I did find are a little vague and somewhat confusing. People like me need are old and dense and need a step by step approach. And trying to do it manually is cumbersome when there are hundreds of player names in the old server vault.
P
Anyways I had posted this at a 1.69 server forum I play that is hesitant to upgrade to EE because of heavily modded/scripted server (dev there thinks would be a major undertaking) so the server is going to wait some. Anyways here's one item I found:
The server admin copies their 1.69 servervault to the new NWN:EE user directory ~/nwn/oldservervault.
The server admin creates the “oldservervault.2da” file in ~/nwn/override that contains the player ID / CD Key pairs of their 1.69 users (such as the following):
2DA V2.0
Player CDKey169
0 trilobyte USVE763A
1 trinketpony UCDEFGHJ
2 trottingkrip URERLADE
When a client logs in to a server, we will provide you with the public NWN:EE CD key. But, 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.
When nwserver/NWN:EE sees a user log in with a new CD Key (and has no characters built), but matches the player name in the oldservervault list, we will look at their 1.69 Key and verify that it is the same as the one that was passed in. If they are the same, we will copy the files from oldservervault/trottingkrip to servervault/(NWN:EE CDKey), and then disallow those files to be copied ever again.
Example of how this works. Trottingkrip used your server extensively before NWN:EE to create Deekin’s cousin Beekin (trottingkrip is terrible at naming characters), and now you’re running a NWN:EE server alongside the 1.69 server to allow people to migrate as they see fit.
So, trottingkrip logs in to the NWN:EE server (which he can see from the in-game server browser that accesses (yet-to-be-determined-URL-for-master-server). His NWN:EE public CD Key is UKJKHDWE, and 1.69 public CD Key: URERLADE.
We examine the folders:
~/nwn/servervault/UKJKHDWE has no characters.
But there is a character here:
~/nwn/oldservervault/trottingkrip/Beekin.bic
Since trottingkrip is the player’s name, and they’ve given their 1.69 public CD Key, nwserver can copy the .bic characters from oldservervault/trottingkrip to servervault/UKJKHDWE, and then changing the file extension of the oldservervault characters to ensure they can’t be automatically copied again (but we leave the files there, just in case you need to restore a specific user’s copy ability).
~/nwn/servervault/UKJKHDWE/Beekin.bic
~/nwn/oldservervault/trottingkrip/Beekin.xbc
Anyways he decided to start with a fresh/wiped vault (thus removing above step) all the legacy players (5 maybe) agreed but I really wanted my vault back because of many reasons...the new host said no problemo,,,, now I am not sure but I think he just took my archived vault folder and copied to the new vault-not sure though- but I have my old vault back now and happy...so if you don't have like a gazillion players wanting their vault back at once, and think this "manual" method might work for you, I could axe the host exactly what he did for clarification.
this will cause each login vault to populate the EE vault and give access to all characters no matter which login you choose to use
hope thats dwarfy enough
@Chokra_Broodslayer @Sarmanos @Grizzled_Dwarflord @PhannSilverthorn
its all done by each player