Troop Type Specific Orders

Users who are viewing this thread

xenoargh

Grandmaster Knight
TL:grin:NR version... quit having generic orders for troops.  Different types of troops need totally different orders, if we're trying to simulate Middle Ages warfare.

Long version:

It's pretty apparent that having a one-size-fits-all approach to giving orders wasn't perfect in Warband.  Something like half the playerbase doesn't even know you can give tactical commands to your troops via the F-key orders systems, and even fewer have really exploited it to the fullest. 

Even worse, the Vanilla AI doesn't use it at all and just charges mindlessly.

So... some general thoughts.

1.  What an "order" does, under the hood, should be exposed, extendable C# code on day one.  Not hidden from modders or coders who want to report issues or suggest improvements. 

This is a separate issue from "formations", which I'm sure a lot of people have asked for, but this will often means similar results.  Technically, a "formation" is a sub-set of a given tactical movement or is naturally a part of a tactical movement; the idea that a "formation" is something troops do while standing still is totally incorrect, a lot of tactics involved both moving troops in specific ways relative to one another (a "formation") while moving them in a specific way in regards to the enemy.  Except for really specific defensive formations, this is how it was done historically.

2.  Orders should be explained to all players via a tutorial early on, not left as a power-tool for the hardcore tactical-sim players.

3.  AI opponents should be designed to use tactics with a reasonable amount of intelligence.  For example, an army of sword-and-board infantry with minor archer and cavalry support should be deploying its support on the wings and advancing to charge range under a shield-wall while the supporting archers halt at range.  The supporting cavalry should flank the position of the enemy army and charge only once the infantry's engaged.

Now, on to some specifics.

Cavalry Orders

Cavalry should have a number of specialized commands (the following are just a few suggestions):

A.  Charge and Reform:  Causes cavalry to charge from their current placement position, engage briefly, then return to the placement position in good order.  This is key to shock-cavalry tactics as they were practiced historically and it would stop the AI from mindlessly milling about or having to be incredibly super-powered (IRL, horses can't run over dozens of humans and not break a leg at some point).

B.  Harass:  This would be an explicit call to the "Archer Cavalry" built-in AI in Warband, only more like the real thing.  Cavalry would keep out at max range -25% for their missile weapons and attack with them, but not charge into melee.

C.  Counter-Charge:  Cavalry would charge opposing cavalry, whilst maintaining formation, with the objective of stopping the enemy's cavalry and then pursuing them.

D.  Pursue / Halt.  Instead of cavalry on Charge orders mindlessly milling about, the AI would only complete its current orders and halt if all nearby enemies have been dispersed, or it would be told to Pursue the enemy until destroyed.

E.  Fantasia:  this is a form of cavalry attack used very commonly, where cavalry charge at an infantry formation to 30-50 meters, launch missiles (usually spears / cast lances in the early Middle Ages, then dragons in the late Middle Ages / early Renaissance) and then immediately turn tail and retreat.  This was a very common tactic for cavalry forces used in a supporting role.

F.  Shock Charge:  a proper shock-cavalry charge should be in formation, or, as the English put it during the War of the Roses, "boot to boot".  Not a bunch of guys arriving at random intervals.  A Shock Charge would keep the formation at the speed of the slowest cavalry and all arrive at once.

Infantry Orders

1.  Shield Wall / Phalanx:  A maximum-defensive formation, with each member using its shield to deflect missile fire and spearmen placed in the second rank, to stop cavalry and infantry charges.  Infantry in this formation should be penalized on speeds, as they need to stay next to one another and stay in tight formation.

2.  Receive Cavalry:  The classic tactics to receive a mounted charge, including letting the front rank kneel and push their spear butts against the earth to maximize damage to cavalry, second rank presenting their spears through the first rank, and third+ ranks leaving a little space between themselves and the front ranks, to take down any cavalry that manage to get past the front ranks.

3.  Shock Charge:  Much like a Shock Charge for cavalry, this is a push forward by infantry where all members are expected to stay in formation while advancing together.  Casualties in the front are replaced by soldiers in the rear, who may be contributing missile fire or shield coverage (or both) to the formation.  A charge of this style is a series of slow moves forward, taking the time to clear any enemy from the front of the formation before advancing.  The Romans used this tactic all the time and so did practically every well-trained infantry army in the Middle Ages.

4.  Sprint Charge:  Tactics of the Swiss Pikeman, units of halberdiers, etc., throughout the later Middle Ages; a unit charges at the maximum-possible speed while maintaining a loose series of lines to avoid casualties from missile fire, then tightens to a solid block before impact, to hit as small an area of the enemy's front line as possible.  In Warband, troops with two-handed spears, polearms, etc., etc., were kind of a bad joke vs. missile weapons that were anything like accurately balanced (i.e., no, you can't take 4 arrows on the way in, lol), largely because Charge orders bunched them up into easy targets and any other orders just dispersed them too much to be effective.

5.  Boar's Head:  Viking / Germanic tactic, where the troops assume a spearhead formation and attempt to engage a minimal part of the enemy line while passing through it.  When it didn't bog down, it was effective at breaking unit cohesion.

6.  Dispersed Charge:  Infantry uses the concept of dispersion to avoid missile fire until it's within 50 meters, and then the front ranks close and slow so that the rear ranks, who are closing also, reform into a tight formation to assault the enemy line.  This was a pretty common tactical approach that worked when infantry was well-trained and led.

7.  Envelop:  the opposite of a boar's head; the unit breaks into two smaller bodies and attacks the flanking corners of the enemy formation, often with the objective of either turning the flanks or keeping the enemy busy while another formation began its assault.  Also a good way to finish off an enemy unit, preventing escape.

8.  Counter-Charge:  the infantry unit waits in the current formation, but charges the enemy when they're within 10 meters or so.  This wasn't done often, as it's really risky to lose unit cohesion when the enemy has momentum on their side and it's hard to convince troops to leave a defensive stance in the face of a charge, but it was sometimes used successfully; the psychological impact on the unit charging of seeing their opponent also go on the offensive was sometimes enough to rout a charge.

Archer Orders

1.  Receive Cavalry.  Archers typically used obstacles to receive cavalry; wooden stakes to kill horses were a very popular (and successful) tactic, but sometimes they dug holes, used caltrops, etc., etc.  Essentially, the idea here is that archers, who typically operated with enough dispersion to minimize casualties from counter-fire, had to use something to stop cavalry from wanting to run over them.  Having to pound in stakes, etc. made them a lot less mobile than other infantry, once placed, but these tactics were quite effective against cavalry charges (unlike every video game, ever, cavalry did not magically win against archers all the time; just ask the French).

2.  Disperse / Form Lines / Form Column.  In Warband, the ability to use archers properly was a bit wonky; if you wanted something vaguely like the Real Thing, you'd put archers into a five-row formation and then told them to Spread Out at least once.  This worked all right, but honestly, there's no good reason why you should have to give two orders when one would do.  When archers are moved, we want them in columns to move rapidly, so that we can place them as soon as possible, not wait for stragglers taking the slowest route.  Generally, I think that this should be a toggled state, whereupon giving movement orders automatically results in the unit reforming into a column that then takes the fastest route.

3.  Fall Back.  In Warband, this merely moves the unit back 10 meters or so.  What it should do, with archers, is move the unit back until it's no longer in close contact with enemy forces (>50 meters from nearest enemy formation centroid).  Archers shouldn't require a million micro-managed commands to merely fall back from contact with enemy infantry attempting to close with them, for example.

4.  Receive Infantry:  archers receiving infantry who've managed to close with them are in a real pickle; they can run and hopefully escape being slaughtered from behind, or they can receive the infantry with a close-range barrage of rapid fire and then counter-charge the enemy's front ranks (hopefully after enough of them have taken hits and are distracted).  While is isn't always the best solution, sometimes it worked quite spectacularly in historical battles, where infantry, with their superior armor and shields, expected archers to flee but were instead put to rout.  Technically, this means the archers reform into a three-or-more deep line, with front ranks kneeling, and wait until the enemy's close (75-50 meters) before firing, followed by rapid fire until the enemy's within 10 meters or so, followed by meeting the charge by counter-charging it.

5.  Disperse to Lanes:  an effective anti-cavalry tactic, archers would step 5-10 meters to their right / left as cavalry began a charge, forming lines with large empty lanes between them.  While this formation was useless against infantry charges, it was effective against cavalry, as the horses would tend to pick the empty lanes rather than charge a line and the archers could get off shots at passing horsemen.  Combined with obstacles, this sometimes caused a lot of casualties.  However, it was risky, because a few horsemen could potentially run down the lines, which were too dispersed to support each other as infantry.


Anyhow, the above are some ideas.  There were a lot of different approaches to tactical problems in the Middle Ages, some of which I  haven't covered here, but generally speaking, what I want to see is a more-nuanced and realistic set of tools, so that commanders get some of the real-world techniques that worked, rather than something that barely feels like a combat simulation.

I know that a lot of work on Bannerlord has apparently been spent on making towns and villages more interesting and adding RPG details, but at its heart, it's supposed to be good combat game, and I'd really appreciate more of a nod to realism.
 
I really wouldn't be surprised if that's the case, honestly.  I totally sympathize with TW on that problem; building pathfinding meshes is such a slog  :razz:
 
14. Will battlefield AI (Both the troop AI and the strategic AI) be accessible or hardcoded?
Lowest-level troop AI is hard-coded, but you can customize it somewhat by changing aggressiveness, maximum speed etc. You can also give AI target movement points.

Formation AI and overall battle AI is extendable and modders can add new tactics and AI behaviours.


Clearly, individual troop ai is closed and army battle plan is open, but the area of unit type (infantry, archer, cavalry, horse archer) or order group (troops assigned to order-able groups which may mix unit types) tactics/behaviour is grey. Typical order groups might be medics (non-combatants the player doesn’t want wounded who will reduce casualties if they survive the battle unscathed) and bodyguards (troops to follow, protect and hopefully this time screen the player).

