Demo doesn't work:
$ ./Downloads/SternlyWordedAdventuresV47Demo.AppImage
Error: [love "boot.lua"]:251: loop or previous error loading module 'love.window'
stack traceback:
[love "boot.lua"]:352: in function <[love "boot.lua"]:348>
[C]: in function 'require'
[love "boot.lua"]:251: in function <[love "boot.lua"]:126>
[C]: in function 'xpcall'
[love "boot.lua"]:362: in function <[love "boot.lua"]:355>
[C]: in function 'xpcall'
Any idea what's wrong?
Sorry it took me a few days to get back about this, I have an idea what this could be, and you can bypass it with an edit to the config.
If you open "~/.local/share/SternlyWordedAdventures", if there's no file called "userConfig" (no extension, plain text) create one with:
return {
window = {
width = 1920, -- or appropriate values for your system
height = 1080,
fullscreen = false,
},
volume = {
music = 1,
effects = 1,
master = 1,
},
}If there is one already, add the window section to it or add the width height definitions to the existing window section. The file needs to be a valid Lua table.You'll probably want to go through the options and set everything then restart the game if you did set that bare minimum config.
I'll change how the code I think is at fault functions to hopefully prevent similar issues in the future for future versions.
Hey, thanks for the reply. Took me a few days to validate. Found another cause for potential error message, which might look like this:
$ Downloads/SternlyWordedAdventuresV47Demo.AppImage Error: Could not initialize SDL video subsystem (wayland not available) stack traceback: [love "boot.lua"]:352: in function <[love "boot.lua"]:348> [C]: at 0x7f68a4d725a0 [C]: in function 'require' [love "boot.lua"]:251: in function <[love "boot.lua"]:126> [C]: in function 'xpcall' [love "boot.lua"]:362: in function <[love "boot.lua"]:355> [C]: in function 'xpcall'I don't understand where it's coming from, but some googling reminded me of a quirks I set some time ago for other applications: SDL_VIDEODRIVER=wayland - after I unset it, the game started.
Glad you got it working! I thought it might have been because my launch script loaded the window module early if the config has no values for resolution set. I already changed V48 so that it delays the window module and user config loading until after the other core modules, I'd be interested to know if that would interact with that setting, or if it would have still crashed anyway.