Starting work on Seeds of Destruction

[KLS]

Ah well we're fairly good at keeping up with live esp with the packet collector working as well as it does. Just more work for us to keep supporting versions as they update them but no big deal.

[gibroni]

doesnt seem to have broken anything. i went ahead and patched it up on steam and made another copy of it. and started it up and went on peq server and worked fine, even went and got a brand newly updated recent ui and worked perfect with no errors. am able to play on the server and use new ui just fine. so maybe its a good thing.

[wolfwalkereci]

Has any work been done to the client recently?
One thing I recently noticed was using /hidecorpse looted, while looting a corpse right after it died before it could poof (since it had no loot) would lock my character into the ducking [I am currently looting a mob] animation and I would have to /q to get out of it.

[Derision]

Originally Posted by wolfwalkereci

Has any work been done to the client recently?
One thing I recently noticed was using /hidecorpse looted, while looting a corpse right after it died before it could poof (since it had no loot) would lock my character into the ducking [I am currently looting a mob] animation and I would have to /q to get out of it.

I wrote the SoD /hidecorpse code and I didn't implement the /hidecorpse looted aspect of it. All the other options should work, just don't use /hidecorpse looted

[Derision]

Actually, if I remember, I will get a packet collect from Live tomorrow of the situation you describe and see if I can prevent you getting bugged.

[trevius]

Originally Posted by wolfwalkereci

Has any work been done to the client recently?
One thing I recently noticed was using /hidecorpse looted, while looting a corpse right after it died before it could poof (since it had no loot) would lock my character into the ducking [I am currently looting a mob] animation and I would have to /q to get out of it.

What server did this happen on? This bug isn't an issue with hidden corpses, it was an issue with empty corpses on servers that use the rule to poof empty corpses. They would be in the process of poofing when a player with high latency was looting them, and the server wouldn't send the end loot packet because it thought the corpse was already gone. Titanium handles the end loot response differently, so this problem wasn't happening on that client. I am pretty sure that I resolved this issue for SoD a while back by changing the handling to respond with the packet that SoD wants when an end loot packet is sent. Maybe the server you are playing on hasn't updated in quite a while. Like if you are playing on THF, I don't know if they are current enough to have that particular fix. Since I added it, I haven't heard any more reports about this issue on my server at least. If the problem does still exist in the current revisions, we will probably need to take another look at it, but as far as I know, it is now resolved.

Here is the revision that I put in the fix for this:

http://code.google.com/p/projecteqem.../detail?r=1546

SoD - Possible fix for empty corpse looting bugging clients.

[werebat]

Just installed SoD a couple of days ago and I see an issue where my Iksar beastlord bot is healing their pet instead of me even when pet is 100% health. This happens when I am below 80% so I think it is trying to heal me but casting the wrong healing spell (Sharik's Replenishing).

[trevius]

Sounds like a like a bot related issue, which should have nothing to do with the SoD client itself.

[werebat]

Delete or move my previous post. I looked at the code and it appears to be a bug unrelated to SoD, sorry about that.

Thanks