Game seems to play itself and triggers GNOME Shell's "is not responding" dialog

[HebaruSan]

Problem

I just stumbled on this game while browsing apps randomly in my Ubuntu system menus. I'm quite interested in Haskell and Roguelikes, so this seems like a really neat project. But so far this is what I get:

It looks like the numerals are the player's squad members (I browsed the documentation a bit but not a lot), based on the cursor movements hovering on them, but they're moving around by themselves rather than waiting for player input. It looks like an AI autoplay mode has been triggered automatically.

I eventually noticed the prompt at the top and tried pressing a key, but nothing happened. All I can seem to do is Force Quit.

Suggestions

• I'd find this a lot more approachable if the default view was of the game paused waiting for player input rather than an AI autoplay, as in other Roguelikes.
• It would help tremendously if the "not responding" popup did not appear. I tried running it in a terminal to bypass whatever problems the custom window has, but it still opened the custom window, so that would be another nice solution.

[Mikolaj]

Hi! Thank you for the report. That's most likely a bug, probably of the SDL graphics library, that blocks any key and mouse input. Which Ubuntu version is this?

Could you experiment a bit with commandline options? Run Allure --help in the terminal and try a few combination. E.g., --frontendANSI would run entirely in the terminal and so rule out the problem with SDL. Or --gameMode crawl would not start one of the AIvsAI modes but the crawl mode, so the player should be in control from the start. Once you start in such a mode once, you should be in control until you cede it intentionally or until the game ends.

[HebaruSan]

Sorry, I realized belatedly that you'd want system info and was in the process of grabbing it:

I'll experiment with those options and report back...

[HebaruSan]

--frontendANSI doesn't exist, so I might have an older version than expected.

$ Allure --frontendANSI
Invalid option `--frontendANSI'

Usage: Allure [--newGame N] [--knowMap] [--knowEvents] [--knowItems] 
              [--showItemSamples] [--exposePlaces] [--exposeItems] 
              [--exposeActors] [--sniff] [--allClear] [--boostRandomItem] 
              [--gameMode MODE] [--automateAll] [--keepAutomated] 
              [--stopAfterSeconds N] [--stopAfterFrames N] [--printEachScreen] 
              [--benchmark] [--setDungeonRng RNG_SEED] [--setMainRng RNG_SEED] 
              [--dumpInitRngs] [--dbgMsgSer] [--gtkFontFamily FONT_FAMILY] 
              [--sdlFontFile FONT_FILE] [--sdlScalableSizeAdd N] 
              [--sdlBitmapSizeAdd N] [--scalableFontSize N] [--fontDir FILEPATH]
              [--logPriority N] [--maxFps N] [--disableAutoYes] [--noAnim] 
              [--savePrefix PREFIX] [--frontendTeletype] [--frontendNull] 
              [--frontendLazy] [--dbgMsgCli] [--version]
  Configure debug options here, gameplay options in configuration file.

$ Allure --version
0.9.5.0

I see the repo is up to v0.11.0.0, so my apologies if this was already fixed. I'll try compiling the repo next...

--gameMode crawl seems to wait for user input but still triggers "is not responding":

[Mikolaj]

Oh, right, I forgot how ancient the version in Ubuntu is. It even has a known error for which the fix is still not applied in Ubuntu (but it's not the one).

It would be great if you tried compiling, feel free to ask questions here if there are any snags.

Another option is to download a linux binary, which may or may not work on your new Ubuntu. See the Releases github subsection.

In this Allure version --frontendTeletype is the (very ugly) terminal-only option. You may require Enter after each keystroke. Please let me know if this one accepts input.

I'd love to work around the SDL bug (it's not present in my old Ubuntu, but I've had reports about it), so any experiments would be very useful. E.g., perhaps newer Haskell SDL bindings (the ones you'd use when compiling yourself) eliminate the problem. Or perhaps upgrading SDL fixes it (downgrading certainly does, but that's hard to do). Or perhaps I can tweak something.

[HebaruSan]

The github build instructions from the README didn't work for me:

$ cabal run --project-file=cabal.project.LH.dir 
Resolving dependencies...
cabal: The run command is for running a single executable at once. The target
'' refers to the package Allure-0.11.0.0 which includes the executable
'Allure' and the test suite 'test'.

Adding Allure to the end seemed to get past that.

In a separate terminal I started the cabal install instructions, and that has been stuck on Building LambdaHack-0.11.0.0 (lib) for several minutes now. How long does it usually take? Never mind, that finished without problems. I guess the answer is "several minutes plus a bit more" 😉 .

[HebaruSan]

(Deleted the previous comment about running the custom compile. It hadn't actually finished, and I was running make play from the other terminal where I ran cabal install. It was in the Allure project folder, though.)

[Mikolaj]

Yes, cabal 3.0 is ancient. I could fix instructions for cabal run to be more portable, as you suggested, but I can't replace list-bin. Oh, I even say "version 3.4 or later is required" in the README.

[HebaruSan]

My custom compile of the code from GitHub is worse; it still says "not responding", but now I can't even move the window.

[HebaruSan]

How do I pass --frontendANSI through the cabal run command? Without quotes it thinks it's a flag for cabal, and with quotes it doesn't recognize the command as valid:

$ cabal run --project-file=cabal.project.LH.dir Allure --frontendANSI
cabal: unrecognized 'run' option `--frontendANSI'

$ cabal run --project-file=cabal.project.LH.dir 'Allure --frontendANSI'
cabal: Unrecognised target syntax for 'Allure --frontendANSI'.

[Mikolaj]

Thank you for the experiment. I guess I mixed up too different methods in the README. One for official version from Hackage, using cabal install and the other, for unofficial version straight from the repo using cabal run. Which you did you end up experimenting with?

[HebaruSan]

I'm trying both in parallel, which admittedly is causing some confusion, but primarily focusing on the unofficial version from the repo right now.

[HebaruSan]

The final output from the cabal install command was:

Starting     Allure-0.11.0.0 (exe:Allure)
Building     Allure-0.11.0.0 (exe:Allure)
Installing   Allure-0.11.0.0 (exe:Allure)
Completed    Allure-0.11.0.0 (exe:Allure)
cabal: installdir is not defined. Set it in your cabal config file or use
--installdir=<path>

I wasn't sure whether that was a warning or an error, but trying the next step suggests error:

$ ~/.cabal/bin/Allure
-bash: /home/user/.cabal/bin/Allure: No such file or directory

~/.cabal/bin exists but only contains my xmonad.

[Mikolaj]

I just tried and this works cabal run --project-file=cabal.project.LH.dir Allure -- --frontendANSI. However, make play would find the binary for you and so you wouldn't need cabal run, which tries to compile again. If cabal is too old, you can find the binary manually inside the repo. It's called Allure and has executable bit set. You can run it directly.

[Mikolaj]

cabal: installdir is not defined probably comes from your ~/.cabal/config being even older than your cabal. Perhaps remove ~/.cabal/config so that it gets regenerated?

[HebaruSan]

I just tried and this works cabal run --project-file=cabal.project.LH.dir Allure -- --frontendANSI

Thanks! That worked for me as well, and spacebar took me to the menu where I could turn off autoplay. My replies may slow down now that I'm trying out the gameplay...