Maybe Fixed Error when selecting sex after starting new game on operagx modile

[Kamerfer]

Error occurs at around fourth click in the play in window version on the screen where you enter a name. Game works in safari and desktop opera(device type not setting) if i remember correct the game worked in far previous versions around 2024 or mid 2025. Also entered three letter name incase this is what somehow broke it.
Version: 0.9.152-PUBLIC#6707 Error details were not provided by the browser. Stack: Stack information was not provided by the browser. Translation not active.; Hash mismatches; may indicate a section of the save has been edited: None (09:12:13.784) (Core) info: GameState postLoad()

 

[Jacques00]

Unless it gives a different message, that error doesn't really say much besides that the browser doesn't want to issue an error message. Please provide more details if you can. Such as which race you chose, what input device you are using to type with (I assume mobile device's keyboard), or if any other games/sites/translators were running while you were playing.

Unfortunately, my mobile device cannot run that browser app, so I cannot personally test it, but more information is welcome. And no, the name having three letters shouldn't be an issue. However, the game will automatically tell you to re-input a name if it has any illegal (code-used) characters, like brackets.

 

[Kamerfer]

Ipad ios 18.7.2

happens with all species and genders(Just tested)

Input device is onscreen keyboard.

I sometimes use vlc to play music but it doesn't effect it in safari and even when turned off and close it i still get the same error.

It isn't asking me to reenter the name when i use the name ()[]{} but I'm not sure if that is specifically detected.

Cant check if it happens when i load a save as i don't have any saves on my mobile device.

 

[Jacques00]

Okay, I tried to look into it further and while I can't replicate the bug on my end, I've made some changes that may fix the problem. Since I can't see the results on my end, I can't be for sure.

It isn't asking me to reenter the name when i use the name ()[]{} but I'm not sure if that is specifically detected.

The illegal characters should be "<", ">", "[", "]", "\\" and "/", as well as placing a space (" ") as the first character in the string. You mentioning that the square brackets didn't produce a note to re-enter the input clued me in to the variable name used for the note, which is simply named "error" could be the problem.

Because "error" may be used by some browsers as a system-specific object or keyword, that would be bad practice to use--which may have explained why the error message turned up as a blank by the browser. Out of an abundance of caution, I've replaced all instances of variables with the name of "error" with something else.

If this is indeed the issue, hopefully it should resolve the problem for the next release. Feel free to respond to this topic with your results once that happens.