New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mitigate Squatting Abuse in Servers by AFK-Hosts #21415
Labels
Comments
When starting and configuring a server, the admin should be able to activate (checkbox) and specify (numeric dropdown selecetion, 5min as preset) a duration of acceptable host inactivity (no changes in game options, chat messages, or team setup made). |
Relates to #16108 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation
REQUEST MOTIVATION
The online/multiplayer experience is negatively affected by players joining as hosts and going AFK, effectively disabling the server for an indefinite amount of time. As a result, users who join that server in good faith, only to receive no response from the AFK host, are angered and have their time wasted. The same also applies to one or more players remaining on a server afk indefinitely, after the match is over. Such a server too cannot be used until the idle players are removed.
Proposed solution
PROPOSED SOLUTION
OpenRA should implement an inactivity timer after which an inactive host (squatter) in the server gets removed. Repeated squatting should lead to an automatic ban from joining again. Others users within the server lobby should be able to hold a vote to kick a user and/or transfer host privileges.
Side effects
EXPECTED SIDE EFFECTS
A host-removing voting feature might incur some conflict or abuses pre-game. An inactive host might get wrongfully auto-kicked even though he may genuinely be waiting for others to join. However, he can try to rejoin the server or respond in the chat to a prompt warning about the inactivity.
Alternatives
ALTERNATIVES
Not addressing the issue will continue the problem of servers becoming idle and unusable.
The text was updated successfully, but these errors were encountered: