Field Manual / Behind the simulation
Development Notes
Coffee Battles is playable now, and its systems are being improved in public. These notes separate what players can use today from areas still being refined.
What the current build contains
The publicly accessible game already includes army setup, a points-based unit catalogue, deployment, real-time orders, three formations, ranged attacks, fatigue, morale, terrain obstacles, fog of war and a result screen. It runs directly in the browser and does not require a personal account to start a battle.
The system is intentionally simulation-oriented. Movement and orders interact with physical formation sizes, facing, roadblocks, line of sight and morale rather than with a single abstract strength number. A visible battle therefore offers both a game and a way to observe how small tactical choices change outcomes.
Selected changes from the public repository
These entries describe publicly recorded changes, not invented milestones or promises of a final release date. For the complete sequence of commits, see the development history on GitHub.
Battle visibility, deployment and match flow
Recent commits restored battlefield fog of war, adjusted the deployment builder position, repaired terrain/grid rendering after setup, added a countdown and rout timeout, blocked movement over sea terrain and changed multiplayer start behaviour to begin at normal speed. These were individual implementation and repair changes; they should not be read as a guarantee that every multiplayer edge case has been resolved.
Monetization controls added to the game shell
Buy Me a Coffee buttons and sponsorship placeholders were integrated around the setup and battle-result views without changing the battle simulator itself. Sponsor placeholders are not paid Google advertisements. Ad-serving approval is independent of these controls, and support contributions are optional.
Ongoing simulation and interface improvements
Work around regiment representation, multi-language interface content and deterministic simulation testing continued around this period. The game is designed so changes can be tested against repeatable scenarios as well as observed interactively.
What is still changing
Balancing eight troop types is not a single pass. A charge that is too powerful or an automatic targeting rule that behaves unexpectedly can change the value of an entire class of regiment. Terrain handling, intelligence, user interface details and multiplayer coordination also need continued testing. Public development means features may be corrected or adjusted rather than remaining frozen after their first implementation.
For that reason, the unit reference documents the current code-defined values, the formation guide explains the practical effects and the exercise guide suggests short tests. These resources are maintained as a description of the playable system, not marketing copy for future features.
How to follow or contribute
You can play the game without an account, inspect the public repository or send reproducible feedback. A useful bug report includes the map type, unit composition, last orders before the failure and what actually happened. Avoid posting personal details or payment information in public issue threads.
Supporting development through Buy Me a Coffee is optional. Access to the core game and its field manual does not depend on making a contribution. Advertising, where enabled, is handled separately from game rules and purchases.
This guide describes the published game mechanics and practical uses for them. Balance and interface details may change as Coffee Battles evolves. Play the current build or report an issue.