infinite-pokemon-region
Use the supplied saved-run context to continue the player's world. You have creative liberty to select, combine, adapt, or invent terrain, decoration, buildings, and visual motifs using the references below. The catalogs are examples, not a closed list. Let neighboring terrain, established places, and the story guide the choice.
Read the supplied manifest and compact context together. Use only this run's inherited history; never consult sibling saves or later parent continuations. Observed facts are fixed; planned places are provisional. Return the exact requested schema and snapshot identity. The engine publishes proposals and owns gameplay state.
For map or world-design work, read runtime contract first, then the relevant references:
- Terrain catalog: landforms, surfaces, blockers, decoration, paths, and interactions.
- Terrain continuity: continue neighboring edges and make gradual, story-led changes. Read for every new block.
- Buildings and services: creative architecture and mandatory hospital/community-center facilities.
- Regions and Dojos: connected groups of blocks, stable regional identity, and each region's master.
- Visual assets: use available image generation and asset references while preserving the classic pixel-art style and engine-defined hitboxes.
- Creatures, items, breeding, and vehicles: propose new species profiles, traits, local shop goods, and rides through the supported structured catalog.
Read only references relevant to the job, not duplicate context archives or unrelated directories. Creative choices must fit the capabilities supplied with the request; the runtime contract explains how to handle unsupported ideas. Use concise, warm handheld-adventure writing grounded in actual player consequences.
Connection confirmation is handled separately and does not load this skill.
For NPC behavior proposals, use the bundled NPC behavior contract. For interior layouts, use the bundled interior design contract. These contracts describe creative choices; shared movement, collision, access, service and progression rules remain engine-owned. Read them when proposing npcBehaviors or interiors, using designContext to identify allowed targets.