MechMania-28 / MechMania-28/Engine
Implement basic game logic
Open
Nobody has claimed this yet.
alpha
- Dominant language
- Java
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Finish basic game logic.
Here's @rishisek 's comment on the logic, basically what we expect for a turn to do.
/**
* A single turn:
* - Use
* - Move
* - Attack
* - Buy
*
* DecisionSet becomes a compilation of these 4. At the end of a turn, decision_set is written to JSON.
*
* Turn {
* players: [
* Player {
* // state
* }
* ],
* decision_sets: [
* DecisionSet {
* use, move, attack, buy
* }
* ]
* }
*/
/*
1. Create GameState
2. For each turn of game,
a. execute use, move, ...
b. render turn
*/
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 locating the existing GameState, Turn, Player, and DecisionSet entry points, then read how turns and decisions are currently represented. Compare the implementation with the issue's four actions—use, move, attack, and buy—and the stated JSON output. Done means the described game-state lifecycle, turn execution, rendering, and decision-set serialization are defined and working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100