Forge & Field
Developer Task Board
Sprint planning & feature backlog · v0.next
← Back to project High priority
Medium priority
Low / Long-term
UX & Navigation3 items · 3 done
✓
Main screen expedition banner — show active expedition status while idle
When a hero is on an expedition, display a persistent banner or status indicator on the home screen similar to the idle state UI.
✓
Hero clickable on main screen → navigates to hero detail page
Tapping the hero character on the home screen should route to their full stats/profile page.
✓
Inventory multiselect — hold to select multiple items for batch sell
Long-press an item to enter multiselect mode; allow selecting multiple items and selling them in a single action.
Features23 items · 20 done
UI: Replace attack power icon on barracks hero screen
## Description
The current attack power icon on the barracks hero screen is dark and hard to read against the background. Needs a more legible, conventional icon.
## Proposed Solution
Use a sword icon (⚔️ or custom SVG) — standard game convention for attack stats. Consider also reviewing other stat icons for consistency:
- Sword = attack
- Shield = defense
- Lightning bolt = speed
## Priority
**Low / Polish**
Discord bot: persistent process with button interactions
## Summary
Current Discord integration uses ephemeral hook scripts (run and exit) for notifications, approvals, and questions. This works but requires text replies (y/n, option numbers) in threads.
Discord buttons (Components V2) provide better UX — click to approve/deny, click to select an option — but require a persistent bot process to receive interaction events.
## Current architecture
- `~/.claude/communicate.py` dispatcher → `discord_approval.py`, `discord_ask.py`, `discord_notify.py`
- `discord_session.py` manages one thread per project per session
- All scripts are ephemeral (hook invokes → posts to Discord → polls for text reply → exits)
## Proposed
- Build a lightweight persistent bot (Python `discord.py` or Node `discord.js`)
- Register interaction endpoint for button clicks
- Approval messages get Approve (green) / Deny (red) buttons
- Question messages get numbered option buttons
- Bot receives click events and writes response to a file that the hook script reads
- Falls back to text replies if bot is not running
## References
- Discord Components V2: containers, separators, flexible buttons
- Claude Code Discord Bridge pattern: thread = session, buttons for approvals
- OpenClaw pattern: approve/deny buttons with auto-cleanup
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Add FAQ / Help guide page
Add a help/guide link accessible from the game UI.
- For complex games: full guide covering mechanics, strategies, tips
- For simple puzzle games: lightweight one-pager with rules and basic tips
- Consider using a shared guide template/component across all games
Part of cross-game UX improvement initiative.
✓
Weapon durability / endurance system — degradation, repair, or dismantling
Add an endurance/durability stat to weapons. Define behavior at 0 durability:
- Weapon becomes unusable until repaired (for a resource cost)
- Magic weapons lose potency as durability drops
- Player can dismantle broken items for crafting resources
✓
Weapon level tiers (1/2/3) stacked on top of rarity (common/uncommon/epic)
A weapon should have both a rarity tier and a numeric level, e.g. 'Epic Longsword Lv.3'. Define how level interacts with stat scaling and upgrade paths.
✓
Hero health & endurance system — fatigue from expeditions
Heroes should accumulate fatigue/endurance drain as they complete expeditions. Introduce potions and a resting mechanic to restore health and endurance between runs.
✓
Weekly event chests & daily quest bonuses
Add limited-time event chests tied to week-long events. Daily quests (e.g. 'complete 3 expeditions') grant bonus loot on completion. Event chests should contain themed or exclusive rewards.
✓
Daily & timed loot chests — tiered by cooldown to drive engagement
Implement multiple chest tiers with different cooldown timers and reward scales:
- Small chests — 4–6 hour cooldown (potions, minor resources)
- Medium chests — 12 hour cooldown (weapons, more resources)
- Daily chest — 24 hour cooldown (best loot: gear, special items)
Rewards should include potions, weapons, and crafting resources.
✓
Expedition consequence model — partial rewards, stat degradation on failure
Define what a failed or partial expedition means: hero health loss, weapon endurance drain, reduced loot, or a combination. Implement consequence application and surface results in the result screen.
✓
Titles / epithet system — event-earned titles with small hero bonuses
Implement earnable titles (e.g. 'Aldrich the Quick', 'Aldrich the Straw', 'Aldrich the Cunning'). Present three choices per title unlock. Each title grants a small passive bonus to the hero.
✓
issue in forge and field where when you sell items in bulk it doesn't sell in event tracking. so my daily event task ...
issue in forge and field where when you sell items in bulk it doesn't sell in event tracking. so my daily event task to sell 5 items doesn't update when I bulk sell
---
*Auto-created from channel feedback on 2026-03-24*
✓
Add PWA manifest icons for home screen install
Add proper PWA manifest icons so the game displays a polished icon when added to iOS/Android home screens.
- Include icons at standard sizes (192x192, 512x512 minimum)
- Ensure `manifest.json` / `manifest.webmanifest` references them correctly
- Test on both iOS (Add to Home Screen) and Android (Install App prompt)
Part of cross-game PWA polish initiative.
✓
Design: Multi-hero party events
Are there planned expedition or combat events that require multiple heroes? If so, the expedition UI should support party composition.
Related issues: Cancel expedition, second hero unlock.
This is a design decision that needs discussion before implementation.
✓
Design: When does the player unlock a second hero?
Define the trigger/milestone for second hero unlock — commander level, story progression, in-game purchase, etc. Document and implement the unlock flow.
This is a design decision that needs discussion before implementation.
✓
Expedition summary — discovery callout
If a discovery was made during an expedition (new area, item, lore, etc.), it should be clearly surfaced in the expedition summary screen. Consider a dedicated animation or highlight moment for the reveal.
✓
Creature loot drops (passive)
Creatures should periodically drop loot during gameplay, influenced by a Luck stat or skill. Drops can include standard items or monster-specific unique drops. Bosses should always drop a loot crate/chest weighted toward rarer items.
✓
Locked content: show unlock requirements on tap
Bosses, expeditions, and map areas that aren't yet available should show a brief, styled callout when tapped — e.g. "Expedition locked · Requires Commander Lvl 5" — rather than being silently unclickable. Keep it short, descriptive, and on-brand.
✓
Cancel expedition button
Add a cancel/abort option for active expeditions to handle mis-clicks. Include a brief confirm prompt to prevent accidental cancellation.
✓
Multi-select item styling — replace checkbox with themed indicator
The current checkbox in the top-left of selected items feels generic/out of place. Replace with a stylized selection indicator (glow, rune mark, corner highlight, etc.) that matches Forge's visual language. No generic checkboxes.
✓
Inventory filter & sort controls
Add filter and sort controls to the inventory screen.
**Sort by:** rarity, level, type
**Filter by:** item type, rarity, level range
UI should match existing Forge design patterns.
✓
Daily counter resets at midnight PST
Ensure all daily counters and timers reset at 12:00 AM Pacific Time. Account for PST/PDT daylight saving transitions so the reset time is consistent for players.
✓
Loot crate opening animation + contents pop-up
When a loot crate is opened, show a reveal-style animation followed by a pop-up displaying exactly what was inside. Should feel rewarding and match the Forge visual style.
✓
Season countdown timer — add minutes and seconds
The existing season countdown timer should display `DD:HH:MM:SS` format for urgency and polish, especially in the final hours of a season.
Bug Fixes7 items · 7 done
✓
Fix inconsistent expedition reward pop-up — always show result screen
Reward/victory screen should reliably appear on every expedition completion. Investigate why it sometimes doesn't trigger. On failure, display a 'Failed' screen showing what was lost (resources, hero health, weapon durability, etc.).
✓
issue in forge and field where when you sell items in bulk it doesn't sell in...
issue in forge and field where when you sell items in bulk it doesn't sell in event tracking. so my daily event task to sell 5 items doesn't update when I bulk sell
---
*Auto-created from channel feedback on 2026-03-25*
✓
Bug: Extra craft slot from hero skill not rendering
## Description
A hero gained a skill that grants an extra craft slot. After acquiring the skill, no additional craft slot appeared in the UI — still only 3 slots visible. A third slot had previously appeared after an earlier fix, so this may be a regression.
## Investigation Notes
- Verify whether slot data is being saved to state but not rendered
- Check if the hero skill bonus is not being applied to the slot count at all
- Previously working — possible regression
## Priority
**Medium**
✓
Bug: Bulk sell not counting toward daily event
## Description
When selecting multiple items and selling them as a bulk action, the transaction does not increment the daily event counter. Selling 5 items in bulk registered as 0 progress toward the daily event goal.
**Expected:** Each item sold (or the bulk sell action itself) should count toward the daily event.
## Repro Steps
1. Select 5+ items
2. Bulk sell
3. Check daily event progress counter
4. No change registered
## Priority
**High** — blocks daily engagement loop
✓
Crafting queue shifts list layout on click
When clicking "Craft," the queue item is added and the crafting list shifts down, breaking rapid re-clicking of "Craft Again." Crafting slots should always be visible (empty slots shown as inactive/placeholder) so the list height remains stable regardless of queue state.
✓
Buried Workshop not granting new crafting slot
Player unlocked Buried Workshop but did not receive the expected additional crafting slot. Likely a save migration issue — when updates are pushed, existing saved progress may not correctly receive upgrade rewards. Investigate whether upgrade/unlock rewards are properly applied during save migration.
✓
Bottom menu bar clipped on iPhone
Menu bar is clipped at the bottom on iOS Safari. Need to apply safe area insets (`env(safe-area-inset-bottom)`) to the bottom navigation/menu bar component to respect the iPhone home indicator area.
Research3 items · 3 done
✓
Research: inventory max size system — scales with hero level or settlement upgrades
Investigate two models: (1) inventory cap grows as hero levels up, (2) players build/upgrade a storehouse structure in a town to expand slots. Recommend one approach with tradeoffs documented.
✓
Research: magic as a weapon category & hero skill branch
Define magic weapon types, casting mechanics, mana or spell-charge systems, and a skill tree branch that unlocks magic affinity for the hero. Ensure compatibility with weapon durability/potency decay.
✓
Research: multiple hero roster — distinct classes, skill trees, and abilities
Spike on supporting a roster of heroes, each with unique skill branches, abilities, and progression paths. Assess impact on balance, UI, and save state.
Open Questions5 items · 5 done
❓ Open QuestionTown/settlement concept — inventory capacity and building upgradesHas a town/settlement/city concept been scoped for the game? If so, is it already influencing inventory capacity? If not, is this something we want to pursue — e.g. building a storehouse to increase inventory max?❓ Open QuestionExpedition consequences — pass/fail vs partial outcomesDo expeditions currently only pass/fail, or do they apply partial consequences (reduced weapon durability, hero health loss, partial loot)? Clarify before wiring up the failure screen so it shows meaningful data.❓ Open QuestionMagic system scope — weapon types, hero skill tree, and durability interactionsIs magic currently a part of the game? If not, scope a magic branch — both as a weapon type (staves, wands, tomes) and as a hero skill tree. Confirm before building durability/potency logic for magic items.❓ Open QuestionAbilities scope — confirm existing ability systems before designing title bonusesHave abilities been scoped or designed yet? Confirm what ability systems exist before designing title bonuses or multi-hero skill trees to avoid overlap.❓ Open QuestionMultiple heroes — classes, skill trees, and hero-specific abilitiesAre there multiple heroes in the game currently? Has any research been done on different hero classes, unique skill trees, and hero-specific abilities? If not, add to research backlog.