Grid Sage Forums

Cogmind => Bugs => Fixed Bugs & Non-Bugs => Topic started by: Hippasus on September 20, 2020, 11:33:17 AM

Title: Incorrect total score shown after self destruct [v10.0]
Post by: Hippasus on September 20, 2020, 11:33:17 AM
I just self destructed on the first mat floor but it reports I have a score of 22,406!

This just so happens to be the score of my previous run...

So yeah, bug.
Title: Re: Incorrect total score shown after self destruct [v10.0]
Post by: Kyzrati on September 20, 2020, 03:20:04 PM
Hi Hippasus, yeah I've heard of this happening once before, last year, but can't actually repeat it. (The one case I have on record actually happened in the Scrapyard, even...) There must be something really weird about the conditions, because people self-destruct there fairly frequently and it doesn't normally occur. Pretty sure this started becoming a (rare) thing due to the scoresheet overhaul for Beta 9.

I need more data in order to solve something like this, like a save file would be ideal, in case there's something involved there, but of course unless you made a backup manually, you likely won't have a save from before you self-destructed since run data is removed at that point. (The only way you'd have a save is if you had stopped the run on an earlier day, since your save would be backed up as part of the daily backups, but that's a rare and unlikely coincidence for an early-game run...)

Interestingly we don't even have scoresheets for runs below-9, so we can't even investigate that for details xD (that's done to keep all those scoresheets from polluting the data for "real" runs that get off the ground)

Wish I knew how to repeat it, since this is the second time now. Guess I'll try again and see...
Title: Re: Incorrect total score shown after self destruct [v10.0]
Post by: Kyzrati on September 24, 2020, 04:17:54 AM
Okay, I've managed to repeat and solve this one, thanks :)

I realized that the only difference between the two reported instances and my own tests were that a scoresheet wasn't produced in your case (due to the depth), whereas I test in debug mode which always produces a scoresheet. Easily repeatable as long as a run ends normally and produces a scoresheet, then you self-destruct before -9 in the next run in the same session.

(Since no scoresheet was produced the tally was not actually recalculated under the new system introduced for Beta 9.)