Disconnect Strats
Posted: Sun May 18, 2025 11:45 pm
There has been a question raised around whether disconnects should be permitted within the rules. This is where a player leaves the instance to trigger/avoid triggering certain quest/mob updates, or to manipulate AI behaviour (or other, yet unknown, reasons).
Whilst there have been several records in the past that have utilised this strategy and have been approved (Urgoz, UW), I think its good to clarify for records going forward given interest on the topic.
Ill add key arguments to this post when as they are raised:
Initial arguments for:
Additional options for players encourages innovation
Other AI / game manipulations are permitted / used extensively.
Initial arguments against:
The leaving player does not receive credit for the area (vq complete, chest, mission completion etc)
Other party manipulations (e.g. slow-load) have specific rules defined and are only permitted for TAS.
Additionally, as part of the discussion, I would invite players to discuss how we should moderate this rule if disconnects are rejected, in particular:
How do we define a disconnect? Is it simply "all players must remain within the instance until area completion"? Theoretically, someone could finish their role in a record and leave for reasons beyond manipulating AI/game behaviour (i.e. accidental disconnect or real-life situations). Would this void the record? If only disallowing "intentional" disconnects - how should this be defined?
How do we prove all party members were present at the end of the run for TAS records (where only 1 video is required)? I assume we will need to add a general rule to have the party window open at the end of the run for all 2+ party member sizes, to prove this - but open to other thoughts. Obviously, the vast majority of players do this anyway so shouldn't impact players too much but I think this would need to be stipulated going forward. One could argue that "it's obvious if someone has intentionally disconnected", but this is not necessarily the case and we cannot predict all future strats.
Whilst there have been several records in the past that have utilised this strategy and have been approved (Urgoz, UW), I think its good to clarify for records going forward given interest on the topic.
Ill add key arguments to this post when as they are raised:
Initial arguments for:
Additional options for players encourages innovation
Other AI / game manipulations are permitted / used extensively.
Initial arguments against:
The leaving player does not receive credit for the area (vq complete, chest, mission completion etc)
Other party manipulations (e.g. slow-load) have specific rules defined and are only permitted for TAS.
Additionally, as part of the discussion, I would invite players to discuss how we should moderate this rule if disconnects are rejected, in particular:
How do we define a disconnect? Is it simply "all players must remain within the instance until area completion"? Theoretically, someone could finish their role in a record and leave for reasons beyond manipulating AI/game behaviour (i.e. accidental disconnect or real-life situations). Would this void the record? If only disallowing "intentional" disconnects - how should this be defined?
How do we prove all party members were present at the end of the run for TAS records (where only 1 video is required)? I assume we will need to add a general rule to have the party window open at the end of the run for all 2+ party member sizes, to prove this - but open to other thoughts. Obviously, the vast majority of players do this anyway so shouldn't impact players too much but I think this would need to be stipulated going forward. One could argue that "it's obvious if someone has intentionally disconnected", but this is not necessarily the case and we cannot predict all future strats.