SphereServer BugTracker - SphereServer
View Issue Details
0002193SphereServerexecutable - windows buildpublic22-08-13 09:5627-08-13 04:53
Coruja 
Ben 
normalmajoralways
resolvedfixed 
16-06-2013, 0.56b Prerelease 
 
Automated (specify build number)
None
None
0002193: Mounts dying while mounted
If I'm using a mount, and this mount got a damage and die WHILE I'M MOUNTED, it will keep alive a few more seconds and theres 2 bugs:

-------------------------------

BUG 1: After mount die, I continue using the mount
After dead, strangely sphere will keep the mount alive a few more seconds and them randomly it detects the dead mount and I got dismounted, the mount die and I got this console warning:

03:53:ERROR:Character Coruja (01e403) riding dead horse (067a60) - forcing death on horse

The problem is: it doesnt die instantly, it only dies after some seconds instead die on the hit moment

-------------------------------

BUG 2: After mount die, I dismount it manually
Now on dismount, instead sphere force the NPC to die, it will remove the NPC from the screen but the NPC will continue existing as a ghost with HITS=0 and you can see it using .update
No console errors now.
1) .add c_llama
2) use ".xtimerf 3 damage 1000" on the llama
2) mount the llama before it dies
3) wait for the mount dies and you got pulled over the mount (bug 1) or dismount manually (bug 2)
Probably theres some protection to prevent this but this protection is failing. Maybe it will work better if it check for the mount hitpoint on every @GetHit instead checking using a strange random timer

PS1: UO has a pet bounding system where loyal pets dies, remains as a ghost and can be resurrected. Since sphere doesnt support this, I'm assuming the correct behavior is make the pet die

PS2: Using latest sphere nightly build
No tags attached.
Issue History
22-08-13 09:56CorujaNew Issue
27-08-13 04:53BenNote Added: 0001643
27-08-13 04:53BenStatusnew => resolved
27-08-13 04:53BenResolutionopen => fixed
27-08-13 04:53BenAssigned To => Ben

Notes
(0001643)
Ben   
27-08-13 04:53   
I have this fixed on local (both bugs) but this will only be added once the compiling issue is resolved.