The VBA Bug Compatibility Mode disables itself whenever I close mGBA

[LOuroboros]

I mentioned this in the last issue I brought up, but I haven't gotten a response in the past 2 days and I'm tremendously unsure about whether this is a bug or not, so I decided to open a GitHub issue to bring it up in a more formal manner.

Just as I mentioned in the title, the VBA Bug Compatibility Mode gets disabled every time I close mGBA.

Is this the intended behavior? If so, isn't there a way to enforce it? If not, could a way to do it be implemented?

Having to re-enable it everytime sounds like it'd get annoying quick.

[endrift]

Game overrides apply per-game. Saving it and then not loading a game saves it to...nothing.

That said, I'm not sure this override is saved anyway at the moment. It's kind of difficult because the way it's saved is based on the internal header code, and ROM hacks tend to not change that. I don't think it would be a good idea to apply that for all Ruby ROMs, hacked or not, for example.

That said, it is a usability disaster as is if it's not saved at all. I should try and make a push for per-game configs in 0.10...

[LOuroboros]

That said, I'm not sure this override is saved anyway at the moment.

It's not. If I enable the override and then boot up the same ROM Hack I originally intended to play, the RTC works, but if I then go to Emulation -> Shutdown, and boot it up again without closing mGBA, the RTC marks 0:0 instead of the actual time yet again.