Implement components
Open
Nobody has claimed this yet.
area: simulation
big stuff
lang: c++
nice new thing ☺
overview
- Dominant language
- Python
- Stars
- 14.4k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
Overview of the necessary gameplay components that we need to implement:
- Idle
- Move
- Turn
- Live
- Selectable
- ComponentState (state changes)
- Stance
- RallyPoint
- ProductionQueue
- CollectStorage
- RemoveStorage
- TransferStorage
- EnterContainer
- ExitContainer
- SendBackToTask
- EntityStorage
- ResourceStorage
- HarvestStorage
- Create
- Research
- TradePost
- Trade
- ResourceExchange
- Formation
- Named
- RegenerateAttribute
- LineOfSight
- Resistance
- Hitbox
- Collision
- Cloak
- DetectCloak
- Herdable
- Despawn
- Stop
- ApplyDiscreteEffect + Ranged
- ApplyContinuousEffect + Ranged
- ShootProjectile
- Projectile
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
Read doc/code/game_simulation/game_entity.md, especially its component data storage section, before choosing a component from the unchecked list. Confirm the intended scope and implementation locations with project maintainers, since the issue does not name files or tests. Done would require implementing the selected unchecked gameplay components and marking the corresponding checklist entries complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100