nx_game_engine_lib.nx

nx_game_engine_lib.nx -- the GENERIC Nishi dungeon-crawler ENGINE (reusable library). This is the "engine" half of autonomous game-gen: it is written ONCE and reused by every generated game. All per-game variation (title, difficulty, enemy/loot counts, damage model, and the COMBAT FSM transition table) arrives at runtime in a config array -- nothing is hardcoded. A generated per-game module just fills the config + FSM table and calls eng_run(cfg); the emitter (nx_game_emit) writes that tiny module from a data game-spec. Built native by Nishi's own toolchain (nx_cc->nxasm_x86). Combat is fully DATA-DRIVEN: g_fsm_step reads the supplied transition table (the STATE_MACHINE shape generalized to runtime data). The combat EVENT CONVENTION the spec's table must follow (same as the emitter-authored _pe_dungenc): states 0=START 1=PLAYER_TURN 2=ENEMY_TURN 3=WIN 4=FLEE 5=END events 0=enter 1=attack 2=enemy_act 3=defeat 4=flee 5=resolve HONEST AUTHORSHIP: this engine library + the emitter are TUTOR-authored tooling (Claude). The GAMES the emitter produces from specs are emitter-authored output = the autonomy lever (feed specs -> games hands-off). The combat FSM tables come from the team's STATE_MACHINE specs. license_tier: ORIGINAL state st[]: 0=px 1=py 2=hp 3=score 4=level 5=mode 6=fsm 7=enemy_hp 8=rng 9=foes 10=msg 11=enemy_x 12=enemy_y | config: 13=walls 14=enemy_base 15=enemy_per_lvl 16=ehp_base 17=ehp_per_lvl 18=loot 19=dmg_base 20=dmg_rand 21=title_ptr 22=fsm_table_ptr 23=fsm_nstates 24=fsm_nevents | world grid 16x12 bytes at st+256