CayPlay’s version 1.0 announcement confirms an optional Mafia questline involving dubious loans. The developer deliberately does not publish its terms, branches, rates, penalties, or outcomes in the launch summary. Any page that supplies those details without a live capture would be inventing the answer.
Use this guide to enter the questline safely and document what the current game actually presents. Exact spoilers should be added only after a controlled public-build playthrough.
Confirm that you found the released questline
Check that Steam is running base AppID 3293260 on the current public build. When the Mafia content appears, capture the NPC or event name, the full prompt, current park state, and any prerequisite the interface displays.
Do not identify unrelated loans, mods, or community role-play as the official quest. The source must be the base game’s own 1.0 interaction or a CayPlay-authored update.
Record difficulty, map, prestige, and date. Those fields help determine whether the same trigger is reproducible.
Back up before accepting a loan or choice
Close the game cleanly and follow the backup-first process on the save recovery page. Keep an untouched copy labeled with the quest state and date.
A backup protects against corruption or accidental overwrite; it does not prove that the quest supports save-scumming or that every consequence reverses cleanly. Steam Cloud may synchronize changes, so understand where the preserved local copy is stored before proceeding.
Do not test an unknown financial choice on the only copy of a long-running park.
Capture financial terms exactly
If the quest offers money, debt, repayment, interest, a deadline, collateral, or another obligation, transcribe only what the interface states. Take before-and-after screenshots of cash and any new quest tracker.
Avoid calculating a rate from an incomplete display. Do not call a payment recurring, timed, or optional unless the game shows or repeatedly demonstrates it.
Keep the loan separate from ordinary park revenue and expenses in your ledger. The money guide provides a baseline that helps identify which balance change belongs to the quest.
Record decisions without predicting outcomes
For every choice, write down the exact options before selecting one. Note the immediate result, new objective, dialogue, and any change to money, research, staff, guests, or park operation.
Do not label one option “best” based solely on its immediate reward. A later consequence may exist, and the launch post intentionally withholds the story detail. A reliable comparison requires separate backed-up branches or independent playthroughs on the same version.
If the interface does not allow a choice to be revisited, report that observation for the tested state rather than claiming universal irreversibility.
Keep spoilers behind clear labels
The safe public summary is short: version 1.0 contains an optional Mafia questline and dubious loans. Triggers, dialogue, terms, choices, and endings belong in a clearly marked spoiler section once verified.
Use progressive disclosure in notes. Put prerequisites and backup advice first, then a warning, then the exact walkthrough. This lets players find technical help without losing the surprise CayPlay preserved.
Do not use an achievement name or global completion rate to guess a secret outcome. Steam’s public achievement data can have blank or concise descriptions.
Test multiplayer behavior separately
The release supports loading existing parks with up to three other players, but the announcement does not say who can accept a quest, whether decisions are host-only, or whether rewards are shared.
Before co-op testing, agree that no one interacts with the quest NPC until the host has backed up. Record who initiated the interaction, what each client saw, and which save changed after the session.
Do not generalize one host/client result to host migration, cross-save, or dedicated-server behavior. Those features remain unverified.
Diagnose a stalled quest
Review the last displayed objective and return to the relevant location. Check whether a prerequisite, time condition, resource, or park state is explicitly shown. Save screenshots of the tracker and interaction point.
Do not spend money, delete structures, or repeat random actions based on an unverified walkthrough. If the state appears broken, restart from the clean save once and reproduce the shortest sequence.
For a repeatable public-build defect, use the official links to reach CayPlay support. Provide version, save state, the exact last successful step, and the evidence requested by the pinned support instructions.
Publish only verified branches
A complete future walkthrough should bind every step to a source screenshot or captured game state, identify semantic version and difficulty, distinguish immediate from delayed outcomes, and mark multiplayer findings separately.
Until that evidence exists, stopping at the boundary is more useful than filling the gap. The quest is confirmed; its hidden details are not.