Hi ToolDevs,
before submitting Flight Commander for review, I'd like to check four design points so I don't build anything that can't be tolerated. I've read Forbidden features, the submission template, the AI-use post and AGENTS.md. Your AGENTS.md is in the repository, and its §7 self-audit will be part of the submission. No other developers' code was used, not even as AI input, and reviewers will get the full source. Until the review, the in-game part only runs on Singularity (en_808).
What it is: a free OGame companion with no paid tiers. Funding comes from donations, a hero.li partner link, and ads on the public website (never in the app or the game). Features: economy/ROI planning, fleet and combat calculators, spy report sorting, expedition statistics and an overview of all official universes. Public API files (serverData, lobby server list) are fetched server-side and cached according to their update intervals. Report and statistics lookups will go through the community proxy.
1) Desktop app with the game inside
A Windows app (Electron/Chromium) shows the official game in a normal browser window. It makes no changes to the game UI. Login goes through the normal Gameforge lobby, and I never see or store credentials. A read-only script parses only the page the player currently has open, and only while that window is visible. The app sends no requests of its own to the game: no fetches, no cp, no accountInfo, no auto-refresh, no timers, no alarms. Currently the Electron marker is removed from the user agent.
Is a client like this tolerable in principle? Should it keep that stock Chromium user agent or identify itself?
2) Upload and AI, only with opt-in
Parsed data leaves the device only after an explicit opt-in. The opt-in can be revoked, and players can export or delete their data at any time. The data feeds a web dashboard. For recommendations (build focus, raid safety, expedition advice), a summarized state without player names or coordinates is sent to an AI provider. The AI only advises. Every game action remains a manual click by the player.
Is this acceptable, and do you expect any disclosure beyond this?
3) Origin Exporter import
On live universes, players could paste their Origin Exporter JSON into the web dashboard instead of using my reader. The dashboard never runs on the game page, but it stores the pasted export in the player's account.
Does that count as manually entered data (AGENTS.md §5), or does storing it server-side already need the review?
4) Partner link
AGENTS.md §1.8 allows a hero.li link. Mine is clearly labelled ("Start a new universe") and appears on the website and in the app's universe overview, outside the game window. In the desktop app, clicking it opens the link in the game window, so the lobby registration happens there.
Is that OK?
If anything here is a no-go, I'll drop or change it before submitting.
Thanks!
