Boss: Mechaqueen

[ntseng]

HP: low for boss Element: Earth Comes with n mechabees

Actions:

• Swarm Protocol - Priority, no target, user gains 100 block, change the move of allied mechabees to "call for help"
• Assault Protocol - Priority, target one delver, user gains 100 block, change the move of allied mechabees to "Sting" on this move's target
• Sacrifice Protocol - Priority, target one mechabee, user gains 100 block, user gains 100 block, change move of target mechabee to "Self-Destruct"
• Emergency Protocol - Priority, target none, user gains 100 block, summon 1 mechabee
• V.E.N.O.Missile - target one delver, deal X damage and Y Poison

Schedule:

1. V.E.N.O.Missile
2. random protocol

[ntseng]

Though the base mechabee has an example of how to summon more enemies into combat, that implementation causes a circular dependency in this case.

[ntseng]

Though the base mechabee has an example of how to summon more enemies into combat, that implementation causes a circular dependency in this case.

Summoning other enemies can probably be made possible by moving action logic into its own dictionary, then keeping string keys of the actions in the enemy files instead of keeping the logic in the files themselves (similar to getting move logic from the equip dictionary). An action dictionary is likely a superior architecture anyways (allowing making Punch less of a special case, and players using enemy moves if game design finds use for that).

[ntseng]

Alternatively, the circular dependency can be side stepped by having the Mechaqueen order the Mechabees to do the summoning (which is somewhat more flavorful anyways)

[ntseng]

If no mechabees are present, maybe a protocol round should be overwritten by summoning 1 mechabee?