Wine: RLIMIT_NICE is <= 20, unable to use setpriority safely causing fail start game

Yesterday it all worked fine, and last thing I did was opening the game in question, then closing it and shutting off the computer. Today, first thing I do after booting is starting the game - but it fails.
Noone touched the computer in-between and no updates has been done to the system nor the game.
Booted another computer with the same game installed, same issue all of a sudden.

Lutris is set to stable Wine-GE and the game has been working fine on both since I first tried it out about a year ago.

But now I get this:

Started initial process 41471 from gamemoderun /home/user/.local/share/lutris/runners/wine/wine-ge-8-26-x86_64/bin/wine /home/user/Games/genshin-impact/drive_c/Program Files/HoYoPlay/games/Genshin Impact game/GenshinImpact.exe
Start monitoring process.
gamemodeauto: 
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
Monitored process exited.
Initial process has exited (return code: 1280)
Exit with return code 1280

So I tried a solution I found:
echo "* hard nice -20" | sudo tee -a /etc/security/limits.conf

Which resulted in:

Started initial process 2769 from gamemoderun /home/user/.local/share/lutris/runners/wine/wine-ge-8-26-x86_64/bin/wine /home/user/Games/genshin-impact/drive_c/Program Files/HoYoPlay/games/Genshin Impact game/GenshinImpact.exe
Start monitoring process.
gamemodeauto: 
fsync: up and running.
wine: Using setpriority to control niceness in the [-19,19] range
Monitored process exited.
Initial process has exited (return code: 1280)
Exit with return code 1280

The exit code bothers me here, usually anything other than 0 is bad.

All the above is using direct launch.
The log generated when using the official launcher is too long to include, which is what I normally use, but the reason for client failing is the same as above, and the launcher starts fine, clicking on “Start game” it minimizes as always - but instead of the game starting as it normally would, the launcher is back on screen. Thus tested direct launch as it generates less of a log to read.
Previously, launching directly has been working fine.

After this I tested other WINE-versions (ge-proton, ge-proton-custom, system) and they all fail to launch the game.
Tested turning off DXVK as I found a suggestion to do, didn’t work.

Note though I am using launcher version 1.4.2 and not 1.5.2 as the newer one doesn’t run.

That line about wine rlimit <= 20 is completely normal, I have it all the time
What I’m saying is, that isn’t what’s causing your game to crash, whatever is causing it not to run isn’t generating logs