Whoever answered with things like "learn2program" is an ass. The poster wants an example architecture/grammar for scripting behavior in a general way, not snarky remarks.
Data-driven state machines are a straightforward way to go. Once the engine that executes that stuff is programmed, you can create new enemies pretty easily and reliably.
1) figure out what types of actions you need (shoot a laser, start flying)
2) figure out what types of triggers you need (player within 10 meters, enemy health at 50%)
3) determine your grammar using some pre-existing data format (Lua if you're hardcore, XML if you're familiar, JSON if you're in the know)
4) sketch out a few example scripts
e.g.
<enemy id='20' name='Trogdor'>
<attacks>
<attack id='burninate'>
<triggers> <healthBelow value='50%' /> </triggers>
<actions> <shootBreath target='player' /> <gotoAttack id='landing' /> </actions>
</attack>
<attack id='landing'>
<actions> <playSound id='rawr.wav' /> ... </actions>
</attack> </attacks> </enemy>
5) program the interpreter
Do whatever works. Don't try to make some super-extensible system or it'll take forever.
Developer
