Waterpark Simulator 1.0 organizes its major theme progression into three named branches: Aztec, Sea, and Pirate. CayPlay’s launch post says the Museum contains three NPCs with separate questlines, that each line awards its own currency, and that the corresponding research branch ends in a massive slide.
That structure is verified. Exact NPC names beyond publicly exposed achievement text, quest steps, currency names, node costs, choices, and full item inventories require a live release-build capture. This guide provides a recording and decision method without filling those gaps with guesses.
Start at the Museum interface
Visit the Museum in the current park and inspect each available interaction. Record the displayed NPC name, questline label, reward icon, and any prestige or research prerequisite. Preserve screenshots before accepting a task.
Keep one worksheet per branch. Mixing rewards creates confusion later because the official release explicitly describes one currency per questline. Use the icon and live label rather than calling every reward a generic token.
The Museum guide covers safe quest documentation and the boundary between confirmed structure and unreleased detail.
Map each quest to one branch
When a quest is accepted, capture its displayed objective and current progress. After completion, record the reward exactly as shown and check which research balance changed. This connects quest evidence to the branch without relying on visual theme alone.
Do not infer the full sequence from one task. A quest may unlock another task, a currency amount, or a research opportunity, and the current game should show which occurred.
Steam’s achievement list publicly names Yogi quest milestones at three, four, and five stars. Those descriptions verify named progression goals, but they do not reveal every Museum NPC, objective, or reward. Keep achievement evidence separate from assumptions about the whole branch.
Build a branch ledger
For Aztec, Sea, and Pirate, maintain five fields: completed quests, available branch currency, unlocked research nodes, placed construction items, and next displayed requirement. Add version and date to every exact amount.
This ledger makes a stalled branch diagnosable. You can distinguish a missing quest from insufficient currency, a locked prerequisite, or an unlock that has not yet been placed.
Avoid converting currencies into a shared value unless the game provides an exchange. The official announcement emphasizes separate questline currencies.
Decide which branch to advance first
Choose according to the park’s current plan. If a district already has room for one theme, progress that branch until it provides a testable build. If you are still learning the Museum, advance the questline whose live objective fits ordinary operation.
Do not claim one branch is universally fastest or most profitable without a controlled 1.0 comparison. Quest tasks, costs, and rewards were not fully documented by first-party text.
Preserve cash and space for the resulting construction. Unlocking a branch-ending slide does not guarantee the current park can place and service it.
Verify research unlocks immediately
After spending branch currency, inspect the build catalog or capability named by the node. Place a small representative object in a test zone and confirm that the unlock persists after saving and reloading.
If it does not appear, check category filters, map, prerequisite connections, and the exact branch selected. Preserve evidence before spending more currency.
The research guide explains how to capture dependency lines. For layout, use the theme building guide to keep paths and maintenance access intact.
Prepare for massive slides
Each branch culminates in a massive slide, but the official post does not publish its footprint or construction constraints. Keep an expansion direction available rather than reserving an arbitrary fixed rectangle.
When the node becomes visible, capture its prerequisites and current placement preview. Save before purchase and before rebuilding a working district. Test the start, route, endpoint, guest access, and service path before decorating around it.
Do not assume the three final slides have identical size, cost, or performance. Record each one independently.
Handle spoilers responsibly
Quest details and late-branch rewards can be spoilers. Put exact task and outcome information under clearly labeled headings once verified. Keep the introductory route useful without revealing surprises that CayPlay’s announcement intentionally leaves unexplained.
If a choice appears, save before selecting it and record the exact text. Do not promise that a choice is reversible or that another player receives the same outcome unless tested.
This is especially important in multiplayer. Official notes allow existing parks in co-op but do not establish quest ownership, reward sharing, or simultaneous NPC interaction.
Recheck after patches
Theme progression is a high-volatility 1.0 system. After an update, compare quest labels, currency icons, research costs, branch connections, and final-slide availability against the ledger.
Keep historical values dated instead of blending them with current information. The durable answer is how to verify a branch; the exact sequence should be published only from a captured live version.