any one have a max race fix [Archive] - ForumsHQ

[the crazy animal]

I was trying to create more races with ljnedit on wg3.20nt mmudv1.11g ran into a problem.

Steps I took:

1. removed wccupda2.dat

2. Opened up the editor and created the new race #14 basic copy of a humman with a new name.

3. brought up wg and let mmud created a new partial wccupda2.dat

4. shut down wg and then used ljnedit to compile a new wccupda2.dat containing the new edits.

5. launched wg and entered the majormud and noticed the new race edit was there.

6. typed the command: sys edit race 14 and it worked I was now the new race.

7. exited the realm to do a retrain and fix my the stats before finishing the edits on the new race.

Problem:

upon entered the realm again it sent me to the stat trainer like expected but, it had changed me from the new race #14 to a half-ogre.

The same thing happened when I tryed to make a new class.

Anyone have a fix for this?

Thanks,

TCA

[synopsism]

Hey I am having the SAME damned problem with the same system running, except, I haven't added new races yet, just changed the old ones, and its saves my char, except when I log back on I get retrained as a half-ogre! Hahah, someone please help me out here...

Thanx~

SyN

[War Hawk]

need a different crack for yer 1.11g then....

[Panterra X]

Not a clue what the problem could be.. Make sure you have the good dll, if you get a corrupted database message you dont. My advice is:

1> Edit what u want in nightmare, ljn, whatever...

2> Do not bring server back up before creating a db update!! If you want to test your edits before you compile just rename your old update wccupda2.bak. If you do not either remove or rename the current update all your changes will be lost.

3> Fire up the server... When you do this after renaming your original update, majormud will create a blank one when it starts up (wccupda2.dat). At this point you can log in and test all your edits. If everything is the way you like it, shut down wg. If not go back to #1

4> With the server down (and fresh update file made) use ljn to compile your new database update.

5> Fire up the server, wait for map update to complete and test your edits... Everything should be as you made it.

One more note about running majormud without a database update (wccupda2.dat) : dont do it... always use a update file that contains everything in your realm.. no partials.. if you do use a partial or no update your game will not operate properly.

[dxpac666]

Everybody always makes things so complicated. delete the wccupda2.dat, make your edits, run the database recovery in wccmmutl, startup the system. worked for me. always run the recovery before starting up the board after putting in new edits. I couldn't possibly tell ya why, just that it works better for the edits from experience, and that's what I was told to do when I had problems getting my edits to stick.

[Panterra X]

only problem with doing it that way dxpac is you didnt create a new database update... without it the game isnt going to work right.. ya it will come up but no items or shops will regen.. it is that complicated...

[dxpac666]

I never created one, but I have one, I must be missing something here... I didn't really have much problem at all. Oh well, I'm not a god at this... hell if I deleted everything and started from scratch my board would probably never come back up

[Atma]

Quote (dxpac666 @ June 17 2002,03:34)I never created one, but I have one, I must be missing something here... I didn't really have much problem at all. *Oh well, I'm not a god at this... hell if I deleted everything and started from scratch my board would probably never come back up *[/quote]

Actually, the cracks I've seen all re-create wccupda2.dat. But it's only about 24K. A real wccupda2.dat is well over 50 megs. So just because you have the file doesn't mean it's a real, working version. In fact, I'm positive yours isn't if only because that placed items never regen.

[Panterra X]

its not the crack its the game routine.. just creates a blank database which u should use when compiling new updates with ljn. i recommend never compiling on top of a full database... when it comes to btrieve you are always better safe than sorry..

[LordSoth]

I never had any luck recompiling over the full update file, I always had to compile over a blank update file to get things to stick.