Fate/Grand Automata (FGA): an Android auto-battle app for FGO farming

What FGA automates, and who it is built for

FGA exists for one repetitive task: running the same FGO node over and over to collect drops. The README is explicit that it is "not made to do the story for you, but to automate the mundane farming." That sentence is the whole scope. If you want a bot that clears Singularities unattended, this is not it.

The audience is Android players who farm a lot and do not want to root their phone. The README states Android 7 or later and says root is not needed on phones. The project is a Kotlin port of FGO-Lua, rewritten as a native Android app with a configuration UI and, per the README, without a time limit on use. That last point matters: the original Lua script had a usage cap, and removing it is one of the stated reasons the port exists. FGA does not modify the game itself. It looks at the screen and taps, the same input path a human uses.

OpenCV, MediaProjection and the Accessibility Service

Three Android platform pieces do the work, and the README names all three. MediaProjection captures screenshots. OpenCV performs image recognition on those frames. An Accessibility Service performs the clicks and swipes. Nothing is injected into FGO, and no game memory is read.

That architecture explains both the app's strengths and its fragility. Because recognition is pixel-based, FGA needs reference images of Servants, Craft Essences and friend supports to make decisions about the support screen. The project ships a Support Image Maker, documented on its wiki, for producing those images. Because input goes through the Accessibility Service, the app needs that permission granted, and the floating play button only appears once the service is running.

The script selection is automatic. According to the README, when you press the play button the app detects which script can run on the current screen and offers it. So the same button covers farming, the Lottery, and Friend Gacha, rather than making you pick a mode from a menu first.

Installing FGA and running your first farm

FGA is not distributed through Google Play. The README points to the project website at https://fate-grand-automata.github.io, and that is the only download location it gives. Sideloading means allowing installation from the browser or file manager you use to fetch the APK.

After installing, launch the app and start the capture service. The README's steps are short: click Start Service and grant every permission it requests.

# No install command exists. Download the APK from the project website:
# https://fate-grand-automata.github.io
# Then install it on the device (Android 7 or later).

With the service running, open FGO. A floating button with a play icon should appear over the game. Navigate to the node you want to farm, then press that button to start. The README notes the same button pauses or stops the run later.

# In-app sequence, from the README:
# 1. Start Service, grant permissions
# 2. Open FGO
# 3. Go to the node you want to farm
# 4. Press the floating Play button to start
# 5. Press it again to pause/stop

If you need support images before farming, the wiki page for Support Image Maker describes how to create and use them. The README directs troubleshooting questions to the wiki's Troubleshooting page before anything else, which is a reasonable signal that first-run permission problems are common.

Where FGA breaks, and when it is the wrong choice

The failure modes follow from the design. Screen recognition depends on the game's UI looking the way the reference images expect. An FGO client update that moves a button, changes a font, or restyles the support list can break recognition until the project updates its assets. That is a maintenance dependency you inherit as a user, not something you can patch locally without rebuilding the app.

Permissions are the second wall. MediaProjection and the Accessibility Service both require explicit grants, and the README tells you to give all permissions the app asks for. On a device where those grants are restricted, or where the user is unwilling to hand an Accessibility Service that level of control, FGA simply will not run.

Platform is the third limit. FGA is an Android app. The related searches include "Fate Grand Automata iOS" and "Fate Grand Automata pc", but nothing in the README describes an iOS or desktop build. Anyone searching for those should treat the absence as the answer.

Finally, scope. The README's own framing rules out story progression. If your goal is to clear content rather than repeat a farmable node, FGA is the wrong tool and no configuration will change that.

FGA compared with the FGO-Lua script it came from

The direct alternative is FGO-Lua, the project FGA credits in its acknowledgements and describes as the origin of this app. FGA is a Kotlin port of it, packaged as a native Android application with a UI for configuration.

The practical difference is the runtime and the interface. FGO-Lua is a Lua script; FGA is an APK you install and configure through an on-device UI. The README states the port has no time limit on use, which implies the Lua original carried one. FGA also adds the Support Image Maker and automatic script detection on the play button, neither of which the README attributes to the original.

What does not change between them is the fundamental method. Both look at the screen and tap. Neither reads game memory or modifies the client. If you are choosing between them, the decision is about packaging and permissions, not about a different automation strategy.

Licence, releases and what upgrades cost you

FGA is MIT licensed, and the LICENSE file sits at the repository root. MIT is permissive: you can read the source, fork it, and ship modified builds, provided you keep the copyright notice and licence text. That matters if you want to patch recognition assets yourself rather than wait for an upstream release. It says nothing about whether automating FGO is permitted under the game's own terms, which is a separate question the repository does not address.

Release cadence is visible in the tags. v3053 was pushed on 2026-09-27, v3050 on 2026-09-14, and v3049 earlier the same day. That is a fast, version-numbered release stream, and the last push to the repository was on 2026-09-27. Frequent releases are a double-edged thing for a screen-scraping tool: they suggest recognition fixes land quickly after game updates, and they also mean you should expect to reinstall periodically.

The upgrade cost for a user is low in mechanics and non-trivial in attention. There is no store-based auto-update path described in the README, so you fetch a new APK from the website when something breaks. If you forked the app to fix an image asset, you now own a merge every time upstream changes the same area.

Editorial conclusion

FGA suits Android players who farm the same node repeatedly and accept a sideloaded APK plus screen-capture and accessibility permissions. It is the wrong tool if you play on iOS, want the story played for you, or will not grant those permissions. Before adopting it, confirm your device runs Android 7 or later, download only from fate-grand-automata.github.io, and read the Troubleshooting wiki page for the failure you hit.

Frequently asked questions

Official sources

1. Fate-Grand-Automata/FGA on GitHub
2. License: MIT
3. Project website
4. README
5. Releases