nhcarrigan/elysium
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 5 Pull Requests 1 Actions Releases 10 Activity

feat: cap auto-buy count on non-max-tier adventurers #151

New Issue
Closed
opened 2026-03-25 15:12:20 -07:00 by hikari · 1 comment
hikari commented 2026-03-25 15:12:20 -07:00
Owner
Copy Link
Copy Source

Description

Auto-buy should stop purchasing lower-tier adventurers once they reach a configured cap (e.g. 100), so that gold is not wasted on weaker units when stronger ones become available.

Proposed Behaviour

  • Each adventurer tier except the current highest-unlocked tier has a maximum auto-buy count (e.g. 100)
  • Once a non-max-tier adventurer reaches that cap, auto-buy skips it and continues to the next affordable tier
  • The highest-unlocked adventurer tier retains no cap (auto-buy continues purchasing it freely)
  • When a new tier is unlocked, the previously uncapped tier becomes capped and the new tier becomes the uncapped one

Example

  • Player has unlocked up to Knight (tier 7)
  • Auto-buy will purchase Peasant, Militia, Apprentice, Scout, Acolyte, Ranger up to 100 each
  • Auto-buy will purchase Knight freely (no cap) as it is the current highest tier

Notes

The cap value (100) is a suggested default — consider whether this should be configurable per player or fixed in the game data. Also consider whether the cap should apply immediately or only once the next tier is unlocked.

✨ This issue was created with help from Hikari~ 🌸

## Description Auto-buy should stop purchasing lower-tier adventurers once they reach a configured cap (e.g. 100), so that gold is not wasted on weaker units when stronger ones become available. ## Proposed Behaviour - Each adventurer tier except the current highest-unlocked tier has a maximum auto-buy count (e.g. 100) - Once a non-max-tier adventurer reaches that cap, auto-buy skips it and continues to the next affordable tier - The highest-unlocked adventurer tier retains no cap (auto-buy continues purchasing it freely) - When a new tier is unlocked, the previously uncapped tier becomes capped and the new tier becomes the uncapped one ## Example - Player has unlocked up to Knight (tier 7) - Auto-buy will purchase Peasant, Militia, Apprentice, Scout, Acolyte, Ranger up to 100 each - Auto-buy will purchase Knight freely (no cap) as it is the current highest tier ## Notes The cap value (100) is a suggested default — consider whether this should be configurable per player or fixed in the game data. Also consider whether the cap should apply immediately or only once the next tier is unlocked. ✨ This issue was created with help from Hikari~ 🌸
hikari commented 2026-04-06 19:04:34 -07:00
Author
Owner
Copy Link
Copy Source

Already implemented — autoBuyCap = 100 with max-tier check in gameContext.tsx. ✨ This issue was closed with help from Hikari~ 🌸

Already implemented — autoBuyCap = 100 with max-tier check in gameContext.tsx. ✨ This issue was closed with help from Hikari~ 🌸
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/elysium#151
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?