Write AI Prompts for a Mercenary-Company RPG

Write AI prompts for a mercenary-company RPG that connect contracts and persistent squad management to working gameplay.

Seele Editorial TeamUpdated November 17, 2026

Define the company and contract board

A mercenary-company RPG can be about recruiting soldiers, leading tactical battles, or negotiating contracts that change the company’s fortunes. A first prompt should choose which part of that fantasy the player manages. This example focuses on contract terms and squad readiness carried from one mission into the next, with a small fixed roster instead of a recruiting or headquarters-management loop.

The fictional Blackbanner Company starts with three members: Bran the Guard, Kestrel the Scout, and Mira the Medic. The company has ten coins, morale of two, and no fatigue. A road escort contract takes two days, requires a Guard and Scout, pays three coins on acceptance and five on successful return, and grants one reputation. A courier recovery takes one day, requires a Scout and Medic, costs one coin to dispatch, and pays five coins at return.

A mercenary captain studies two contract scrolls with a guard, scout, and medic in camp.
Concept art for a fictional mercenary company planning its next contract.

Keep the first slice small. Leave recruitment, equipment crafting, territory control, random contract generation, and a large tactical battle outside the milestone. The player should be able to read a contract, check the required roles and readiness, accept or reject it, dispatch the party, resolve the mission, and review a debrief showing what changed.

Use stable fields for contract ID, duration, required roles, payment timing, deadline, and reputation gain. The company state should track treasury, morale, reputation, roster availability, fatigue, and injuries separately. If the game stores all of these as one general “readiness” score, it will be difficult to tell whether a rest day or treatment action changed the right part of the squad.

Write contract terms as rules the player can inspect

A contract is more than a quest title. Its clauses can change how the company prepares and when it gets paid. Show the role requirements and payment schedule before acceptance. The escort pays an advance immediately and holds the balance until the company returns successfully. The courier contract has no advance and requires a one-coin dispatch fee. Both grant one reputation point after success.

Separate acceptance from dispatch. Accepting the escort adds three coins, but it does not send anyone out. Dispatch checks that the company has the required available members, that neither member has fatigue of two or more, and that the company can pay any dispatch cost. Only after every check passes should the contract become active and the assigned members become unavailable.

{
  "id": "road_escort",
  "durationDays": 2,
  "requiredRoles": ["guard", "scout"],
  "advancePayment": 3,
  "returnPayment": 5,
  "reputationOnSuccess": 1
}

Make the debrief the source of truth for the contract outcome. It should show the contract status, returned party, payment received, reputation change, morale effect, and each member’s new fatigue. In this first example, mission success is deterministic when the role and readiness checks pass. There is no hidden injury roll or combat score to muddy the state trace.

A scout rests beside the company campfire while the medic checks the squad before the next contract.
Mechanism concept: between-contract rest changes persistent squad readiness.

Track fatigue, morale, and availability separately

After a successful mission, each assigned member gains one fatigue. Fatigue is a small integer value. A member at fatigue two or above cannot be dispatched until they rest. One rest day reduces fatigue by one for every member. This rule creates a simple planning decision: the player may send the same experienced Scout again after resting, or preserve the calendar for a different contract.

Morale changes at the company level. A successful escort adds one morale; a failed contract removes one, with a minimum of zero. Reputation records successful contracts and does not replace morale. The first slice has no injuries, so injury state remains a separate field set to false rather than being folded into fatigue. If injuries are added later, treatment can become its own action and cost.

Availability is also separate. Assigned members become unavailable while on a mission and return when the mission ends. A mission in progress should not allow its characters to be assigned to another contract. A rest day applies only to members who are back at camp; it should not shorten a mission or reduce fatigue while the crew is still away.

State these rules before adding mission narratives. A generated story may say that the Scout is “worn out,” but unless the game updates fatigue and availability fields, the next dispatch could still treat them as fully ready. Prompt for both the descriptive debrief and the structured state change.

