Build Escort Prompts Around Route, Threat and Protection

Use six AI prompt drafts to define an escort action game with a moving route, sentry timing, a one-shot guard and clear rescue conditions.

Seele Editorial TeamUpdated November 17, 2026

Define the Hearthline escort loop

An escort prompt must describe the companion's movement in a way that can be predicted from the player's actions. “Protect the traveler” sets a theme, but leaves open whether the companion follows, waits, gets stuck or rushes into danger. A short route with a fixed movement rule makes the protection decisions easier to prompt and later inspect.

This guide uses Hearthline, a fictional top-down encounter. Yara, the traveler, follows a marked ten-node route from a forest pass to a safehouse. One player character protects her while two sentries fire from fixed positions. Each player turn is one beat, and Yara advances one route node after the action unless the player chooses Call Halt.

A traveler follows a glowing marked path through a forest pass with a protector nearby.
The route is visible so the escort's progress can be read at a glance.

The player chooses Step, Pulse, Guard or Call Halt. Step moves one orthogonal cell. Pulse hits a sentry within Manhattan distance three for one damage. Each sentry has two health. Guard blocks one incoming shot during that beat. Call Halt keeps Yara at her current route node for one beat, but does not stop the mission timer.

Yara has three hearts. Each unblocked projectile removes one heart. The player wins when she reaches node ten with at least one heart. The mission ends in a loss at zero hearts or after twelve beats. Restart returns Yara to node one, restores all hearts and sentry health, resets shot counters and returns the timer to beat one.

Define protection and enemy timing

Threat timing needs an activation condition and a repeat interval. A sentry begins aiming when Yara is within two route nodes of its position. After two beats in range, it fires once at Yara, then repeats every two beats while she remains within that range. A sentry at zero health is disabled and no longer counts down or fires.

Each beat resolves in the same order: player action first; Yara advances or holds; then each active sentry updates its counter and fires if due. Guard stays active through this final phase and blocks one shot, after which it expires. If two sentries fire during the same beat, one Guard blocks only one of them; the other projectile hits Yara. This prevents the protective action from silently becoming an unlimited shield.

PhaseRuleObservable state
1. PlayerChoose Step, Pulse, Guard or Call HaltPlayer position and action
2. EscortYara advances one node unless haltedRoute node
3. ThreatsIn-range sentries count down and fire when dueCounter and target
4. ProtectionGuard blocks one shot then expiresBlocked or landed shots
5. End stateCheck hearts, endpoint and beat limitWin, loss or continue
The protector raises a shield to intercept a bright projectile aimed toward the escort.
Guard has a bounded effect and a clear resolution point.

Keeping the resolution order fixed helps distinguish a failed rescue from an ambiguous update. If Yara reaches the endpoint during the escort phase, the end-state check happens after sentries have resolved that beat. Thus a projectile due on the final route node can still cause a loss before victory is awarded.

Make each player action matter

Pulse and Guard create a simple tactical choice. Pulse can remove a future threat, but only within three cells and only one health at a time. Guard absorbs one immediate projectile but leaves sentries active. Call Halt delays Yara's arrival and threat counters still resolve, so it is useful only when it changes distance or buys a beat for another choice.

For example, if Yara is two nodes from a sentry and its counter is at one, Guard can absorb the shot that is due after she advances. Pulse instead may reduce the sentry from two health to one, but it will remain active and may fire again on its next interval. A second Pulse is needed to disable it. These are implications of the specified rules, not claims about a tested encounter.

Do not add escort morale, pathfinding around obstacles, companion attacks, healing items or randomized target selection in the first version. Each new system changes the route and timing contract. If a later build needs those features, add them as separate prompts with their own visible state and acceptance checks.

Trace an escort beat

Consider a fictional moment when Yara stands at node two and the first sentry is at node four. The sentry is in range and has one beat remaining on its aim counter. The player chooses Guard. Yara advances to node three. The sentry counter reaches zero and it fires. Guard blocks that one shot, then expires. Yara stays at three hearts.

