Master server integration for lobbies
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.4k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
After multiplayer games are working, we want to mediate players between lobbies.
- Anybody can host a game
- The game can be chosen to be registered at the master server
- Others can join the game either directly or via master server
- Games can be password or token protected
The masterserver is already implemented but needs to be further polished.
Mainly, openage now needs to implement the counterpart for the lobby stuff.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked openage-masterserver project and the existing multiplayer lobby implementation; no repository files or tests are named in the issue. Define how hosting, registration, direct or master-server joining, and password or token protection should work, then identify the corresponding openage entry points. Done means the lobby counterpart integrates these flows with the master server.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, game-dev, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100