Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
After posting this on Steam, I searched the forum using the keyword “AZERTY” and noticed I wasn’t the only one reporting this issue.
I only found the support link by chance, while reading a totally unrelated post where a dev had shared it. It’s not mentioned anywhere obvious.
I’ve submitted the bug officially here: https://rawfury.atlassian.net/servicedesk/customer/portal/1
Maybe you could consider pinning the support link somewhere, so people don’t have to randomly stumble upon it — or just to know it exists at all?
@Helen - Raw Fury
Hi,
Thanks for your input, but I’d like to clarify a few things — because while you're right that W or the arrow keys might technically work for some, it doesn't mean the issue isn’t game-breaking in practice.
First, on an AZERTY layout, the expected behavior is for Z to move forward — not W. The rest of the game respects this layout (menus, character movement, etc.), so this inconsistency is not intuitive at all.
Second, there is no in-game prompt, remapping option, or indication that other keys like W or arrow keys work. So unless a player guesses or tries every key on their keyboard, they will assume pushing Jacklifts is simply not possible — which can soft-lock progression in certain layouts.
Third, saying “just use a controller” or “try random keys” is not a viable solution. It’s equivalent to saying “just plug in a steering wheel if the accelerator doesn’t work” — it’s not a fix, it’s a workaround that hides the actual problem.
So yes, it is a bug — and when it leads to players believing they're stuck, abandoning a run, or spoiling themselves trying to find out what they missed, I’d argue that’s pretty game-breaking, especially in a game built around procedural runs and time investment.
No offense meant, but this deserves a real fix — not assumptions that “it’s fine because you can do X if you know.”
The bug report link is included in the pinned FAQ discussion.
Probably would've wasted another 20 hours if I hadn't googled it lol.