improve rogomatic so that is works well with rogue 5.4.5

[lcn2]

The goal is to have rogomatic use rogue 5.4.5 well enough that in time, rogomatic can "win" the game (i.e., find the Amulet of Yendor on level 26 and safely exit out of level 1).

Such a "winning" game wil take a while to play for start to finish. To "train" rogomatic to obtain the skill to eventually play a "winning" game will tale much longer: perhaps a much as a few days from start to finish?

As of 2026 February 22, rogomatic cannot be start as it crashes:

./rogomatic
Error opening terminal: rg.
                           zsh: bus error  ./rogomatic

But at east it compiles. 😉

[lcn2]

Issue #3 created as per the "crash on launch" problem.

UPDATE 0

Issue #4 crated as per the automated code scan.

Issue #5 created to deal with the current README.md stub file.

Issue #6 created to address the out of date rogomatic(6) man page.

[jenoola]

visibility ping :)

[lcn2]

visibility ping :)

Welcome @jenoola .. you have been invited to be a collaborator on this repo.

In the mean time see the open issues.

Thank you 🙏 for your help.

[lcn2]

Hello @jenoola ,

Let's discuss what needs to be done to fix rogomatic in this Discord discussion thread.

Also I sent an invite to become a calibrator for this repo.

I do recommend that you also GitHub fork this repo, and star it so you have a GitHub base under which you can work.

[lcn2]

The "rogue version 5.4.5 release 2026-02-27 (chongo was here)" release contains a feature that will probably be useful to rogomatic, where the $ROGUEOPS environment variable will allow rogomatic to specify the:

• rogue player name
• rogue lock file path
• rogue score file path
• rogue save file path

See commit 1c05a87f73c4cfdeb98be86257bdb1d2702ae824 in "the other repo". :-)

[lcn2]

BTW, @jenoola : The authors of the rogue game has fun making tweaks to rogue to challenge the authors of rogomatic to up their game. They had a friendly competition of "add new features" / "code the expert to deal with the new features".

There is likely to be a bit of mismatch between what rogue 5.4.5 presents, and what rogomatic can drive.

Moreover, the rogomatic authors were more on the "academic" side, and less on the "robust coding" side.

So part of the "make rogomatic drive rogue" will involve bug fixing stuff like the current startup crash.