Back to the park

Support

Something broken, a question about a saved park, or an idea for a ride we have not built yet - there is one address for all of it and a real person on the other end. This page answers the things people ask most, and tells you what to send if it is a bug.

Last updated: 4 September 2026

Getting help

One inbox, no ticket system, no account to make.

Write to us

info@corbata.games reaches the person who makes the game. Anything at all: a bug, a question, a suggestion, or a park you are proud of.

We answer in a few days

Corbata Games is small, so it is days rather than minutes - but every message gets a reply, and a bug report gets one even when the answer is "found it, fixing it".

Bugs are welcome

Half of what is in the game was fixed because a player noticed something odd and said so. The checklist below is what makes a report easy to act on.

Not on sale yet

The park is still under construction, so there is nothing to install today. This page is here for when there is - and for anything you want to ask in the meantime.

1. Reporting a problem

Send it to info@corbata.games. There is no form to fill in and no account to make - an ordinary email is fine, and a short one is better than none at all. If you can, put these five things in it:

1

What happened, and what you expected

"The queue for the teacups emptied itself when I saved and loaded" tells us far more than "queues are broken". The difference between the two is usually the whole bug.

2

What you were doing just before

Building, demolishing, loading a save, changing the game speed, coming back after leaving it running. Most faults live in the step before the one you noticed.

3

Your device and the version

iPad model, or your computer and its operating system, plus where you bought it - Steam and the App Store are not always on the same build.

4

A screenshot, if there is anything to see

A picture of a ride in the wrong place, a guest standing somewhere impossible or a number that looks wrong saves a great deal of guessing on both sides.

5

The saved park, if it only happens in one

This is the one that turns a puzzling report into a fixed bug in an afternoon. Section 2 says where the files are; attach the one park rather than the whole folder. A save describes a made-up theme park and nothing about you - see the privacy policy - and we delete it once the fault is found.

If the game will not start at all

Restart the device first - it is worth the thirty seconds and it fixes a surprising share of it. Then check there is room on the disk, and that the operating system is at least the version in section 5. If it still will not open, write to us and say which of those you tried; do not reinstall yet, because reinstalling removes your saved parks along with the game.

2. Your saved parks

Every park you save is one file on your own device, and you can keep as many as you like - they do not overwrite each other. There is no cloud account behind them and nothing is uploaded anywhere.

Where the files live depends on the platform:

PlatformSaved games are kept in
iPadOSthe app's own Documents folder, inside the app's sandbox, in a Saves folder
macOS~/Library/Application Support/Corbata/Amusement Factory/Saves
Windows%USERPROFILE%\AppData\LocalLow\Corbata\Amusement Factory\Saves

The game saves itself as you play

Alongside the saves you make yourself, the park keeps its own rolling backup - by default every five minutes, into three files that take turns, so there is always more than one moment to go back to if something goes wrong. How often it does that is yours to set in Settings → Saving, from every three minutes to every ten, or off altogether. Autosaves never overwrite the park you saved by hand.

Backing them up, and moving them

Copy the Saves folder anywhere you like - that is the whole backup. Putting those files into the same folder on another computer is also how you move a park across, as long as it is the same game. The files are compressed and are not meant to be opened or edited by hand; a file that has been changed outside the game is refused when you try to load it, which is deliberate and not a fault.

On an iPad, the parks are inside the app's sandbox, so a device backup to iCloud or a computer takes them with it. Deleting the game deletes them too, and we have no copy - so if a park matters to you, back the device up before you remove anything.

3. If it runs slowly

A big park with a full crowd is the heaviest thing the game does, and a fanless tablet feels it first. Three settings are worth knowing about, all of them in Settings - from the main menu or from the menu in the top right of the park - and all of them remembered.

