I was using EQEmu-0.7.0-989, so I rolled it back to EQEmu-0.7.0-988. It didn't fix the problem, but it was an excellent suggestion.
I'm sure there is nothing wong with the actual ax_peq database. As I mentioned privately, I wasn't able to do a fresh install of the db so I restored over my current database. I'm guessing that's where things went wonky. (The problem is usually 18 inches between the monitor and the chair.)
What table(s) in the db dictate movement? I'm guessing it's zone_points, though that might just be the waypoints. I have my old database backed up, along with the SQL files from the recently-released developer version of the PEQ db. I could use one of those to overwrite the movement table(s). Or do the maps dictate movement? I haven't changed my maps at all, and movement with the old database worked perfectly.
I'm also going to go back through the previous changelogs and see if there's something I need to add. I'm not sure that will solve the problem, as everything else works perfectly other than the insane movement, but it's worth a shot.
|
Threaded Mode
