So what can I do to fix it? Wait for the final 0.5.3 version to be released?
Zoning worked OK in previous EQEmu versions with most zone points. The current problem isn't that you can't zone, but that you get sent to the wrong
destination. This appears to happen both with hard-coded zone points and those stored
in the EQEmu DB.
From reading the post it sounds like one of the opcodes relating to zoning has changed in the
EQ client, and this is what's causing the mix-up problem.
|