ok.
just so i'm seeing this in the correct light, i perceive the issues are this:
(and chime in if i got it wrong)
1) at some point between 0.6.2 and titanium, something "possibly" changed in death handling on the client.
2) all of the old timers have their "golden" 0.6.2 frozen clients which work fine.
3) at some point, a line was drawn in the sand and titanium compatability was stated as the goal to prevent the constant chase with Sony.
4) there is a reticence or hesitation to fix the "death in bind zone" bug because it might invalidate the 0.6.2 version which eqemu doesnt "officially" support.
5) someone might be working on this besides me, but they havent chimed in yet.
6) my limited knowledge of the eqemu has brought me upto a brick wall.
so, barring anyone stating otherwise on the above points, does anyone want to help me out in fixing this. i chased it a decent way down. from what i can see, the disconnect happens sometime AFTER the ->Death() method returns. i know this because the toon's coords are correct (at bind point) when they respawn after the LD. i'm not an assembler whiz so disassembling the client (which could be considered illegal, i'm not sure on the specifics of that) is technically not an option atm, so i'm not sure where to go from here. there appear to be a few people who are adept at eq packet analysis and are knowledgeable of the underpinnings of the client/server relationship. do any of these people want to help me find a fix for this. i know you all have your pet projects and this is a low priority if you have the magical 0.6.2 client, but i'm sure i can fix it, if i can get a little hand holding. whether we migrate it into the CVS or put it on a branch, i dont care. i just want my server to work with titanium since thats the "communicated" line in the sand.
== sfisque
|
Threaded Mode
