Unexpected error: Propagating error from GS 1 (method: createGame): Fatal error during lordsofxiditadmiral setup: Class

[admiralspunky]

I can't get Lords of Xidit to start. Other games, I request read-only access, make a new project, overwrite my project with the actual one, then go to Play Now and hit Express Start, no problems. But for some reason, when I do that exact set of steps with Lords of Xidit, it gives me an error when I try to start the game. Am I doing something wrong?

Unexpected error: Propagating error from GS 1 (method: createGame): Fatal error during lordsofxiditadmiral setup: Class Lordsofxiditadmiral not found

[RicardoRix]

Given it renames all the instances of all the game_name to the new one, it's likely something to do with that.

What is your class called in game.php ?

[admiralspunky]

The class in game.php is just called Lox. Capital L, lower o and x.

[Tisaac]

The class in game.php is just called Lox. Capital L, lower o and x.

Why ? It should match the name of your project.

[admiralspunky]

The class in game.php is just called Lox. Capital L, lower o and x.

Why ? It should match the name of your project.

I don't know why it didn't get renamed; that's why I'm asking. And, looking through the code, I see several things called lordsofxiditadmiral, but I also see several called Lox. Why did the project renamer rename some, but not all, of the 'Lox's?

[Een]

Most likely guess: non standard project, where the developer did some renaming of their own.

[admiralspunky]

Most likely guess: non standard project, where the developer did some renaming of their own.

It was someone called Pierre Scelles. I could just find and replace the text back to what it's supposed to be, but the original change was probably for a reason, right? I'm also not entirely sure how Xidit works on the main site, when it doesn't work in the Studio. Does the main site not check the names of projects?

[Een]

I have not worked on this specific codebase, but I see two possibilities:
- the developer had renamed everything that needed to be for it to work, but the replacement when copying the project somehow messed up something
- something was changed on the studio codebase since the last deploy in prod.