In a small valley, summer exposes a shallow ford and a repairable footbridge. Autumn floods the river; winter freezes part of it. There are no character classes. Two forage actions unlock fieldcraft, while two repair actions unlock mending. The route and the skills earned both shape the next season.
Make the seasons change the map
Use one valley map with a river, a shallow ford, a footbridge and a village. In late summer, both crossings work. After the autumn flood, the ford is impassable and a bridge left unrepaired loses a plank. In winter, the river edge freezes, opening a short but risky crossing.
Show the season in the scene and update route markers when it changes. Keep the village and resource nodes fixed so players can compare the same map across seasons.

Unlock abilities through repeated actions
Give the character a small action log instead of a class menu. Two forage actions unlock fieldcraft, which reveals a safe berry route. Two repair actions unlock mending, which restores the missing bridge plank before winter. Show progress after each action and let the player keep both abilities.
Actions should answer a current need as well as build toward a skill. The player can forage for supplies or repair the crossing before the flood, but has only two actions before autumn arrives.

Replay the flood with two action plans
The deterministic replay gives the player two late-summer actions. The forage-only plan unlocks fieldcraft and supplies but leaves the bridge unrepaired. After the flood, the winter crossing is longer and fieldcraft reveals a safe berry detour. The repair plan unlocks mending, restores the bridge and reaches the village directly, but collects fewer supplies.
Reset the same starting season, action count and flood event to compare the plans. The replay checks action thresholds, bridge state and route availability. A future human playtest should test whether each trade-off feels meaningful.

Prompt AI for one seasonal valley quest
Start with three seasons, two crossings and two action-earned abilities. Add regions only after the route and growth changes are easy to read.
Create a classless RPG quest in one valley with a river, ford, footbridge and village. Late summer has two working crossings. The autumn flood closes the ford and removes a plank from an unrepaired bridge. Winter freezes part of the river. Two forage actions unlock fieldcraft and reveal a safe berry route; two repair actions unlock mending and restore the bridge. Give the player two actions before the flood, show seasonal route changes, skills and reset.
SEELE's free game maker describes starting from a text prompt and refining a first version with follow-up requests. Use this quest to inspect route changes and action-earned skills before adding regions.
Start the seasonal classless RPG prototype in SEELE
Frequently asked questions
How can progression work without character classes?
Tie abilities to repeated actions the player chooses in the world. A small threshold, such as two forage or repair actions, is easy to see and test. Keep the ability list short at first so players understand how their choices changed what they can do.
Should the map change completely in every season?
Keep landmarks fixed and change a few routes, resources or hazards each season. Players need to recognize the same valley to plan around the new conditions. Start with the ford, bridge and frozen river edge before adding more seasonal systems.
How do I compare seasonal plans fairly?
Reset to the same season, action count, map and flood event for each replay. Compare the skill unlocked, bridge state, available route and supplies. A human playtest is still needed to judge whether the trade-off feels meaningful rather than merely correct.


