MACRO RECORDING
Recording a sequence of player actions for automated replay — programmable routines captured by demonstration rather than written in code.
- SOLO-DEV COST MEDIUM
- TIMING REAL-TIME / TURN
- COMMON IN AUTOMATION · SIM · MMO · SANDBOX
Final Fantasy XIV's crafting macros let players script rotation sequences, factory and automation games flirt with record-and-repeat for repetitive build tasks, robot-programming games like Autonauts make teach-by-doing the core loop (perform the task once, the bot repeats it forever), and emulator/speedrun tool-assisted traditions run the concept at the frame level. Designers add macro recording because it's programming without syntax: players who would never touch a script editor will happily demonstrate a task, and the record-replay loop converts mastered, solved activities into delegated ones — the same promotion-from-laborer-to-manager arc that automation genres sell, reached through imitation instead of engineering. Key decisions: how literal the replay is (exact input playback breaks when context shifts; action-level recording like 'chop nearest tree' generalizes), whether recorded routines can be edited, looped, and branched after capture (the growth path from macro to program), and what's out of bounds — combat macros in multiplayer are a botting policy question, not a feature question. Pitfall: brittle replays — a macro that desyncs the moment inventory is full or an object moves teaches players their delegation can't be trusted, and distrusted automation is worse than none, because now they're doing the task and supervising it.
SEEN IN
- AUTONAUTS
- FINAL FANTASY XIV
- STORMWORKS