Draft AI Movement and Attack Flowchart

[jam]

Draft AI flowchart - Darts welcome.

I'm from the board game side so go easy on me!

dcmoveattackflowchart.pdf (49.65 KB)

[mister frau blucher]

Hey, jam,

Thanks for putting this together! No worries about being from the board game side - LAW and its antecedent TFT are "tactical RPGs" or hybrid rpg-board game so it is all good, man.

This looks more useful than I was originally thinking it could be - really nice work.

I do have a few comments:

1. The big comment - Keep in mind you cannot move and fire your missile weapon in the same turn (except for thrown weapons). Given that, there does not seem to be any differentiation between archers and melee enemies initially. I say this because the initial "No" has you moving toward PCs to attack, while the second "No" is clearly for archers.

2. The Yellow square would indicate the end of the turn for archers, as they cannot move and fire the same turn (except for thrown weapons). The branching from this spot seems to confuse melee and archer enemies, and the turn they are on? Maybe I am misreading.

3. Nitpick - it should be "PCs" rather than "PC's" unless I am again missing something? PCs is plural, not possessive or a contraction. The exception is the first "Yes" off of the yellow square - this would be possessive for a single PC and correct.

But I really like the direction this is heading in!

Bret

[jam]

Thanks for the feedback, Bret.

 

It sounds like the AI Wizard/Archers don't move much if at all during combat so that should simplify things.

Not sure if there would be times when the Wizard/Archer would rather move than attack?

There's probably some things that could be added - using cover, maybe a bodyguard mode where an AI prioritizes protecting his boss rather than himself. But hopefully I'm understanding the basic movement protocols.

Attached is a 2nd version - for review, of course!

AI_flowchart_v2.pdf (118.29 KB)