Just wondering if we screwed the pooch

[Lordlemur]

Today was the day.

Upgraded from 6.2 to the most recent build of 6.4. In an attempt to maintain the server's customized content the install was kinda peicemeal over the old install. It is my understanding that the guy who actully did the upgrade configured all the files correctly.

The server finally loads up with it's customary (ie we haven't been able to shake them) Opcode.conf errors. The world loads up and the zones seem to stay asleep. After several attempts we got a zone to wake up. However there are no NPCs of any kind. The doors work so we dont' think the issue is Maps. The game allows for search and summon of items. The game correctly displays items already on charcters. The zones will not talk to eachother and zoning itself isn't working either by zoneline or by #Zone. Further GM spawned NPCs generate an error that is something very close to:


Error loading NPCs from Database. Bad query #1054 unknown colum NPC_types.str in feild list.

I took a quick tour of the wikki and was wondering if the this error means that we have fubared the database and if there is anyway to patch it back up.

Thanks for you time and input.

-Lemur
This error is raised anytime an npc comes into sight.

[Doodman]

Look in the changelog, there should be a set of alter table statements in there to add the missing columns to your db.

[jimbabwe]

yeah, that would be the answer. All of the DB modifications made throughout the 6.4 version are in the changelog.txt(with your copy of 6.4 you downloaded, and on the download page). They are also all in the npc_pet_zone_fix.sql file. Just open it up and copy what you like(I would be wary of just sourcing it in as it may comprimise your db if you have custom pets). The reason you can't zone is becuase you didn't add the flag info to the character and zone tables. The reason the npcs don't show up is because you haven't added their ability stats data(i.e. strength, wisdom, etc.) I would backup my database before making sweeping changes like this though.

mysqldump.exe -u LOGINHERE -pPASSWORDHERE DBNAMEHERE > backup.sql

then you can just source it in later if you break it.

I'm generally in #support if you have any more questions.

[Lordlemur]

Thanks alot i'll give it a spin.

[gottasummer]

the peq forums also have a topic on what to do in detail if you do not understand the changelog.