10. How is the code split between hard-coded (engine) and modsys (open to the modding community)? What level of access do we have to the game UI code, AI, etc.? Could you provide us with an example of what will likely remain hard-coded?
Unlike Warband, the vanilla game scripts will not be directly modifiable by modders. However, it will be possible for modders to add new scripts as plugins and also have modifications for XML data files. In Warband, we had the problem that, whenever we released a new version or patch, almost all existing mods would immediately become incompatible with the new version and modders had to go through the lengthy process of reapplying their changes on the new version’s scripts. Moreover, it was impossible for players to run multiple mods in conjunction. The new system will make modders’ lives much easier and also support multiple mods.

By changing XML files, it will be possible to modify or add/delete most types of game objects such as items, characters, factions etc. Of course it will also be possible to add new assets such as meshes or textures.

Modders will be able to add new campaign behaviours, mission behaviours and quests. Campaign behaviours are executed while the player is spending time on the campaign map, whereas mission behaviours are executed when the player is in a scene. For example, if you want to create some extra bandit parties every few days, you can do that with a campaign behaviour.

Modders will also be able to change most of the formulas used in the game. For example, if you want to add a special item that makes you move faster on map, you will add the item through an xml file, and also modify the formula for campaign map speed so that it returns a higher number if a party is in possession of the said item.

Modders who want to change an existing behavior (like party members deserting when morale is low) will have two options: Either they will modify the default formula, or if that’s not adequate for some reason, they will be able to disable the default behavior entirely and add a new one from scratch


Hopefully, the ability to modify mission behaviours will give sufficient freedom to achieve what you suggest as I would hate to only be able to designate a formation shape and a target position for unit tactics.

As this subject is modding specific, TW/Callum, please provide greater clarity and considerably more detail.  It should be sufficiently removed from vanilla Bannerlord to avoid compromising any fan surprises so please be more specific that a normal Dev Blog’s brief overview.
 
xenoargh said:
I know it's late, but hey, they need something for the coders to work on while they get those Scenes done, amirite?  :iamamoron:
+10
1XKCbLr.jpg



Very interesting your argument xenoargh.

If you would allow me to add only one thing to the section on cavalry orders:

G- The torna-fuye or Karr wa-farr was a military technique introduced in the Iberian Peninsula by the Arab armies. After an impetuous charge, before coming into contact with the adversary, the cavalry grouped together and pretended to retreat. This emboldened their enemies, who undertook the persecution, falling into deception and being decimated attack after attack or clamped and annihilated by another enemy group. In the Iberian Peninsula both Muslims and Christians employed abundantly throughout the Middle Ages and also widely used by Normans, peoples of the East - Hungarians, Scythians, Mongols, Turks, etc..

If this tactic were well implemented, a simulation of the "Cantabrian circle" and "Parthian shot" among others infantry Tactics of retreat from Germanic peoples or Rome (Orb, wrap the enemy, Pincer, Nodus, Crown, etc.) could be effectively achieved...


 
Agreed, the false retreat was effectively used by various Mongol, Arab, and other eastern armies to lure an opposing group into chasing them and abandoning their close-order formation.  The fleeing unit would then turn on them, and either charge or pick them apart with ranged attacks, isolated from their usual support.
 
Nice OP.

Adding another layer of depth: limit tactical options available to players/AI until they reach a sufficient tactics skill level and/or read books on the different styles of tactical warfare. Actual execution and efficiency of the formations could be dependent on overall troop quality and commander/sergeant tactical experience.
 
BayBear said:
Nice OP.

Adding another layer of depth: limit tactical options available to players/AI until they reach a sufficient tactics skill level and/or read books on the different styles of tactical warfare. Actual execution and efficiency of the formations could be dependent on overall troop quality and commander/sergeant tactical experience.
+1 to this, and +1 to OP. It really bothered me that the Tactics skill only affected how many troops you brought. It should (in an ideal world where code writes itself), affect every aspect of command. Giving new formations and orders available to high skilled characters would add another great aspect to progression.

What I'd really love to see, is the Tactic skill now change AI command behavior, so maybe your companion is a pompous french knight and he decides to charge his cavalry straight into the filthy Flemish peasants, only to be annihilated by the superior weapon of the middle ages, the GOEDENDAG. Rather than flanking or some other smart move.
 
I think it would be great to see better AI.  Perhaps you can give some instructions on behaviour and let the computer run it.  Rather than having to give precise orders.  I think Dragon Age had something similar, when to heal, when to retreat and all which goes down the drain when the unit is broken.

Would love to see more cowardly troops acting like Myron from Fallout 2.  One dead comrade in a unit of 100, and the whole unit runs away...
 
I think the analytic capability of the AI is highly overestimated. The decision of handmade battlefields makes me think that the AI choices will be held in the domain of AI maps - like the ones for town walkers weighted differently for different branches. So I dont except any earthshaking changes on troop or formation level.
 
Back
Top Bottom