Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Bannerlord M4] Formation Commander — Real-Time Battle Orders #1096

New Issue
Closed
opened 2026-03-23 16:49:24 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-23 16:49:24 +00:00
Collaborator
Copy Link

Parent: #1091
Benchmark gate: Level 3 (battle tactics) passed

Task

Timmy enters battles and issues real-time formation orders instead of auto-resolving.

Steps:

  1. Implement battle/* GABS tools in heartbeat loop
  2. Combat state polling via MissionBehavior
  3. Formation order pipeline (position, arrangement, facing, firing)
  4. Tactical heuristics: high ground for archers, cavalry flanking, retreat logic

Done when: Timmy wins 70%+ of evenly-matched battles via formation commands (not auto-resolve).

Estimated effort: 4-6 weeks

**Parent:** #1091 **Benchmark gate:** Level 3 (battle tactics) passed ## Task Timmy enters battles and issues real-time formation orders instead of auto-resolving. **Steps:** 1. Implement battle/* GABS tools in heartbeat loop 2. Combat state polling via MissionBehavior 3. Formation order pipeline (position, arrangement, facing, firing) 4. Tactical heuristics: high ground for archers, cavalry flanking, retreat logic **Done when:** Timmy wins 70%+ of evenly-matched battles via formation commands (not auto-resolve). **Estimated effort:** 4-6 weeks
claude self-assigned this 2026-03-23 17:56:49 +00:00
claude commented 2026-03-23 17:59:05 +00:00
Collaborator
Copy Link

Formation Commander — Declined

After reviewing this issue, I am declining to implement the requested Bannerlord M4 battle formation AI. Here is why:

1. Out of scope for this repository

This task requires:

  • A Windows VM running Mount & Blade II: Bannerlord
  • The GABS C# mod with a TCP/JSON-RPC server on port 4825
  • Real-time combat AI against the game's MissionBehavior C# API
  • Formation order heuristics for in-game unit control

None of this belongs in a Python/FastAPI web dashboard. The Timmy-time-dashboard has no game integration layer, and this work cannot be done or tested without the full Bannerlord + GABS infrastructure.

2. Estimated 4-6 weeks on a different stack

The issue itself estimates 4-6 weeks. This is a reasonable estimate for a non-trivial game AI integration — but it is an estimate for work on a different platform (C#/game modding), not on this Python codebase.

3. Missing prerequisite infrastructure

The parent epic #1091 describes the full architecture: Timmy → GABS TCP/JSON-RPC → Bannerlord.GABS C# mod → Game API. That TCP client and heartbeat loop do not exist here yet and would need a separate repository or module.

Recommendation

If this is planned work, it should live in a dedicated bannerlord-agent/ module or repository, not inside the dashboard. Start with M1/M2 milestones from #1091 to establish the GABS connection before attempting M4 formation commands.

PR: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/1109

Refs #1096 — declining as out of scope.

## Formation Commander — Declined After reviewing this issue, I am declining to implement the requested Bannerlord M4 battle formation AI. Here is why: ### 1. Out of scope for this repository This task requires: - A Windows VM running Mount & Blade II: Bannerlord - The GABS C# mod with a TCP/JSON-RPC server on port 4825 - Real-time combat AI against the game's `MissionBehavior` C# API - Formation order heuristics for in-game unit control None of this belongs in a Python/FastAPI web dashboard. The Timmy-time-dashboard has no game integration layer, and this work cannot be done or tested without the full Bannerlord + GABS infrastructure. ### 2. Estimated 4-6 weeks on a different stack The issue itself estimates 4-6 weeks. This is a reasonable estimate for a non-trivial game AI integration — but it is an estimate for work on a different platform (C#/game modding), not on this Python codebase. ### 3. Missing prerequisite infrastructure The parent epic #1091 describes the full architecture: Timmy → GABS TCP/JSON-RPC → Bannerlord.GABS C# mod → Game API. That TCP client and heartbeat loop do not exist here yet and would need a separate repository or module. ### Recommendation If this is planned work, it should live in a dedicated `bannerlord-agent/` module or repository, not inside the dashboard. Start with M1/M2 milestones from #1091 to establish the GABS connection before attempting M4 formation commands. PR: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/1109 Refs #1096 — declining as out of scope.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1096
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?