Problems after upgrading from June to current release

[gnode]

Originally Posted by cavedude

Easily done. First, get yourself the Rev 233 update: http://www.projecteq.net/phpBB2/viewtopic.php?t=4612 You're only using this to update your db, don't worry about quests or anything. The 1110a DB is very old, so that might be why you are having trouble. This assume you have not changed your db name, user, or password. If you have, then the update will fail as it depends on the settings the original installer provided. You will know if it failed if the DOS window that sources the DB doesn't stay up for at least a minute or so.

From there, grab the newest PEQ CVS. Source drop_system.sql, then source in the gz file after you unpack it. Go into the updates folder and run EVERY update from 233 up. So, start at Rev247 and go through Rev294. DO NOT skip right to the end, or run any other updates before 247. Also, don't source any sql from the EQEmu SVN, including from the changelog. Everything you need is handled by PEQ CVS.

Then, grab the newest quests from PEQ Quests CVS, and the newest server build from the EQEmu SVN and you should be set.

While all of your character data will be safe, your content will be lost. There is no way to preserve that other than keeping a sql record of every change you make and source it after you resource the content. PEQ makes so many changes to its database daily that there is no way we can offer individual table changes.

Thanks I will give it a try. I am going to try it exactly that way first to see if I can get it running. If so, I am going to alter my original tables mentioned above up to the current schema and bring them in to try to skip on content changes. We aren't going beyond PoP and I did a lot of work to restore PoM back to original. Unless, do you know if PoM has a separate spawn table now? I wonder how many of my customizations might be standard by now..

[cavedude]

PoM is by the default the original version as best as I could get it. It's a spawn_condition now, so the default setting of 1 is for PoM 1.0, and changing it to 2 switches the spawns to version 2.0.

[gnode]

Originally Posted by cavedude

PoM is by the default the original version as best as I could get it. It's a spawn_condition now, so the default setting of 1 is for PoM 1.0, and changing it to 2 switches the spawns to version 2.0.

Hmm... awesome. The only other really involved change I made was cleaning up airplane's spawn times and loot tables. Perhaps I should redo that on the new version and submit it back to you guys if needed.

I also made a quest that upgrades people's kunark and old planar armor up to low-tier velious specs. I can live without that given the stage we are in. But my only concern with that is all the old item ids floating around. Many of those items are in the 1400-1500 range and used by some people still...

What guidelines do you have regarding item ids? If I were to change all of these IDs to something that won't interfere with the peq db, what number range should I use?

It sounds like a lot of the big "fixes" I put in are standard now. I may just have to re-import a minority of my changes and clean up inventory.

[cavedude]

Sure, any work you do on airplane or any other zone submit to me on the PEQ forums. If it's good, I'll merge it I never turn good work away.

The item IDs are Sony's so I don't handle the ranges at all. Because of that, I can't give you IDs that I can say with certainty won't be taken when I do the 13th floor dump again.

[gnode]

Originally Posted by cavedude

Sure, any work you do on airplane or any other zone submit to me on the PEQ forums. If it's good, I'll merge it I never turn good work away.

The item IDs are Sony's so I don't handle the ranges at all. Because of that, I can't give you IDs that I can say with certainty won't be taken when I do the 13th floor dump again.

So really, with any luck, a lot of my items may not even be harmed if I re-insert it back in.