OpenRA / OpenRA/OpenRA

Mitigate Squatting Abuse in Servers by AFK-Hosts

Open
#21,415 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Idea/Wishlist
Dominant language
C#
Stars
17.4k
Forks
3k
Avg merge
1d 12h
Merged PRs (30d)
14

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points; begin by locating the multiplayer server host and inactivity handling. Clarify the timeout, warning, kick or ban, voting, and host-transfer requirements, then define tests for the agreed behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
game-dev, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
22/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.