Trace two contract cycles and a rest day

Start with ten coins, morale two, no reputation, and zero fatigue for Bran, Kestrel, and Mira. Accept the road escort and receive a three-coin advance, bringing treasury to thirteen. Dispatch Bran and Kestrel for two days. At return, the escort succeeds: receive the five-coin balance, add one reputation and one morale, and add one fatigue to both assigned members. The company now has eighteen coins, morale three, and fatigue one on Bran and Kestrel.

Take one rest day. Both fatigue values return to zero, and Mira remains rested. Then dispatch Kestrel and Mira on the courier recovery, paying one coin. When they return, add the five-coin reward, one reputation, and one fatigue to the assigned Scout and Medic. The company ends with twenty-two coins, two reputation, morale three, and fatigue one on Kestrel and Mira. These numbers are a fictional hand trace, not a test result.

EventTreasuryMorale / reputationSquad state
Start102 / 0All rested and available
Accept escort132 / 0Contract accepted; no dispatch yet
Escort return183 / 1Bran and Kestrel fatigue 1; both available
Rest day183 / 1All fatigue returns to 0
Courier return223 / 2Kestrel and Mira fatigue 1; all available
A guard and scout return to camp escorting a supply wagon after completing a fictional contract.
Outcome concept for a fictional contract cycle, not a recorded game result.

Include one invalid dispatch in the prompt test. If Kestrel is at fatigue two, the courier contract cannot leave camp. Treasury, roster availability, morale, reputation, and contract status remain unchanged. The player may choose a rest day or another eligible contract. A clear rejection makes the readiness rule visible before a commitment is made.

Turn contract rules into prototype checks

Build the first version in layers: contract board, roster fields, role/readiness validation, payment timing, mission return, and then rest. Reuse the same contract IDs and values across every prompt. Ask for an event log that shows state before acceptance, after advance, after dispatch, at return, and after rest.

  • Confirm accepting the escort adds only the three-coin advance.
  • Verify dispatch requires both Guard and Scout, available and below fatigue two.
  • Check that assigned members become unavailable while the mission is active.
  • At successful return, add the five-coin balance, one reputation, one morale, and one fatigue to each assigned member.
  • Verify a rest day reduces fatigue by one and does not change treasury or reputation.
  • Check that the courier costs one coin at dispatch and pays five only at return.
  • Reject a dispatch at fatigue two without changing any company state.
  • Keep morale at zero minimum and do not merge it with reputation.

If the advance is paid again at return, separate advance and balance into different contract fields. If the Scout remains unavailable after the mission, update party return before the next dispatch phase. If fatigue falls below zero after rest, clamp it at zero. Small, named checks are easier to reuse when you later add injuries or more contract types.

SEELE’s AI RPG Maker overview gives general context for defining an RPG goal, playable scene, quest objective, and consequential choice. It does not document the fictional company ledger or contract mechanics here. The prompt sequence below is planning material and has not been run in a game builder.

FAQ

What should a mercenary-company RPG prompt define first?

Define the company roster, available contracts, role requirements, dispatch costs or advances, return payments, and which squad conditions persist between missions.

How do contract clauses affect a mercenary RPG?

Make each clause change a tracked rule such as payment timing, deadline, required role, or reputation. Show the clause before acceptance and include its effect in the mission debrief.

How can I make squad condition persist between contracts?

Track fatigue, injuries, availability, and treatment separately. State when each value changes and which camp or rest action can clear it.

Should mercenary missions have random results?

Use a deterministic first contract and explicit readiness checks before adding random outcomes. This makes contract requirements, squad state, and payout easier to verify.

Were these mercenary-company prompts tested in a playable build?

No. The company, contract clauses, and squad state are fictional planning material. The prompts are unrun drafts and no playable build or test results are included.

SEELE AI

Turn this guide into a playable build.

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

Start creating