High Resurrection bug

FeelsFuckingBadMan

 

Also just want to point out some wording in the Rewarp Policy thread that is misleading, and in this case should have definitely warranted a rewarp for Dylan when res did not work.

"However, at that time we still allowed people to get rewarped if they got banned by our auto ban system (falsely of course). The most common case back then was Bow Masters getting banned for faraway mob, or other cases.

Later on we not only improved our auto ban system by a lot, but we also changed a lot how instanced events work (especially boss battles, since Zakum and Horntail are pretty much (almost) GMS-like now, while back then they were barely instanced at all)"

First:
The policy in place right now which says no rewarp in any condition only makes sense IF you have improved the system (bosses like HT) exactly like GMS. If bosses are not GMS-like yet (in GMS you would NEVER have a resurrection glitch), then the no rewarp policy inherently gets voided. Rewarps in our scenario today should be allowed as an exceptional case due to the code not working as expected.

Secondly:
Even if bosses are instanced now,

"A similar thing is for boss-battles, but not as major. Example, the boss still hits the person, etc. However, lets say the boss timer runs out, everyone except the person that got rewarped will be teleported out"


If the only consideration for not rewarping somebody back into a boss battle is only one minor reason which is the person may not be teleported out at timer expire, does it even make sense to include boss rewarps in the policy to begin with?

In cases like ours.. where the timer is nowhere near being used up and the boss dies as an end result (we have 100% success rate at HT so far), the rewarp consideration for the person after timer expires doesn't even come into play.

I don't know, just my opinions on the logic used in the no rewarp policy vs what actually is happening in game.

 

Manually warping people means that there has to be a GM active. This may not always be the case. In extend, that means that if one of the staff has a character involved with the boss run, it gives you the advantage of always having that needed person active. Which smells like a no-no to me.

Secondly there's the instanced behaviour, which does more than just timers and warp-outs. And for reason number one, I do not believe it would be a good idea to rebind the instance on warp.

Thirdly, there's no way of an automated process here.

That's why we have that lovely policy. I rather have to deal with fixing a bug, than having to deal with "why did they get a re-warp while we didn't".

 

I understand all of this but it still sucks to be punished for something that isn't your fault.

 

My res hasn't, my Holy Shield has tho, not sure if related. (Not as big of a deal, only 3min cooldown, but still annoying)

 

My res works fine - have not countered a bug, agree with Number32 on Holy Shield.
Goes on cool down but only some party members get it (it has even happened that 4/6 party members got Holy Shield but not I + 1 other)

 

doesnt seem to happen very often but i also don't go on enough runs to say