
Renari
Published
Was not able to test online due to servers currently being down, will update when I get a chance to test.
EAC will kick you from online matches
Prologue is fully completable on proton 7.0-3, it appears there's some sort of single palyer episode mode that is inaccessible in the beta, that should be fully playable. Online however would kick me from matches about 1 minute into the game.
I also tried proton 6 since I saw other reports saying the game crashes on that version and can confirm the game crashes immediatly on proton 6.
It appears there is some sort of single player episode mode, it's disabled appers to be disabled in the test. So if you only want to play the single player mode, that would appear to work based on the prologue.
bound ZXCVAQW similar to the settings menu
text is massive, preventing mosttext from being readable
I didn't run into any issues that required me to turn on compatibility mode after playing for ~30m.
Very minor issues, appears the game was intended to run on 16:9 so you see some odd animation stuff that was intended to be out of frame.
When messing around with the graphics settings the game felt like it was playing in slow motion, restarting the game seemed to fix the issue. Might be graphics settings related.
Accidentially switched to keyboard mode and had to bind right arrow key to R4 to get back to controller mode.
Runs well ootb, didn't experience any issues, I did switch to Proton-GE to see if it would allow me to enable shaders but it did not.
Requires applying a Ren'Py patch manually to prevent freezing.
Some of the menu text for controls was hard to read.
Game would freeze after a few minutes of gameplay.
It seems the game is launching the exe even on Linux, I had to replace the exe with the provided shell script and make a small change for it to run natively.
Ren'Py issue showing needed patch: https://github.com/renpy/renpy/issues/3978
I also changed MaidCafe.sh
to MaidCafe.exe
and made the following change to the file on line 25:
From
BASEFILE=$(basename "$SCRIPT" .sh)
To
BASEFILE=$(basename "$SCRIPT" .exe)
I've reported these issues to the developer here: https://steamcommunity.com/app/423640/discussions/2/3823047306761765251/
So it's possible they may get fixed.
echo "%command%" | sed s/MaidCafe\.exe/PatchAndRun\.sh/ | bash
Added a file named PatchAndRun.sh
to game directory:
#!/bin/bash
# download updated steam integrations for renpy to prevent freezing
curl -s -o "$(pwd)/renpy/common/00steam.rpy" https://raw.githubusercontent.com/renpy/renpy/d3bc7650febe464519e660420a4c936778bca07d/renpy/common/00steam.rpy
# launch the native version instead of the windows version
bash "$(pwd)/MaidCafe.sh"
Some settings menu text remains hard to read or positioned poorly but it's a menu you'll probalby only visit once.
Developer released an update fixing previously mentioned issues
ACE anticheat
Can open the launcher but after that nothing. It seems the devs are specifically whitelisting steamdeck hardware, so works on steamdeck but nowhere else.
Added I, O and P buttons from keyboard to back buttons to swtich between 2D, 3D and iso views.
While not docuemented, controller is supported, I switched to the gamepad controls. It might be better to just bind the keyboard controls correctly however since the gamepad controls can't be rebound in-game.
Had 2 crashes in a full playthrough, but nothing was lost due to frequent auto saves.
Played through the whole game and it ran pretty well, the gamepad controls are mostly sufficient however there is some minior things you are missing out on, like being able to hover over buffs to see what they say they do. You can view these via the touch screen with a little jankyness (since it will try to play cards).
Launcher doesn't fit correctly on the screen, after fiddling with the maximize button a few times I was able to get it to scale to the screen correctly so I could hit the launch button. Sadly after hitting lauch you get the same error everyone else is mentioning "Your game environment is abnormal. Please close the game and try again." Followed by the game closing.
mangohud %command%
I was getting crashes pretty consistantly at the first picture scene but after swapping around between proton versions and turning off and on mangohud it just stopped happening altogether and now I can no longer reproduce it on any version of proton with our without mangohud.
I did run into some issues but I was later no longer able to reproduce them, so the exact cause/fix is unknown. I was having craches on proton-cachyos and GE-Proton9-26, I then switched to proton 9.0.4 and turned off mangohud and the crashes stopped. However after that I switched back to proton-cachyos and GE-Proton9-26 and was no longer getting the crashes there even with mangohud turned back on, so whatever the issue was, it seemed to go away.
Installed luxorpeda using wine cellar, selected luxorpeda as the compatability tool, launched the game and when the luxorpeda menu popped up you select the nw.js runtime, an the game came right up.