LambdaHack / LambdaHack/LambdaHack
Make equipment capacity a stat, not a hardwired constant
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 664
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
In this way some very powerful weapons, e.g., with "two-handed" in name, may take 2 equipment slots.
Much harder goal: make it possible for an item to set actor's equip capacity (or any stat) to max 13 (current_stat_value). Or just a flat number if that's much easier. This would be useful to avoid a single hero getting 25 equipment and going solo instead of three getting 15 and doing smart tactics.
The first easy step, worth a separate PR, may be defining this constant in one file, instead of keeping the hardwired 10 in many. This would address the code smell aspect of that.
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 searching the project for the hardwired equipment-capacity value 10 and map where it is used. Decide whether to scope the work to centralizing that constant or to item-controlled capacity, then verify that equipment limits and the stated solo-versus-squad scenario behave as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100