Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A gameshark code that works on VBA-M (SVN r878) doesn't work on mGBA #2297

Closed
LOuroboros opened this issue Sep 2, 2021 · 6 comments
Closed
Labels
feature:usability UX issues due to unclear UI
Milestone

Comments

@LOuroboros
Copy link

LOuroboros commented Sep 2, 2021

Title.
I need to use a gameshark code to generate shiny Pokémon in a ROM Hack of Pokémon Emerald to check out something, and while the code works normally on my preferred version of VBA-M, it doesn't work on mGBA.
It's worth to note that this is also happening with a clean ROM of Pokémon Emerald, the same ROM that can be generated by building Pokeemerald.
explorer_768
explorer_769
explorer_770
explorer_771

I thought it was worth bringing up in case it's something that can or should be fixed on mGBA's end.
Perhaps I'm just adding the code incorrectly? I wouldn't rule it out since I can be tremendously dumb at times.

The gameshark code being used: F3A9A86D 4E2629B4 18452A7D DDE55BCC
And just in case it's relevant, the ROM Hack is called "Pokémon Shadow Specter".
EDIT: Oh yes, and after introducing the code I reset the game by going to File -> Recent too, not sure if it was needed or not.

@endrift
Copy link
Member

endrift commented Sep 2, 2021

You need to split it into two lines. The fact that it even lets you put it in as one long line is...a bug.

@LOuroboros
Copy link
Author

You need to split it into two lines. The fact that it even lets you put it in as one long line is...a bug.

Since it's 2 lines of 16 characters each without counting blank spaces, couldn't mGBA handle it automatically?

Less troubles for the user 👀

Thanks for the clarification though.

@endrift
Copy link
Member

endrift commented Sep 2, 2021

Yes, that's why I called it a bug and not user error.

@endrift endrift added the feature:usability UX issues due to unclear UI label Sep 2, 2021
@endrift endrift modified the milestones: mGBA 0.9.3, mGBA 0.10.0 Sep 18, 2021
@RunisDauphin
Copy link

What year was released VBA-M r878? I think VBA-M 2.0.0 Beta 2 was released in 2015.

@endrift
Copy link
Member

endrift commented Oct 5, 2021

Please keep it on topic.

@RunisDauphin
Copy link

My point was: why keep such an old version of the emulator? Would not it make more sense to compare it with the current state of other emulators (or recent versions of this one)? Maybe that cheat is conflicting with something that was solved a decade ago.

rtomasa pushed a commit to rtomasa/mgba that referenced this issue Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature:usability UX issues due to unclear UI
Projects
None yet
Development

No branches or pull requests

3 participants