SettingWhat it does
Frame cap
30 fps, 60 fps or uncapped
It ships at 30 on every platform on purpose: nothing in a park builder is judged on reaction time, and a game that holds 30 steadily reads better than one swinging between 120 and 70 - on an iPad it is also roughly half the battery. If your machine has room to spare, 60 is two taps away.
Crowd
every guest, half, or a quarter
Simulates half or a quarter of the visitors and counts each of them for two or four, so the park still fills up, still takes the same money and still hits its goals at the same rate - it just has fewer people to walk about. Leave it alone unless the park judders; it defaults to one guest being one guest.
Autosave
off, 3, 5 or 10 minutes
Saving a very large park costs a brief pause. If you feel it, five minutes is the default and ten is quieter still.

Beyond that: the game speed buttons make the park busier rather than the machine slower, so 3x on a device that is already struggling is the wrong direction. And if the park slows down over a long session rather than being slow from the start, that is worth an email - it is a different problem from a heavy park and we would like to see it.

4. Controls

Touch, mouse and keyboard and a game controller all work, at the same time, and the game words its own hints for whichever one you last used.

Touch

One finger builds and selects, two fingers pan, pinch to zoom. Because there is no hovering on glass, the building tools let you aim a piece first and put it down with a button - so you can see which way a corner runs before you pay for it.

Mouse and keyboard

Click to place, R to turn a piece, the edges and the arrow keys to move the camera, the scroll wheel to zoom. A mouse or trackpad is required on a computer.

Controller

The left stick pushes a cursor about the screen and the right stick, the shoulders and the triggers drive the camera. All sixteen buttons can be moved in Settings → Controls, and a rebind swaps two buttons rather than doubling one up.

Nothing about the controller runs until a real one is used, so a park played with nothing plugged in behaves exactly as it did before. If a pad is connected and the game ignores it, press a button on it once - that is what wakes it up - and tell us which pad it is if that does not do it.

5. What you need to run it

The park is one flat map with a crowd in the low hundreds and no streaming, so it asks less of a machine than its screenshots suggest. The minimum below is honest rather than cautious - integrated graphics really are enough.

PlatformMinimumComfortable
Windows Windows 10 64-bit (21H1), Core i3-8100 or Ryzen 3 1200, 4 GB RAM, Intel UHD 630 / GT 1030 / RX 550 with 2 GB, DirectX 11, 2 GB free Windows 11, Core i5-10400 or Ryzen 5 3600, 8 GB RAM, GTX 1650 or RX 6400 with 4 GB - 1080p at 60 fps with a full park
macOS macOS 12 Monterey, Apple M1 or a 2017-or-newer Intel Core i5, 8 GB RAM, any Metal-capable GPU, 2 GB free macOS 14 or newer on Apple M2, 16 GB RAM - Retina at 60 fps
iPad An iPad with an Apple silicon chip Any of them. The game is built for this device first and everything else is the port.

A mouse or trackpad is needed on Windows and macOS, and the minimum screen is 1280x720. There is no Linux or Steam Deck build yet - it is a natural fit and it is on the list, but we would rather not tick a box we cannot stand behind.

6. Buying, refunds and updates

The game is sold through stores we do not run, and purchases, receipts and refunds are theirs rather than ours - we never see your payment details and we cannot refund an order on your behalf. If the game is not what you hoped, ask the store you bought it from:

Updates arrive through the same store, at no extra cost. There is no subscription, no season pass, no advertising and nothing to buy inside the game - you buy it once and that is the whole transaction.

We do still want to hear it if a purchase went wrong, even though we cannot fix the billing ourselves. Sometimes the underlying problem is ours.

7. Your data

The game collects nothing, sends nothing and needs no account, and your parks never leave your device. That is worth a page of its own rather than a paragraph here - see the privacy policy, which also covers what this website measures.

8. Following along

New rides, shops and systems land all the time. The clearest place to see them is the YouTube channel, and the rides, shops, arcade and staff pages on this site are kept in step with the real game.

9. Still stuck?

Then this page did not cover it, which is useful to know on its own. Tell us what you were trying to do - there is no wrong way to ask.

info@corbata.games

Corbata Games, the Netherlands · www.corbata.games