In Discussion Bossing Automatic Rewarp for Boss run DC

I am pretty sure a similar topic has been discussed before but I couldn't find it with my search skills therefore I would like to post my suggestion here.
This idea was originally from @222222 and I'd like to give him credit for any fortunate outcome.

Disconnection during boss runs, especially Zakum and Horntail, is one of the worst things one can experience; whether it was caused by a server sided issue (Lag, Server freeze, graphical glitch) or individual's faults (Struck by lightning, accidentally pressing X button, cat kicking lan cable etc.). Have you ever witnessed random client shutdown with "error -21xxxxxxxxx" message? Have you ever experienced random internet loss that resulted in a disconnection? If there could be a system that allows automatic rewarps of disconnected runners, boss runs will be way less stressful - even if it's once-off.

I believe this idea was rejected numerous times in the past due to the loopholes in the system that allowed people to abuse it for selfish purposes. However this suggestion could possibly cover all those loopholes.

Layout of this system

• Once one signs up for the bossing squad, individual's [waiting room] with a 3min timer will be created somewhere.
• If a signed member of the squad disconnectes during the run, gone from the map, (excluding exit via npc chat) allocated [waiting room]'s 3 minute timer will start ticking.
  • If the character relogs, in the same channel, before 3 minutes are up, the character will automatically get warped to the [waiting room].
  • Once the character is in the [waiting room], whatever remained of the 3 min timer will disappear and 5 second timer will appear instead, ticking immediately. Once the 5 sec time is up, the character will get warped automatically back to the boss map.

-This 5 second extra duration in the [waiting room] is for the sake of mages who can die instantly if warped without magic guard.

Limitations

1. This system is once-off/ boss run (individually) and will not be activated if the same character disconnects for the 2nd time.
2. If the 3 minute timer runs out before disconnected character logs in again, the chance for automatic rewarp is forfeited.
3. If the character was dead at the moment of disconnection, it will be rewarped to town or a different map (Passage map for zak, Cave of life for HT) and not to the [waiting room].

Pros of this system

• Gives 2nd chance to those unlucky people who happened to disconnect during an important boss run.
• Once-off availability of this system will prevent people from abusing the system.

Possible Cons of this system

• One can disconnect intentionally toward the end of a boss run or during an emergency (e.g Seduced in HT) to spend upto 3mintues out of the boss' vicinity in safety?

- I cannot think of many who'd intentionally disconnect themselves with the risk of not being able to make it back if anything goes wrong with game launching.
- If one could survive till the last 3minutes of a boss run, there is no particular reason to go through the tedious work of re-logging for "safety".
- 3 minute is really not that long of a period because some royallers use old/slow pc and may take longer to launch the client.
- If the seduce target disconnects intentionally right after getting seduced, target for seduce is automatically shifted to the next person on the signup list and that would be far more dangerous.

• If you happened to be dead at the moment of dc...sorry but nothing can be done about that.

- Purpose of this system is to give a 2nd chance to those who disconnected not those who died

• Coding may be complicated

- Uh..I dunno about coding. The person who came up with the original idea said it'll just require lots of "IF" scripts in chain.

This is ONLY a rough example :
I have 0 idea how coding works

if (hp>0){
login to waiting room;
warp to zakum map after 5 seconds;}
else warp to Passage;


This is ONLY a personal suggestion for the purpose of less stressful bossing runs! Please feel free to object any room for improvement, loopholes I didn't catch or problems that lie ahead with this system. If you think this system isn't necessary, please explain why as well

 

+1 I'm sick & tired of my cats fighting near the router box and making me lose out on potential splits.

 

It could work I guess. The main reason they stopped warping is cause people abused it to leave when they die then claim they dced to get warp.

 

I love your script. I suggest implementing it unedited

 

Yes, please!

 

Yes, please.
I’m tired of d/cing at HT, not being able to res my n word @Dre and it’s worse than dying twice in a single run like @FarmerStory would do.

 

I 100% support this, I've played on a much smaller private server with this feature and it was honestly a godsend. I don't see ANY reason why this shouldn't be implemented on a server of this size (other than feature priority), but it should definitely be on the future features list at the very least.

 

In addition to preventing abuse from lying, I believe that the many previous ideas you referenced were rejected because staff wanted to make sure they were rewarping for issues that were actually Royals-sided and not user-sided.

Your system includes things that are player-sided, such as internet disconnects, which currently aren't covered by the rewarp policy. Just wanted to clarify if your suggestion is simply about getting an NPC to automate the task of rewarping, especially since we don't have a working ~GM command right now, or are you asking for an expansion of the current rewarp policy?

 

