Development transmission
The route to
campaign command.
Battleforge is being built in public stages. Dates are targets, not promises; each gate depends on testing, accessibility and whether the feature makes play better at the table.
ARCHIVERDM-27TRANSMISSION // OPEN
01
PHASE 01Live now
Public systems demo
A playable proof of the core loop: choose a platform, apply damage, watch systems degrade, save scans and export a battle report.
- Four reference platforms
- Seven tracked systems
- Critical hit sequence
- Crew condition
- Local scans and report export
02
PHASE 02Target 2027
Closed alpha
Put the tracker on real tables across different games, devices and accessibility needs. Feedback from this phase decides what earns a place in the core product.
- Editable vehicle profiles
- Custom critical tables
- Account and cloud saves
- Touch and keyboard testing
- Multiple ruleset trials
03
PHASE 03In development
Faction archive
Expand the original universe into optional commanders, troops, vehicles and narrative modules while keeping the tracker fully system-neutral.
- Faction dossiers
- Unit and vehicle archive
- Narrative events
- Original setting toolkit
- Shareable profiles
04
PHASE 04Planned
Campaign command
Connect battles into a persistent record where repairs, injuries, experience and hard-won reputations continue from mission to mission.
- Persistent forces
- Repair and salvage
- Crew progression
- Linked operations
- Club event tools
Product principles
What does not change.
01System-neutral core
The tracker supports your rules; it does not require a proprietary tabletop system.
02Useful before paid
The current intent is a genuinely useful free core, with optional advanced features still to be decided.
03Test before promise
Features and dates remain provisional until they survive real tables and real accessibility testing.
Development signal open
Help decide what comes next.
Join the list, test the demo and send a field report about the feature your table needs most.