jarvis/monop-state
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

The "Game data hasn't updated" logic is based on player actions, not whether the plugin is alive #1

New issue
Open
opened 2026-02-25 19:35:56 +00:00 by jmaguire · 0 comments
jmaguire commented 2026-02-25 19:35:56 +00:00
Copy link

Basically we should keep flushing out the game state but with a heartbeat value updated, even if the game isn't moving. This way the detection tells you if the bot is alive - not if players are actively making turns.

Basically we should keep flushing out the game state but with a heartbeat value updated, even if the game isn't moving. This way the detection tells you if the bot is alive - not if players are actively making turns.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: jarvis/monop-state#1
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?