The patch supplies English and control, not the arcade game
FGOAC scooby sits on top of Cloud23333's FGO Arcade local platform V1.01 or V1.02. It does not ship Sega or TYPE-MOON game data. The release replaces the Chinese launcher, applies translated files, and starts the existing local server and game. A player who has only this repository has a patch, not a playable installation.
The translation is large enough to change the experience: the README counts 65,266 translated text rows and 240 rebuilt sprite archives. Menus, tutorial, story, battle screens, shops, help, Servant profiles, and Craft Essence information are covered. A few event banners and later event-shop images remain Japanese because their text is baked into artwork.
The launcher also solves practical offline-platform jobs. Its five pages manage Master accounts, a 30-card deck, draw-rate presets, display and controller settings, the local server, diagnostics, and event banners. It can grant a full roster, and its card library holds 1,384 cards. None of that restores online play; every sortie uses the local server.
What happened when we ran it
The lab record contains no execution result for commit 15146e7. C# was outside the supported ecosystems, and the repository provided no Dockerfile as an alternative route. There is therefore no honest install duration, dependency total, disk footprint, compiler result, test count, or dependency-audit result to publish for this project.
Repository and release evidence can describe requirements, but it cannot substitute for that missing run. The source targets Windows through C# and WPF, while the player release bundles its own .NET runtime. A source build needs the .NET 10 SDK on Windows 10 or 11 x64, restores the .NET 6 reference and runtime packs, and publishes a self-contained executable. Those are author instructions, not lab-confirmed behavior.
This distinction matters because success depends on more than the launcher compiling. The patch must find the right game tree, modify it safely, start the bundled server, pass Windows security controls, and reach working graphics hardware. Our evidence does not prove any of those steps on a real PC.
V1.02 and a supported GPU narrow the workable setup
The supported base is the Cloud23333 local platform, with V1.02 preferred because it fixes ERROR 4102, blank Servant records, and an enhancement sync problem. The launcher must sit beside the install's App and Server folders. On first start it requests administrator approval, applies English files, checks write access, creates Windows Firewall rules, makes a Master account, and selects windowed 1280 by 720.
NVIDIA on a current driver is the documented safe graphics path. An older AMD layer covers several RX 500 and RX 6000 cards, the RX 7600, and desktop Ryzen graphics. A newer shim runs on the RX 7900 XTX but is documented as crashing at the first battle on other cards. Intel integrated graphics, Intel Arc, and Ryzen laptop graphics are not covered.
The issue tracker matches those warnings. Issue 41 reports a Vega laptop crash in the AMD OpenGL path, while issue 11 covers Intel Arc B580. Several earlier reports describe exit code 22 or access violations around the tutorial. These are user reports on particular systems, but they give competent buyers a reason to check the exact GPU before assembling the rest of the platform.
The patcher backs up files and protects account data
The English payload overlays an existing install, so recovery behavior matters. The development guide says the patch manifest stores a SHA-256 for each shipped file plus a hash over the list. Before replacement, files go under a timestamped backup directory. The patch checks copied files and records the installed version and manifest hash. Running the same manifest again does nothing.
Rollback restores the newest backup and removes files that release added. The manifest is forbidden from listing accounts, decks, server state, the database, or unrelated launcher settings. Version 1.2.0 fixed a rollback case where an update with no changed game files could restore the prior release's backup. That fix is specific enough to justify updating rather than assuming rollback was already harmless.
Drive restrictions remain unusual. E: and Y: are rejected because the game's hook redirects paths on those letters to a cabinet data mount. The troubleshooting table also warns about Storage Spaces and ReFS save failures, while recommending a plain NTFS drive. Install location is part of compatibility here, not housekeeping.
Diagnostics are unusually useful for a fan launcher
The Advanced page maps error codes to actions and gathers logs for the launcher, translation hook, server control, game server, MariaDB, and environment check. ERROR 4102 points to local-server communication. ERROR 8404 means the cabinet startup mode is waiting for a main unit. ERROR 4105 means the game was not elevated. A 0xC000001D exit points to a CPU without F16C.
Some entries remain unresolved. Exit code 22 can mean the window opens and closes even after environment checks pass. ERROR 6401 with a controller or USB device has a reported power-setting workaround, not a pinned cause. The docs ask users to attach crash dumps and named logs rather than posting a screenshot alone, which gives maintainers a better chance of separating patch failures from the underlying game.
Version 1.2.0 is active, but the audience stays narrow
GitHub showed 176 stars, 25 combined issues and pull requests, an MIT license, and a September 21, 2026 push. Release 1.2.0 shipped the same day with the rollback fix and event-banner controls. The repository's English documentation is detailed and direct about unsupported graphics, missing online play, administrator access, and ownership of the original game.
FGOAC scooby is useful because it accepts the strange shape of its dependency instead of hiding it. For the right fan, 65,266 translated rows and a capable account launcher turn an inaccessible local platform into a workable offline game. For everyone else, the missing base package, Windows-only stack, hardware gaps, and absent lab run are enough reason to walk away.