Issue information

Issue ID
#4430
Status
Needs more Info
Severity
None
Started
Hercules Elf Bot
Sep 11, 2010 18:45
Last Post
Hercules Elf Bot
Dec 26, 2011 13:09
Confirmation
N/A

Hercules Elf Bot - Sep 11, 2010 18:45

Originally posted by [b]theultramage[/b]
http://www.eathena.ws/board/index.php?autocom=bugtracker&showbug=4430

I see a problem in r14220 "Intimidate should warp you anyway even if the target died" and the followup r14221 "Intimidate now checks the distance between source and target in case it kills the target and then warps the respawned one". This change tries to patch the hole created by the preceding change, but in an awkward way. My initial suggestion was to figure out how to let the warping code know that the target was killed and that no warping should be done at all.

However, thinking about it produced more questions:
1. If you're supposed to warp even if killing the target mob, does that mean that the mob's loot drops on the ground while you end up on the other side of the map? Common sense says that it should definitely be the other way around. What happens on official servers?
2. Everything would be way more consistent if you first warped, and then dealt damage. This way these corner-cases wouldn't occur. However, on aegis the warp effect is scheduled to activate exactly 500ms after the hit lands (so 500ms+aspd since processing). I wouldn't stick to official behavior here though.

This post has been edited by theultramage: Sep 11 2010, 11:48 AM