Refactoring Agent
fc9e4c8327
Build and Publish Mana Loop Docker Image / build-and-publish (push) Successful in 1m46s
33 lines
1.5 KiB
Markdown
33 lines
1.5 KiB
Markdown
# Task 5: DebugTab Update - Invoker Debug Buttons - Context
|
|
|
|
## Task Description
|
|
**From task2.md:** Add Invoker Debugging Buttons to manually trigger/force Pacts with different Guardians.
|
|
|
|
## Current Implementation:
|
|
- DebugTab is likely in `/home/user/repos/Mana-Loop/src/components/game/debug/` or similar
|
|
- Pact system involves Guardians and signing pacts with them
|
|
- DebugTab already has some debugging features
|
|
|
|
## What Needs To Be Done:
|
|
1. Find the DebugTab component (search for "DebugTab" or look in `src/components/game/debug/`)
|
|
2. Read the component to understand current implementation
|
|
3. Find how Pacts work:
|
|
- Look for "pact" related functions in the store (`store.ts` or similar)
|
|
- Understand what signing a pact does (what state changes)
|
|
4. Add buttons to manually trigger/force Pacts with different Guardians:
|
|
- Each Guardian should have a button
|
|
- Clicking the button forces a pact with that Guardian
|
|
5. Test the implementation
|
|
6. Commit with message: "Task 2: DebugTab Update - add Invoker Debugging Buttons for Pacts"
|
|
|
|
## Key Files To Examine:
|
|
- `src/components/game/debug/` - DebugTab component
|
|
- `src/lib/game/store.ts` - Pact-related functions
|
|
- Look for Guardian definitions (maybe in `constants/` or `data/`)
|
|
|
|
## Implementation Notes:
|
|
- Pacts are likely stored in the game state
|
|
- Forcing a pact might involve calling a function like `store.signPact(guardianId)`
|
|
- The buttons should be clearly labeled with Guardian names
|
|
- Consider adding confirmation dialogs to prevent accidental clicks
|