Legacy Of Kain Soul Reaver 1 & 2 Remastered has been released.

It contains a lot of bonus material, including a few areas that have been scrapped before release.

Exploration of one of those areas may end up _crashing_ the game...

...Imagine that...

It's always the 'Poll Of The Day' on some other site that reminds me that there's an actual word for the fear of the Friday the 13th...

You know your e-Post Office really sucks when you receive only now scammers' emails that are _decades_ old.

I've recently learned how committing of the Save Data to file works in my project.

The file is updated w/ _each change_ made to the settings.

Worse yet - the file is updated even when _no actual change_ is made due to the setting already being at its highest / lowest value possible.
/*
e.g. 5 is maximum sound volume.
- You try increasing the sound volume.
- Setting can't get any higher, so remains unchanged.
- *Update the Save Data*.
*/

What kind of abusive masochist would do that?

// Yes... there's always blame.

There was this one time when we've managed to upload a Debug build to Google Play Store.

On the same day we had to create a new build w/ fixes, have the testers perform smoke tests, then switch to some fairly quick overall tests.

If nothing were to come up during those tests, the build was supposed to be passed over to the submission manager for release.

Things weren't going that smoothly in the beginning, w/ the first two builds being broken in one way or another.

Finally, however, we managed to create a properly working build.

QA hadn't had that much time to test it, but no major problems were identified && given the deadline we had to submit it.

The next workday it turned out that the tester responsible for passing the approved build over to the submission manager gave him the Debug build.

The submission manager none the wiser uploaded that build for release.

Result?

The users who managed to update their game got their save data wiped... sort of.

It looked that way given the Debug build was communicating w/ a different server.

In the aftermath of that situation, we had to repair the damage && upload the correct build as quickly as possible.

Also, ever since then a huge text 'DEBUG' was added to the loading screens of Debug builds to make people very aware of which build they were looking at.

As for any repercussions for the tester responsible for the mess, or the submission manager - I have no idea.

They were both still working there, so at the very least none of them got fired because of this.

Tester has found an issue: controller input stops working when performing certain steps.

Creates a report and provides an attachment.

The attachment depicts some menu where, at first, the cursor moves around various options, then simply stops moving.

The problem:

Since this is a simple in-game recording, there is neither an overlay of the controller w/ a visual representation of the input actually being provided but not working, nor there is a camera recording available where I can see the tester pressing buttons on a controller.

For all I know, the tester put down the controller / stopped pressing buttons.

...I've also seen reports of animations not working... w/ fucking screenshots attached.

How the fuck can you see something not being animated in a fucking static picture?