I am asking for an expansion of the current rewarp policy but WITH the use of an automated rewarp system. I "think" Matt and staff excluded player-sided issues from warping policy because it could be abused at individuals' intention and there would be no way to tell if the player is telling the truth. Without an automated system, the amount of rewarps they have to handle would also go way out of hand if done manually one by one.

One could say disconnecting due to one's own mistake/fault is part of nostalgia and hardships make you strong and more competitive ~ etc. However, what is the server losing if the poor victims are given a 2nd chance? (not even 3rd) From my own and others' experience, disconnecting during boss runs is one of the most irritating and discouraging thing that can happen to a player. This would be extremely biased if the server was stable and only players' faults caused the DC but there are known stability issues in bosses right now. Regional lags exist and graphical glitches persisted for months, years if counting old source cases. I witnessed many players rage quitting after continuous DCs and unfortunate cases of new players who were unable to get a single Zhelm after numerous failed attempts due to disconnection issues. Although I'm aware the staff are working hard to fix the problem, but in realistic approach, it is very unlikely to happen anytime soon. (Yes GFXing can prevent DC but not in every case).

I understand the T&C was made to serve a good purpose. I'm not asking for the rules to be broken but only manipulated for the improved welfare of active players we have here who ultimately make up the server.

 

Fair enough, and I totally understand! Just wanted to clarify because if it was solely about the NPC, I wanted to know how it was going to differentiate between player side vs. server side DCs, as this was one of the biggest stopping points of previous ideas regarding this. I really like the waiting room part of your idea, as this addresses Matt's concern about people using this as an opportunity to repot or whatever.

For reference, here's the previous rendition of the NPC idea that evolved from a feedback post by @liomio about the rewarp policy in general. Don't believe a conclusive decision was made regarding the NPC because new source was considered the solution, but the stance about differentiating between server/regional lag vs. player side seemed to be pretty strict at least back then. https://royals.ms/forum/threads/no-evidence-of-server-lag.70050/

 

Bump for sake of reminder, can this be moved to feedback perhaps? @Evan

 

+1

 

I second this motion

 

+1 especially since players from the SEA region are getting periodic major lag spikes for no apparent reasons

 

I think we can make the character invincible for a few seconds after rewarp instead of implementing a waiting room.
Because other than magic guard, you may need party buffs like hyper body to survive.

 

Bump!

To further improve on Sparky's idea, I suggest if any players want to get reconnected to an ongoing battle, it will consume untradable and unique items like Boss certificates. This is will ensure players will continue to GFX when necessary instead of relying on the auto-connecting system and it creates extra hassle if players think about abusing this system. Furthermore, by using boss drops, it already automatically filter out players who unable to survive till the end due to HP requirement or level.



The waiting room could be blank too if you want to simplify it. For tougher expedition bosses, like Horntail, you can add more requirements/items. Now disconnection from expeditions can be part of the gameplay instead of an obstacle.

 

Yes to this as well.
As we all know, whatever possiblity on disconnection into reconnections is definately to be abused by players in any way possible.

A quick abuse of such system i could quickly imagine up in my head is such as, my sed player/mule in Horntail is Sed Right, and in danger to walking to the tail, giving a super good chance of death.

One can easily alt f4 and dc-s. To avoid that death.
The other is mentioned by OP where Mass Seduce happens, example SE Mule, simply DC it and relog.

But meanwhile if an troublesome quest/unique item is required to use this rewarping from a DC-ing issue, then definately players wouldn’t even bother trying to abuse it, saving their time & resources.

Meanwhile i think this is an terrific idea if an requirement is added to be rewarp-ed inside the waiting room.

Imagine this and pink bean is added. MonkaS

 

Could there be a way to make it so that if you dc while seduced you can’t rewarp? That would solve some abuse potential. Also, if you are rewarped to a “waiting area” ensure that players cannot drop/trade anything in said area.

 

Seems like dc issues are becoming a bit more problematic in the recent days. I'm hearing new random dc stories here and there without a known cause. Custom client still seems quite far away in future. Bumping again for support.

 

+1.
Pretty sure my connection is working fine cause I am the only one who DC and my bf who is living with me is still happily jumping in royals.

My dc rate is 1% but still.

And for those who DC all the time because of their graphic card etc.. Idk how you guys cope with it but I don’t think I will ever get a new graphic card just for a game lul. So this idea is really great.