GetAssetPack

Battalia: Army Battles for GameMaker

Battalia: Army Battles for GameMaker
Price
$9.99
Creator
CSAF — Core Systems Asset Factory
Genre
Strategy
Setting
Military
Engine
GameMaker

A GameMaker army battle system with five soldier types, banners, five generated battlefields and four formations for RPG, strategy and tactics games.

Army battles drawn in code: soldiers, banners, fields, four formations. Pure GML.

Available on

Search by image

Upload a reference to find previews with similar colors, contrast, and detail.

Battalia: Army Battles for GameMaker

Battalia: Army Battles for GameMaker1 / 9
CSAF — Core Systems Asset Factory · itch.io$9.99
License not indexed
  • i Check the terms on the original listing.
Show full terms

Army battles drawn in code: soldiers, banners, fields, four formations. Pure GML.

A GameMaker army battle system with five soldier types, banners, five generated battlefields and four formations for RPG, strategy and tactics games.

View original listing

Description

Want the whole set? The GameMaker Library holds the CSAF GameMaker assets on one page, plus every new one, for $19.99.

Show full description...

Battalia is an army battle system for GameMaker 2024.14 in pure GML, with a runnable demo room. You declare two armies of regiments (foot, pikes, archers, horse and mages, any number of soldiers), and Battalia draws every soldier, every regimental banner and the battlefield itself, lets the player choose a formation from four cards, then plays the clash out soldier by soldier and hands the survivors back to your code. Inside: 5 arms in 4 poses in any army's colours, banners struck from each regiment's name (16 ordinaries, 14 charges, 4 cloths), 5 battlefields painted from a seed, 4 formations, a war record with the course of the battle charted. Everything is drawn by the package; the only image files that ship are the glyph sheets of its 4 fonts. One commercial licence covers all your games.

Use it for the big battle in an RPG, a kingdom or strategy game's auto-resolve, a war between factions that the player watches and steers, or a tactics game's set piece.

// Create my_battle = bta_scene_create({ title: "The Battle of Ashford", terrain: "meadow", player: { name: "Your Host", army: "foot:44:Iron Company, pike:32:Black Pikes, archer:34:Rivermarch Bows, horse:16:Queen's Own" }, enemy: { name: "The Red Host", army: "foot:50:Crowfoot, archer:30:Sunspears, horse:20:Duskriders" } }); // Step bta_scene_step(my_battle); // Draw GUI bta_scene_draw(my_battle, 0, 0, display_get_gui_width() / 816);

What your players see

  • Every soldier drawn. Foot with sword and shield, pikemen, archers drawing their bows, lancers on horseback and robed mages with glowing staves, each standing, marching and striking in their army's colours, and lying where they fell.
  • Banners from names. Every regiment carries its own banner, struck from its name with real heraldry (the rule of tincture kept): the same name always flies the same arms. The banners ripple over the regiments and lean as a broken regiment runs.
  • A field painted from a seed. Meadow, steppe, snow, desert or moor: hills, a keep on the ridge, a tree line, a cart track, tufts, stones and flowers, never the same field twice.
  • The choice that matters. Four formation cards (line, wedge, square, loose), the enemy's own order shown first. Each beats one other.
  • The clash. Volleys arc overhead and land where they were aimed, spells burst, cavalry charges and pikes stop it, regiments break and run, the fallen stay on the field. Hold a key to watch it three times faster.
  • The war record. Victory, defeat or neither, every regiment's fate (stood, fled, fell), the course of the battle charted with where each regiment broke, and the totals.

What you get as the developer

  • One call for a whole battle (bta_scene_create, step, draw), or the rules alone, headless (bta_battle_create, bta_battle_run, bta_battle_result) for an auto-resolve or a strategy layer.
  • Results in soldiers. A 5,000-soldier army is carried at several soldiers per figure and accounted for to the man: for every regiment, survived + fled + dead = count.
  • Seeded. The same armies, formations and seed replay the same battle, frame for frame.
  • Your sounds, your input. An onEvent callback for every blow, volley, spell, death, charge and rout; drive the formation choice and the fast-forward from your own UI if you like.
  • Balanced, and measured. With the smaller army (32 foot against 40), a wedge against the enemy's line won 17 of 20 battles where copying the line won 0; pikes in a square held horse in a wedge 16 times in 16; identical armies split 14 to 16 over 30 battles.
  • Costs, measured on a real build. At the cap of 480 figures on the field, one battle frame costs 8.8 to 10.0 ms on average to step and 2.1 to 2.6 ms to draw on the VM (two runs); a lower cap costs less.
  • The pieces for your own screens: a regiment's banner as a sprite, a battlefield as a sprite, the soldier atlas in any colours.
  • Raw, commented GML, everything prefixed bta_, a demo room with five battles, and a full Readme. Tested in a blank project from the shipped package.

Compatibility

  • GameMaker 2024.14 and later; built and tested on runtime 2024.14.4.268 (Windows, VM). HTML5, mobile and YYC were not built.
  • Touches none of your resources and leaves your draw state as it found it.
  • The type is Cinzel and Alegreya (SIL Open Font Licence; notices included).

From the same studio

  • Muster: the battlefield a tactics game fights on, drawn per encounter.
  • Crest: factions and reputation with composed heraldry.
  • Armoury: weapons that forge themselves.
  • Drawn in Code: a free GameMaker sampler of three of our systems.
  • Warhost: the RPG Maker MZ edition of this battle system.

Written with AI assistance: the code and the drawing are AI-assisted. Core Systems Asset Factory.

Tags

armyAuto BattlerbannersbattleGameMakergmlheraldrysoldierssourcecodetactics

Downloads