Here are some tutorials and user guide for Terminal Micro Engine!
You can use them to get used to the tool
Another super easy tutorial:
TerminalLog Engine – Ultra-Short User Guide
1. Core structure (what really matters)
{
"title": "...",
"startRoom": "room_id",
"viewport": { ... },
"flags": { ... },
"rooms": { ... },
"events": [ ... ]
}
The important parts:
rooms → where the player moves (descriptions, exits, actions).
flags → the game’s global variables (“power_on”, “monster_alert”, etc.).
events → automatic reactions (timers, global commands).
---
2. Rooms (your main content)
Each room has:
desc → shown with look
scan → shown with scan
exits → north, south, east, west
actions → custom commands for this room
onEnter → auto-executed actions
Rooms are where 90% of your gameplay lives.
---
3. Flags (the MOST important system)
Flags control all logic in your game.
Example:
"flags": {
"power_on": false,
"monster_alert": 0
}
You use flags in:
conditions[] → to check if something should happen
actions → to change values (set, add, toggle)
events → to trigger global reactions
They act like the game’s memory.
---
4. Actions (local commands inside rooms)
A room action looks like:
"listen": {
"conditions": ["flags.power_on === false"],
"actions": [
{ "type": "log", "text": "Something moves..." },
{ "type": "flag", "add": { "monster_alert": 1 } }
],
"onFail": [
{ "type": "warn", "text": "Nothing unusual." }
]
}
If conditions fail → onFail runs.
---
5. Events (global logic)
Two types:
onCommand → react when a specific command is typed
timer → react every X seconds
Example timer:
{
"trigger": "timer",
"delay": 20,
"repeat": true,
"conditions": ["flags.monster_alert >= 1"],
"actions": [
{ "type": "log", "text": "It gets closer..." },
{ "type": "flag", "add": { "monster_alert": 1 } }
]
}
Events + flags = your whole game logic.
---
6. Essential workflow
1. Edit the JSON.
2. Click Validate JSON.
3. Click Apply & Restart.
4. Test in the built-in terminal (look, scan, flags, movement).