Every few months the same argument goes around: expeditions got nerfed, DM finds dried up, the big resource hauls stopped showing up. And every time it's the same evidence — "feels like it", "I used to get more", someone's daily 200 expeditions collected across months with no record of which days had which boosters, which lifeform bonuses, or which game version was live.
That's the actual problem. It isn't only sample size — it's that nobody writes down the conditions. A 200-expo sample where the context is unknown can't tell you whether your results shifted because the game changed or because your ExpoComputer expired. You can't separate the two after the fact.
So: a userscript that records expedition results together with the conditions they happened under. Every result is stored alongside the buffs active at the time, your lifeform bonuses, class, universe speed, and game version. That's what makes comparison possible.
What it collects
Runs on the overview and messages pages:
- Expedition results — every type (resources, DM, items, shipwrecks, trader, alien/pirate combat, fleet loss, early/delayed return, nothing) with depletion level, size, timestamp, and amounts gained or lost, read from the game's own message data. Follows pagination and picks up new messages as they appear. Only messages newer than the script's first run — nothing historical gets uploaded.
- Active expedition buffs — resource booster %, turbo %, extra slots, expedition computer, and when they expire.
- Lifeform bonuses — class bonus and the expedition techs (ResultBooster, DMBooster, ShipResultBooster, SpeedBooster, FleetLostReducer).
- Context — server, game version, universe speed, character class.
A small status indicator in the messages tab bar shows what it's doing.
What happens with the data
To be clear about what this is right now: a backend that collects and aggregates. There's no dashboard, no login, nothing to look at yet. I run the analyses and post results.
What I'm building toward is tooling where analyses run automatically rather than me writing queries by hand. Once that exists, per-player analysis becomes cheap — which is the interesting part, because the most common version of this complaint isn't "expeditions are nerfed", it's "my expeditions are nerfed". With enough of your own trips recorded against known conditions, that becomes checkable: either your distribution really does sit off from comparable players on the same universe and class, or it doesn't and you've had a rough stretch.
A frontend might happen eventually. No promises. If you want that now, this isn't it.
What gets sent, and where
Data goes to api.antiga.me, run by me.
The script sends:
- Server ID and player ID
- Character class, game version, universe speed
- The expedition results described above
- Currently active expedition buffs and lifeform bonuses
The server additionally records a hashed form of the IP address the request came from. That's not something the script reads or transmits — every HTTPS request carries the sender's address by necessity, the same as any website you visit. It's hashed with a key that rotates and is then discarded, so past hashes stop being linkable to anything. Basic abuse measure, nothing more.
On the player ID: this is the one that looks intrusive, so — it does two jobs. It's what makes per-player analysis possible at all, and it's how I can delete your data if you ask. Without an identifier there's no way to locate your rows, and "sorry, can't find your data" is a bad answer to a deletion request. No player name, no email, no credentials. Anything I post publicly will be aggregate; I'm not putting up a leaderboard of who loses the most fleets.
Your data, your call
Legal basis is legitimate interest (Art. 6(1)(f) GDPR). Participation is voluntary in the plainest sense — don't install it and nothing happens, uninstall it and collection stops immediately.
Want a copy of everything stored under your player ID, or want it deleted? DM me on the Origin board, or on Discord (Discord handle: _rivenscryr).
Expedition results are kept for as long as the project runs, since long-term comparison across patches is the entire point.
Honest caveats
- Data is self-reported and I can't verify it. Treat conclusions with the skepticism that deserves.
- Early on the dataset will be too small to conclude anything. Expedition variance is brutal — this needs volume and time before it says anything trustworthy.
- It only sees what your messages tab still shows. Expeditions whose messages have already rotated out are gone.
Install
- A userscript manager (Tampermonkey, Violentmonkey, whatever you use)
- The script: https://greasyfork.org/en/scri…-ogame-expedition-tracker
- Open your expedition messages — it handles the rest
This tool is tolerated. 16.09.2026
