Well, your previous VBA 24 is a resurrected VBA 20, and you said GBA emulation isn't changed in it. VBA-m is useful since it fixed emulation glitches in some GBA games. Wouldn't it be a good idea to merge VBA 24's GB/C core with VBA 24-m's GBA core?
It has been using the v24 GBx core since the first day it was created.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
That's about it. If you have two cheats enabled and then uncheck one of them (to disable it), then the other cheat stops working too even though it's checked and enabled.
ReyVGM wrote:
When searching for a cheat, you often find the codes in the ram bank change, which makes the code start with "90" instead of "01".
That does sound more like a feature than a bug[/quote]
Problem is that codes that start with "90" don't work on previous VBA versions or any other emulators. Bear in mind that the actual address in the game doesn't start with 90, it's the cheat engine that tries to add the code starting with 90 instead of 01.
ReyVGM wrote:
Please please disassociate save states from retaining all the options, cheats and configurations. I hate that every time I load a save state, it reverts all my options, cheats and configuration to the way it was when I made the save state.
I agree with that, I'll add it to the feature request[/quote]
I actually requested that years ago on the VBArr dev page and it was Accepted. But it never got implemented.
I don't think there is a point to continue on the 7.24 branch (aka. "v20 branch").
EDIT: But I keep updating all of the three v20 descendants nonetheless.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do