A companion app that mostly automates the game 'Iron Nest' for you.

Go to file

Dominik Roth 7ecda4ea3b Rename package/app to FeNigma consistently - src/ironnest_assist/ -> src/fenigma/ - run.sh invokes -m fenigma.app - APP_ID: eu.dominik-roth.IronNestAssist -> eu.dominik-roth.FeNigma - window title, IronNestApp class -> FeNigmaApp - __init__.py docstring, README pgrep hint updated IRON NEST (the game's own name, e.g. NEST_KEYWORD in ocr.py) is left untouched, only our own project/app naming changed. Verified: clean import under the new module path, install.sh still builds the venv correctly, and the OCR regression sweep (9 known screenshots) still passes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>		2026-08-08 20:20:43 +02:00
src/fenigma	Rename package/app to FeNigma consistently	2026-08-08 20:20:43 +02:00
.gitignore	Initial commit: IRON NEST Assist	2026-08-08 20:01:50 +02:00
icon_alt.png	Rewrite README short, rename project to FeNigma, add icon/showcase	2026-08-08 20:15:14 +02:00
icon.png	Rewrite README short, rename project to FeNigma, add icon/showcase	2026-08-08 20:15:14 +02:00
install.sh	Add install.sh, run.sh uses the venv when present	2026-08-08 20:18:15 +02:00
README.md	Rename package/app to FeNigma consistently	2026-08-08 20:20:43 +02:00
requirements.txt	Initial commit: IRON NEST Assist	2026-08-08 20:01:50 +02:00
run.sh	Rename package/app to FeNigma consistently	2026-08-08 20:20:43 +02:00
showcase.png	Rewrite README short, rename project to FeNigma, add icon/showcase	2026-08-08 20:15:14 +02:00

README.md

FeNigma

Fe (iron) + enigma, we solve the geo puzzles.

A companion app that mostly automates IRON NEST: Heavy Turret Simulator for you. Screenshot the game's typewriter orders and it solves the geo puzzle and the trajectory math, handing you ready-to-fire commands: elevation, azimuth, number of powder charges. Screenshot the field log and it picks up kills and newly-spotted units automatically. You can also plan strikes of your own, picking a shell for the blast radius you need. Pure screen-reading, no game files touched, no input injected.

What it does

Reads orders, solves the geometry. Paste/screenshot the in-game typewriter text and it parses absolute grid refs and relative bearing/distance descriptions, then resolves everything into map coordinates, chained clues ("Bearing 293 from Alpha") included. The map shows its work: the actual bearing lines/circles behind each resolved position. When a description is genuinely ambiguous (two intersections), both candidates are shown instead of guessing.
Calculates the shot. Every resolved target gets a live firing card: elevation, azimuth, and minimum powder charge, computed from the Nest.
Tracks the battle. A second screenshot of the field log marks units destroyed and folds in newly-spotted contacts, merging with what's already known instead of duplicating it.
Plans strikes. Drop a strike anywhere on the map and pick a shell to preview its blast radius before committing.

Install

./install.sh

Sets up a venv for the Python deps (Pillow, numpy, pytesseract) and checks for the system packages that pip can't install: GTK4/libadwaita bindings and tesseract. If either is missing it prints the package names for your distro and stops, install those and re-run.

Run

./run.sh

Uses the venv from install.sh if one exists, otherwise falls back to system python3. GTK apps with this app ID are single-instance, if a run gets killed uncleanly it can leave a zombie registered on D-Bus and silently no-op the next launch. If ./run.sh seems to do nothing, pgrep -af fenigma and kill any stragglers first.

Stack

GTK4 + libadwaita (PyGObject) for the UI, Tesseract (via pytesseract) for OCR, Pillow/numpy for preprocessing. Details on the coordinate system, OCR formats, and solver internals live in code comments (solver.py, ocr.py, models.py) rather than here.