-
Notifications
You must be signed in to change notification settings - Fork 556
-
Notifications
You must be signed in to change notification settings - Fork 556
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
Pokemon Ultra Moon cheats very unstable on v10 #1272
Comments
Could you provide the actual text of the codes, along with your installed Ultra Sun version and the version the codes were made for? |
Ultra Moon, rather |
Cheats were from this file: https://github.com/FlagBrew/Sharkive/blob/2b75942800d80a48bedf6d1658f1efb4083362ab/db/00040000001B5100.txt Retail digital download of Ultra Moon patched to v1.2 Specifically, these codes as far as I can tell. I rolled back to v9.1 but can do various configuration testing to be sure if you'd like. [(START+L)Wild Pokemon Shiny, (START+R)Disable v1.2] [(Hold START and Open OPTIONS menu)Access the PC from anywhere v1.2] |
What's your 3DS system version? |
11.10.0-43U |
This seems to be a kernel bug (null deref), blame Nintendo I guess. |
There's a race condition in the kernel between the moments when:
Basically you have to pray this doesn't happen. |
I don't know if this is the same issue, but here goes: Ultra Sun [No Outlines v1.2] |
V1.5 Pokemon Y Using this: https://github.com/FlagBrew/Sharkive/blob/master/db/0004000000055E00.txt [(Hold R)Walkthrough Wall v1.5] It doesn't work, and crashes afterwards. |
I rarely get crashes on ultra moon |
Nintendo bug, not related to Luma3DS; resolving. |
After updating to v10, enabling a small amount of the cheats for my device that used to work just fine result in a number of crashes at various points in Pokemon Ultra Moon. The two that I'm able to absolutely pinpoint as being a culprit are the Wild Pokemon Shiny toggle and the Hold Start and open Options to access PC. See attached dmp
crash_dump_00000000.zip
.
The text was updated successfully, but these errors were encountered: