Pick the brief that lets you review third-person movement, tool select and use, plant, water, harvest, interact, dialogue choice, inventory, map, sleep, pause, and save or follow state through calendar and time, crop growth, soil state, tool targeting, item inventory, NPC schedules, relationship variables, requests, market prices, weather, and persistence. Every Unreal Farming and Life Sim Game Maker CTA carries the Unreal engine, this source page, its intent, and campaign attribution into the same generation workflow.
Playable vertical slice
Create Unreal Farming and Life Sim Game Maker as a native Unreal 5 slice: wake at the farmhouse, prepare two plots, plant and water crops, visit the village market, complete one neighbor request, sell produce, sleep, and inspect the next day. Place it in an original warm valley homestead with farmhouse, two crop plots, tool shed, footpath to a small village market, stream, and changing evening light. The build passes only when daily state advances once, crops follow water and growth rules, NPCs remain reachable on schedule, transactions conserve items and currency, and reload resumes the correct day. Keep the Unreal Farming and Life Sim Game Maker slice previewable, profile its representative load, then prepare both package and project outputs.
Use this promptControls and camera
Greybox an original warm valley homestead with farmhouse, two crop plots, tool shed, footpath to a small village market, stream, and changing evening light around these player inputs: third-person movement, tool select and use, plant, water, harvest, interact, dialogue choice, inventory, map, sleep, pause, and save. For the Unreal Farming and Life Sim Game Maker movement and interaction pass, leave an auditable state trail; delay visual polish until failure and restart behavior is clear.
Use this promptStateful game systems
Represent calendar and time, crop growth, soil state, tool targeting, item inventory, NPC schedules, relationship variables, requests, market prices, weather, and persistence as observable state in the Unreal Farming and Life Sim Game Maker project. Connect each transition to wake at the farmhouse, prepare two plots, plant and water crops, visit the village market, complete one neighbor request, sell produce, sleep, and inspect the next day, expose it in the browser build, and mark the Blueprint, C++, asset, or configuration assumption that still needs editor inspection.
Use this promptRegression and packaging
Run a regression build for cozy-game teams validating daily routines, crops, relationships, schedules, and persistence. Prove that daily state advances once, crops follow water and growth rules, NPCs remain reachable on schedule, transactions conserve items and currency, and reload resumes the correct day, then deliberately trigger this risk: a cozy presentation can mask irreversible missed schedules, runaway time, crop desync, duplicated sales, inaccessible NPCs, or save-state conflicts across daily systems. Preserve a rollback point, repeat the same test, and keep the unreal farming and life sim game maker slice previewable, profile its representative load, then prepare both package and project outputs.
Use this prompt