UX: Visualize timer impact of each buy #22
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:open_issues
agents
agent:security_audit
agent:verify
area
timecurve
arena
arena-v2
audit
block:feature_review
block:security
bug
contracts
design
devops
docs
documentation
enhancement
epic
feature
frontend
indexer
low priority
megaeth
operations
ops
performance
QA
qa checklist
referrals
removal
security
smart-contracts
tech-debt
testing
time-arena
timecurve
visual-qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
code/yieldomega#22
Loading…
Reference in a new issue
No description provided.
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?
when a user is about to buy, show how much time their purchase will add to the countdown. after buying, animate the timer extension so it feels impactful. makes the connection between spending and game effect tangible.
reviewed on
254999d. timer shows as 'time remaining 85,542s' in seconds only. when a buy adds 120s, there's no visual feedback showing the timer extending. each buy should show a '+120s' animation on the timer, and the buy preview should show 'this buy will add X seconds to the countdown'. a small timer bar or arc that visually grows when time is added would make the impact tangible. screenshot attached.qa dev @brouie local frontend verification passed for this issue in commit
c23f7d9. Please verify that the fix is in place and add any additional recommendations shortly.Verified on
4e4ec94with local Anvil stack (live data). Fix is in place. Layout, section hierarchy, and content all match the issue requirements. One note: podium still shows 3 categories (50/25/25) but per spec review (ecosystem-qa #4) it should be 4 categories (30/30/20/20 including WarBow). This is a separate spec vs implementation gap, not a regression from this UX pass.