Skip to content

Ion Fury - RetroBIOS

Type standalone
Classification Game engines
Source https://voidpoint.io/terminx/eduke32
Version r11007
Profiled 2026-10-04
Cores fury
Systems fury
Technical notes

Ion Fury runs on EDuke32 built with FURY=1 (GNUmakefile:6-15), which defines EDUKE32_STANDALONE and sets APPBASENAME=fury, APPNAME="Ion Fury". In standalone mode the GRP-detection table of EDuke32 (source/duke3d/src/grpscan.cpp:38-77) is compiled out by #ifndef EDUKE32_STANDALONE, G_DefaultGrpFile returns "(none)" (source/duke3d/src/common.cpp:60-77), and the loader autoscans the search paths for .grp / .zip / .ssi / .pk3 / *.pk4 (source/duke3d/src/common.cpp:913).

Search paths added for the Fury binary include the Steam install (Ion Fury) and the GOG install (ION Fury), marked with SEARCHPATH_FURY (source/duke3d/src/common.cpp:585-587, 622-625, 822-833). After scanning, G_CleanupSearchPaths removes all non-FURY entries when the FURY game flag is active (source/duke3d/src/common.cpp:850-851), so Fury only reads from its own install directory.

No hash or filename is validated by the engine: Ion Fury ships one GRP (fury.grp) that holds every map, art bank, sound and DEF the game needs, plus a small number of top-level files the retail installers lay down alongside it. Only the GRP is listed below; the other files (fury.cfg, settings.cfg, saves, screenshots) are user state.

1 files | 1 required, 0 optional | 0 in repo, 1 missing Categories: 1 game data

fury.grp required missing game_data

  • System: fury
  • Source: source/duke3d/src/common.cpp:913, source/duke3d/src/common.cpp:585-587, source/duke3d/src/common.cpp:822-833
  • Main data archive bundled with the retail Ion Fury release. Autoscan picks it up as the only GRP under the Fury search paths.

Generated on 2026-10-10T11:26:01Z