One park, many connected jobs
A useful way to read the game is to separate four kinds of attention without treating them as isolated modes. Construction determines which slides, pools, and service spaces exist. Direct operations cover the hands-on work of selling food, cleaning, repairing equipment, rescuing visitors, and responding to what is happening in front of you. Management adds staff and guest happiness to that picture. Progression then turns those visible conditions into a park rating that reflects cleanliness, slide fun, food quality, and happiness.
That structure explains why a single narrow tip rarely solves a stalled park. A new attraction can expand what guests can do, but it does not replace cleaning or food quality. More staff can support the operation, but the official material does not provide a universal staffing ratio that fits every layout. The wiki therefore starts with the player’s current task and then links outward to the neighboring systems that the task can affect.
What version 1.0 adds to the fieldbook
Version 1.0 released on July 31, 2026 after Steam Early Access began on August 22, 2025. The launch announcement expands the fieldbook in several directions at once: multiplayer with up to three additional players, a Beach map that requires a new park because layouts do not transfer, Aztec, Sea, and Pirate research themes, custom slide layouts, character customization with five saved slots, new staff categories, night operation, and weather effects that apply bonuses or penalties.
These additions are reflected as separate reference routes only when they answer a distinct player question. Maps and themes remain a focused noindex reference because the official material supports a compact answer rather than a large scenario database. Achievements receive an indexable tracking page because Steam exposes 71 entries as of August 4, 2026, while individual achievement conditions are not reproduced without version-bound evidence. That keeps the site broad enough to be useful without splitting thin facts into artificial pages.
How to use the wiki without losing the park context
Begin with the walkthrough when you want an order of operations. Move to Slides, Park Management, Multiplayer, Achievements, or Updates when the question has a stable standalone intent. Use the shorter Pools, Characters, Research, and Maps references when you need a verified structure, role, count, or release constraint. Every guide keeps a visible source section so that a dated claim can be checked against the official page that supported it.
The site intentionally avoids optimization theater. It does not publish guessed prices, hidden unlock requirements, exact staff efficiencies, slide ratings, or achievement conditions. When official material names a relationship but not a number, the guide tells you what to inspect and why it matters. That approach is slower than filling tables with assumptions, but it produces a manual that remains dependable as the game changes through updates.