AI BEHAVIOR SETTINGS
Player-configurable rules that govern how AI-controlled allies act — priority lists, condition-action pairs, aggression toggles — letting the player program behavior once instead of issuing constant orders.
- SOLO-DEV COST MEDIUM
- TIMING REAL-TIME
- COMMON IN RPG · CRPG · ACTION-RPG
Final Fantasy XII's gambit system is the canonical version: ordered if-then rules ('ally HP < 50% → cast Cura') that players tune into elegant battle programs, and Dragon Age: Origins offers a tactics page of condition slots per companion. Designers use behavior settings to solve the party-management problem in real-time combat — direct control of four characters at once is impossible, dumb AI is infuriating, and scriptable AI turns the frustration into its own satisfying puzzle. It also shifts difficulty from execution to planning, which suits players who enjoy optimization. Key decisions: how expressive the rule language is (too simple and it can't handle real fights; too rich and the UI becomes a spreadsheet), whether rule slots are a progression resource, and what the defaults are — most players never open the menu, so shipped presets carry the experience. Pitfall: making good configurations mandatory rather than optional; if the game is unplayable without an hour of AI programming, players who wanted an RPG got an IDE.