
MowdownJoe
Published
Minor to moderate slowdown on the first combat encounter of each session. Had one instance where I waited 5 minutes for the slowdown to abate, and just force-closed the game instead.
Touchscreen would be blocked by the touchscreen keyboard at seemingly random times, usually if there's any form of textbox on screen
Mostly runs perfectly, and the touchscreen is perfect for this kind of game. It can just be a little insistant of popping up the touchscreen keyboard.
Text on cards can be very small and hard to read.
Gameplay scene did not scare properly to screen size, and my graveyard was partially off-screen and hard to look at.
No matter what version of Proton I tried, I would receive frequent disconnects that I would not get on my Steam Deck. Occasionally, I'd get a playable game, but that was rare.
For a while, I found that the game could run on the Steam Deck fine, outside of the known crash at the start of a new in-game day. Now my save files just crash any time I'm in the Abbey. I am unsure what has caused this change in stability. I am not willing to make huge tweaks just to run one game, and having the boot into Desktop to fix the game saves not properly syncing was enough of a hassle.
OS did report the game as hanging repeatedly until the title screen appeared. I was able to just dismiss the alerts asking me to force quit the game. Everything ran fine after that.
Default controller layout, when game is set to use gamepad controls, appears non-functional.
End up immediately seeing a Javascript error on launch (EINVAL: invalid argument, uv_pipe_open)
Interestingly enough, Steam presents an option to install the game natively, but then is unable to find an executable shell script to launch the game.