Define one guild cycle before building a campaign
A guild-management RPG can combine recruiting, character stories, mission planning, base upgrades, and combat. A first prompt that asks for all of them at once often returns a broad design with no clear way to check whether the roster or mission rules work. Start with one guild hall, one short mission, and a cycle that connects party choice to a cost and a reward.
This fictional example begins with six coins and two adventurers: a Scout and a Medic. The guild hall has room for three members. Recruiting another adventurer costs two coins. A two-day mission requires one Scout and one Medic, costs one coin to dispatch, and awards five coins when completed. At the end of each guild cycle, the guild pays one coin per roster member. These values are invented for the example; they are not balanced or tested gameplay.

Keep the first milestone focused on the guild loop: review available adventurers, recruit if desired, assign a valid party, pay the dispatch fee, resolve the mission, collect the reward, and pay upkeep. Leave combat tactics, crafting, hall expansion, random missions, and character romance out until this loop produces consistent state updates.
Use the same step names throughout the prompt sequence. If “dispatch” means the party leaves the hall, say when assigned characters become unavailable and when they return. If “cycle close” means upkeep is due, use that phrase consistently instead of alternating between day-end and mission-end. A vocabulary table can prevent the game logic from treating these as separate phases.
Model roster members and mission roles
Give each adventurer a stable ID, role, upkeep, and availability state. Here, the Scout satisfies the mission’s route-finding requirement and the Medic satisfies its injury-prevention requirement. These are specific contributions, not universal bonuses. The Scout does not make every mission cheaper; the Medic does not prevent all damage across the campaign.
A simple record might look like this:
{
"id": "scout_01",
"role": "scout",
"available": true,
"upkeepPerCycle": 1,
"contribution": "satisfies_route_finding"
}
Store the guild roster separately from the mission party. A member can be in the roster but unavailable because they are on an active mission. When they return after two days, mark them available before the next assignment. This distinction prevents an adventurer from being assigned to two missions at once, even though this first slice includes only one mission.

Validate assignment before changing state. The party must include exactly one Scout and one Medic. Each chosen member must be available, no ID can appear twice, and the party cannot exceed the hall’s roster or mission size limit. If the player tries to dispatch a Scout alone, show the missing Medic requirement and leave treasury, roster, and availability unchanged.
Recruitment should update the roster only after payment succeeds. With six starting coins, hiring one new member costs two and leaves four. The new member occupies one of the three roster slots and adds one coin of upkeep at the cycle close. This tradeoff makes recruitment a meaningful choice: the larger roster adds flexibility for later missions, but it costs more to maintain.
Set dispatch costs, mission timing, and upkeep
Resolve the mission in a fixed order. First validate roles, availability, capacity, and payment. Then subtract the one-coin dispatch fee and mark assigned members unavailable. Advance two mission days. Resolve the fixed mission result and grant five coins. Mark the party available again. At guild-cycle close, subtract one coin per roster member. This order avoids charging upkeep before the reward or returning the party too late for the next cycle.
For this first pass, the mission result is deterministic once a valid party is dispatched. Do not add a random injury roll or a chance of failure. Random outcomes can come later, after the core assignment and state transitions work. A prompt should also say what happens if the guild cannot afford the dispatch fee or upkeep: reject the action or apply a clearly defined consequence, but do not silently allow negative coins.
Ask the builder to maintain a compact state object:
{
"treasury": 6,
"rosterCapacity": 3,
"members": ["scout_01", "medic_01"],
"activeParty": [],
"missionDaysRemaining": 0
}
Keep the mission result, returned-party state, and financial ledger visible. If the mission is complete but the Scout remains marked unavailable, the next cycle will behave as though the party never returned. If the reward is applied twice, the ledger will reveal the duplicate event. An event log is a practical design prompt even before a polished interface exists.
Trace one mission cycle by hand
Begin with six coins and two roster members: Scout and Medic. Recruit one additional adventurer, spending two coins and leaving four. Assign the Scout and Medic to the mission; the third member stays in the hall. Dispatch costs one coin, leaving three. After two days, the fixed mission succeeds and awards five coins, bringing the treasury to eight. The party returns and becomes available. At cycle close, all three roster members cost one coin each, leaving five.
The same trace should include a failed assignment. If the player sends only the Scout, the game explains that the Medic role is missing and changes no state. The treasury remains six before recruitment, the Scout remains available, and no mission timer starts. This makes validation observable instead of treating an invalid button press as a hidden partial action.
| Step | Roster / party | Treasury | Availability and result |
|---|---|---|---|
| Start | Scout, Medic | 6 | Both available |
| Recruit | Scout, Medic, third member | 4 | All available |
| Dispatch | Scout + Medic assigned | 3 | Party unavailable; mission takes two days |
| Return and reward | Party returned | 8 | All three available; +5 reward credited |
| Cycle close | Three members retained | 5 | −3 upkeep applied once |

This is an expected hand trace, not evidence that the system has been implemented. The prompts in this article are unrun drafts and no playable build or test result is included. If you run them in a builder, compare the treasury after every event and record whether availability changes at dispatch and return as expected.
Turn the prompt sequence into checks
Build in layers. First define the roster and capacity. Next add recruitment and payment. Then validate mission roles and availability. Add the fixed mission timer, reward, and cycle upkeep after the assignment state works. Keep random events and upgrades disabled so a mismatched coin total can be traced to a specific step.
- Confirm the roster never exceeds three members.
- Reject recruitment when the hall is full or the treasury is below two coins.
- Reject an incomplete mission party without changing treasury or availability.
- Confirm dispatch subtracts one coin and marks only assigned members unavailable.
- Advance exactly two mission days before applying the fixed reward of five coins.
- Return the party to available state before the next mission cycle.
- Subtract one coin per roster member exactly once at cycle close.
- Test low treasury and duplicate assignment without allowing negative currency or duplicated members.
If the output applies upkeep each mission day, clarify that upkeep is charged once per guild cycle in this example. If the mission reward arrives before completion, restate the two-day timer. If an invalid party still loses the dispatch fee, make validation a prerequisite that happens before any cost or state mutation. Tight prompt revisions are easier to inspect than a wholesale rewrite.
SEELE’s AI RPG Maker overview provides general context for planning an RPG around a character goal, playable scene, quest objective, and consequential choice. It does not document a guild-management feature or the example’s roster and upkeep rules. Use it as broad planning context and verify any generated behavior in the tool you choose.
FAQ
What should a guild-management RPG prompt define first?
Define the guild goal, roster limits, recruitment cost, mission requirements, reward rules, and when upkeep happens. Keep one short cycle small enough to trace.
How do I make adventurer roles matter in a guild RPG?
Give each role a clear mission contribution and state which mission requirements it satisfies. Avoid broad bonuses that apply everywhere unless the rules specify their scope.
Should a guild mission use random outcomes?
A first prototype is easier to inspect with fixed mission requirements and deterministic outcomes. Add uncertainty only after party assignment, costs, and rewards update correctly.
How can I prevent sending an invalid party?
Validate party size, role requirements, availability, and payment before dispatch. If a check fails, explain the unmet requirement and leave the roster and treasury unchanged.
Were these guild-management RPG prompts tested in a playable build?
No. The guild cycle, roster, and mission are fictional planning material. The prompts are unrun drafts and no playable build or test results are included.


