Post: #60

but that's not the point :/
theres "2 types" of resurrect with different functionalities, I just wanna integrated all on a single trigger that works for both, not prevent one type to be used

on my server we use the normal "cast" resurrect (where the resurrect confirmation dialog appears) and theres the "forced" resurrect too (function RESURRECT 1) which we use on scripts (automated quests, systems, etc) where the player -will- be resurrected without any confirmation. No problem resurrecting, because both will resurrect fine. The problem is about how sphere handle both resurrect styles (triggers)

Using a real situation example, I use a realtime SQL paperdoll to show it on the website, when the player dies it must update corpse color to 0 and make it ghost style (works fine with @Death), but when it resurrects the body must be updated again to the correct body and color but this is only possible using the "casted" resurrect (@Success on spell 59). For RESURRECT 1 functions I must create a horrible workaround calling a horrible function every time I use RESURRECT 1 and it's a pain for who uses a lot of them in different script files. So, everything is a horrible workaround because half of the code is wrote on a workaround (@Success on spell 59) and the other half is wrote manually on another workaround. Theres workarounds everywhere and thats not good. Thats why a simple @Resurrect will save tons of ugly workarounds, making everything works perfectly on a single trigger