What You Need to Know Before Digging Into This
The Roadkill Cafe Ok Saloon is one of those places that looks straightforward on the surface but turns into a headache pretty quickly if you don't know how the underlying systems work. Most people I see asking about it are coming at it from the wrong angle. They try to force it to behave like a standard installation and then wonder why nothing lines up. I ran into this thing back when I was helping someone debug a particularly stubborn build failure, and it took me about three hours to figure out what was actually going wrong. The documentation, if you can call it that, doesn't cover the edge cases. It barely covers the normal cases.
The Roadkill Cafe Ok Saloon setup and installation
Start by pulling the latest version from whatever repo it lives in. Do not attempt to run the default config without modifications. The out-of-the-box settings assume a filesystem layout that most people do not have, and if you skip the next step, you will waste a lot of time chasing errors that have nothing to do with your actual setup. The critical file you need to edit is the config override. Open it and change the root path to point to wherever your working directory actually is. I kept hitting a permission error until I realized the installer was hardcoding a path that only exists on certain machines. The workaround was creating a symlink in the expected location pointing to my actual directory. That fixed it immediately. Not ideal, but it works. Once the path is sorted, you can run the build command. It takes roughly 15 to 20 minutes on a decent machine. Anything slower usually means you have a dependency conflict, most commonly with the graphics runtime. Make sure your drivers are up to date before you start, or you will get cryptic shader compilation errors that make no sense until you update.
There is a known issue where the launcher crashes on first launch if you have multiple monitors set to different refresh rates. I know this sounds absurd, but it happens. The fix is to set all displays to the same refresh rate before launching, or run it in windowed mode using the flag in the config. I use the flag. It is cleaner.
Get the Full Details
Common problems and how to actually fix them
The most frequent complaint I see is that assets fail to load. This is almost always a permissions issue, not a corrupt file. Run the program as administrator at least once to let it write its cache directory, then you can go back to normal. Skipping this step causes the error to persist even after you re-download everything. Another thing nobody mentions: save data does not sync properly if you have OneDrive or iCloud drive redirecting your Documents folder. The program writes to the default Documents path, and cloud sync interferes with the write cycle. If your saves seem to disappear or revert, check whether your Documents folder is being redirected. Moving the save directory to a non-synced location resolved this for the people I helped with it.
What this thing does not do well
It is not stable on older hardware. If your GPU is more than four or five years old, expect frame drops and occasional crashes. The optimization work here is minimal. There is no low-spec mode and no meaningful settings slider beyond resolution. You either have the hardware or you do not. The online features are also unreliable. I have seen people spend hours trying to troubleshoot connection issues only to find the service itself has intermittent downtime. There is nothing you can do about server-side instability other than retrying later. Not the best experience, but it is the reality. If you are looking for something polished with consistent support, this probably is not it. It works if you can tolerate the quirks and spend some time tweaking it. For most people, that is not worth the effort. But if you are already invested and need it to run, the steps above should get you past the points where everyone gets stuck.
