openrct2-park-director

OpenRCT2 Park Director

Standard workflow

1. openrct2_status — confirm bridge + ride-builder connected
2. get_park_overview / park_health_report_tool — baseline metrics
3. Build coasters — survey → plan → build (see below)
4. Verify — capture_game_view and/or advance_time with ticks
5. Remind user to save the park before large AI builds

Coaster build pipeline (survey → plan → build)

1. Poll — coaster_poll_buildable_blocks_tool(x, y, width, height) → flat owned (x,y,z) slots
2. Plan — coaster_plan_build_tool(archetype, mood, near_x?, near_y?) → site, station, track_z, waypoints, circuit segments, feasibility score (no track placed)
3. Build — coaster_execute_plan_tool(plan_json) or one-shot coaster_auto_build_tool(brief=..., archetype=...)

Review the plan before executing on difficult terrain:

Field	Meaning
coverage_ratio	Fraction of site tiles buildable at track_z
build_strategy	rectangle (≤12×12, high coverage), creative, or perimeter
feasibility_probe	Dry-run lift/drop at station — must be ok: true
lift_peak_z / post_drop_z / max_track_z	Energy budget for piece ranking
station_pad	Tile budget: station, exit buffer + lift run east, entrance north, exit south
guest_access	Planned entrance/exit coords + path_route to nearest park footpath
errors	Blockers (probe failed, ring blocked, etc.)

coaster_execute_plan_tool and coaster_auto_build_tool now finish e2e when the circuit closes:

1. Optional pad prep (buy/clear on pad bbox)
2. Track build
3. placeEntranceExit + footpath along path_route + short queue from entrance toward path

RCT2 coaster design rules (enforced in code)

1. Station → flat exit buffer → chain lift (up-slopes, not flat chain) → drop → layout → flat entry buffer → StationEnd
2. Lift apex is the highest point; later hills must stay lower or the train stalls
3. First drop after lift provides gravity speed for the rest of the circuit
4. Small high-coverage sites use rectangle strategy (endpoint-driven corners); larger sites use out_and_back or other creative recipes inside the bbox
5. Track must stay inside the planned footprint (max_track_z caps runaway elevation)