dodox/FeNigma
dodox/FeNigma
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

README: drop em-dashes, unwrap paragraphs to single lines

Browse Source 
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Dominik Moritz Roth 2026-08-08 20:16:40 +02:00
parent 07c89c5be4
commit 0f29915c45
1 changed files with 8 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
README.md
View File

@ -5,34 +5,18 @@
<br>
</h1>
<p align="center"><b>Fe</b> (iron) + enigma — we solve the geo puzzles.</p>
<p align="center"><b>Fe</b> (iron) + enigma, we solve the geo puzzles.</p>
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.
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.
![Showcase](showcase.png)
## 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.
- **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.
## Run
@ -40,14 +24,8 @@ screen-reading — no game files touched, no input injected.
./run.sh
```
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 ironnest_assist`
and kill any stragglers first.
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 ironnest_assist` 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.
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.