Autohosts unable to connect / host
Posted: 01 Dec 2018, 19:49
There seems to be a lobby update command which triggers a global reset of all servers when triggered.
From the observations of myself and other players it seems that rather than being used for its intended purpose of lobby updates this functionality is being exploited as a mean of resetting servers when BA10 maintainers see unwanted activity on BA9 hosts.
Today for example, a lobby update was triggered mid game during a BA 9 match. This would otherwise have gone unnoticed, had I not tabbed out to Springlobby to see Triton as the lone occupant of the sole BA10 host remaining online. There was no sign of a genuine update and Triton's host subsequently gained players because no other host was available. Triton has previously stated on Discord that as maintainer his ambition is to take down all hosts of previous versions. It is possible something to this effect has been underway behind the scenes of lobby development.
Is there anyone left impartial with sufficient privileges to check logs to confirm if a command was triggered? If confirmed please can people exploiting it have their powers revoked. Thanks.
From the observations of myself and other players it seems that rather than being used for its intended purpose of lobby updates this functionality is being exploited as a mean of resetting servers when BA10 maintainers see unwanted activity on BA9 hosts.
Today for example, a lobby update was triggered mid game during a BA 9 match. This would otherwise have gone unnoticed, had I not tabbed out to Springlobby to see Triton as the lone occupant of the sole BA10 host remaining online. There was no sign of a genuine update and Triton's host subsequently gained players because no other host was available. Triton has previously stated on Discord that as maintainer his ambition is to take down all hosts of previous versions. It is possible something to this effect has been underway behind the scenes of lobby development.
Is there anyone left impartial with sufficient privileges to check logs to confirm if a command was triggered? If confirmed please can people exploiting it have their powers revoked. Thanks.