Games in stand-alone codeworld-api
- Dominant language
- Haskell
- Stars
- 1.3k
- Forks
- 201
- PR merge metrics
- No merged PRs in 30d
Description
Development of games has left the stand-alone hackage release behind. This issue tracks the need for feature parity.
It's unclear whether these games should connect to the code.world/gameserver endpoint just as the JavaScript ones do. In some ways, I'd prefer to spawn a game server locally, so that the details of the game server protocol don't become relevant to backward compatibility.
Contributor guide
Research direction
Compare the stand-alone Hackage release with the current JavaScript games to identify the missing feature parity. Resolve whether games should use the code.world/gameserver endpoint or spawn a local game server, then verify that the stand-alone release supports the same games without exposing protocol details that affect backward compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100