This sequence makes the action order tangible. If the player had chosen Pulse instead, the sentry would lose one of its two health before it fires, but the projectile still resolves this beat because the sentry remains alive. If the sentry had started with one health, Pulse would disable it before the threat phase, so it would not fire. These state branches are a manual rules trace, not gameplay observations.

The traveler reaches a lit safehouse at the end of the marked route with the protector beside them.
Illustrative destination art; no generated game or tested result is shown.

Future checks should record the sentry's health and counter before the player action, then verify whether the shot phase occurs. Also test a beat with two active sentries to confirm Guard blocks exactly one projectile. This gives a reviewer a compact event log rather than a vague impression that the escort felt safe.

Write the six prompts

Use a prompt sequence to introduce the route, protection tools, threat timing, and finish state. These drafts are for Hearthline and have not been run.

Prompt 1: build the route

Create a top-down escort action encounter with a marked 10-node route from forest entry to safehouse. Yara starts at node 1. Put sentries at nodes 4 and 8. The player begins nearby. Yara has 3 hearts; the mission has a 12-beat limit.

Prompt 2: define player actions

Each player turn is one beat. Choose Step one orthogonal cell, Pulse a sentry within Manhattan distance 3 for 1 damage, Guard to block one shot this beat, or Call Halt to keep Yara at the same node for this beat.

Prompt 3: define escort motion

After the player action, move Yara forward exactly one route node unless Call Halt was chosen. The mission timer still advances during Call Halt. Do not let her skip nodes or move backward.

Prompt 4: define sentry timing

Each sentry has 2 HP. It begins aiming when Yara is within two route nodes. After two in-range beats it fires one projectile, then repeats every two beats while in range. A sentry at zero HP is disabled.

Prompt 5: set resolution and outcomes

Resolve each beat as player action, escort move/hold, sentry counters and shots, then Guard blocks at most one shot and expires, then check mission outcome. Each unblocked shot removes 1 Yara heart. Win at node 10 with at least 1 heart. Lose at 0 hearts or after 12 beats. Restart resets all state.

Prompt 6: prepare future tests

For a future build, log beat phase, player action/position, Yara node, sentry HP/counters, shots, Guard state, hearts and remaining time. Check Guard with one and two shots, Pulse disabling a sentry, Call Halt, endpoint resolution and Restart. Do not say a check passed until observing a real build.

SEELE's official page describes general plain-English prompting, a playable first version, browser testing and follow-up refinement. It does not verify Hearthline or its rules. See Free AI game maker for general workflow context.

Prepare future build checks

Use an event log with one row per beat. Capture the player action, Yara's node before and after, each sentry's health and counter, whether it fired, Guard state, hearts remaining and the mission timer. A short log makes it possible to compare actual event ordering against the prompt without claiming that the design itself has been implemented.

Future checkExpected ruleEvidence
Escort paceOne node forward each beat unless HaltNode before/after and action
Sentry activationStarts aiming inside two nodesDistance and counter
Guard scopeBlocks one shot then expiresShot count and Guard state
Pulse resultOne damage; zero HP disables threatSentry HP and shot phase
Win/loss and restartEndpoint/heart/timer rules resolve in orderOutcome and reset snapshot

The rules also create one edge case worth preserving: an endpoint arrival does not bypass a shot scheduled during that same beat. If product intent changes this priority, change the resolution contract and update the prompts and tests together. No prompt run or playable test is included here.

Frequently asked questions

What should an AI prompt define for an escort action game?

Specify the companion’s route and pace, how threats attack, what protective actions can block damage, the escort health limit and the win/loss states.

How does Yara move in the Hearthline example?

Yara advances one marked route node after each player beat, unless the player uses Call Halt to keep her in place for that beat.

How does Guard protect the escort?

Guard blocks one incoming sentry shot during that beat, then expires; it does not damage or disable the sentry.

Were the escort prompts tested in a playable game?

No. Hearthline is a fictional rules example. The prompts are unrun and no playable output or observed test is included.

What should be checked in a future build?

Record action order, escort node, sentry cooldowns, blocked shots, hearts and timer to verify that the route and damage rules resolve consistently.

SEELE AI

Turn this guide into a playable build.

Start with a focused brief, then iterate in the Seele AI Workspace.

Start creating