Breeze beta100+ Unity and UE aware cheat making

[ranma99vn]

@TomSwitch
beta 108.7a
i got freeze when try to look into class field (ZL ZR Y) this cause a hard rest the switch
in the game Dave the diver (not all some time)
the second game is Legacy of Kain Ascendance if you have the game try watch this line 0x1F51FB4 then use class field

this is my finds if im using manually choose class field (ZL ZR Y) and press A on it it open just fine, but if im use the key short cut it will freeze in my end

 

[TomSwitch]

@TomSwitch
beta 108.7a
i got freeze when try to look into class field (ZL ZR Y) this cause a hard rest the switch
in the game Dave the diver (not all some time)
the second game is Legacy of Kain Ascendance if you have the game try watch this line 0x1F51FB4 then use class field

this is my finds if im using manually choose class field (ZL ZR Y) and press A on it it open just fine, but if im use the key short cut it will freeze in my end

I observe some not class field will cause the yellow panic screen. Using A key is fine would be very surprising. I think it is to do with the address please double check this press A is ok observation. Real class field no crash, not class field I have observed with Dave the diver oxygen search causing yellow panic screen. The search will find address that will crash when you use the class field button.

 

[NeoGranzon]

I observe some not class field will cause the yellow panic screen. Using A key is fine would be very surprising. I think it is to do with the address please double check this press A is ok observation. Real class field no crash, not class field I have observed with Dave the diver oxygen search causing yellow panic screen. The search will find address that will crash when you use the class field button.

This screen also happens with R-Type III Dimension 1.0.3 and not in other games,why does the Switch run out of RAM?

 

[TomSwitch]

This download link is for members of the Nintendo SWITCH Cheat Codes Download group. Join the group to see it. It's free.

Register Log in

@ranma99vn @NeoGranzon If you're sure you know how to reproduce the crash, please try this version and let me know if it's fixed. Gen2fork has changed, please reinstall.

 

[ranma99vn]

This download link is for members of the Nintendo SWITCH Cheat Codes Download group. Join the group to see it. It's free.

Register Log in

@ranma99vn @NeoGranzon If you're sure you know how to reproduce the crash, please try this version and let me know if it's fixed. Gen2fork has changed, please reinstall.

try it with Legacy of Kain Ascendance using shortcut key no crash

 

[NeoGranzon]

This download link is for members of the Nintendo SWITCH Cheat Codes Download group. Join the group to see it. It's free.

Register Log in

@ranma99vn @NeoGranzon If you're sure you know how to reproduce the crash, please try this version and let me know if it's fixed. Gen2fork has changed, please reinstall.

Perfect,now using class view shortcut it doesn't crash anymore on R-Type III Dimension.

 

[TomSwitch]

This download link is for members of the Nintendo SWITCH Cheat Codes Download group. Join the group to see it. It's free.

Register Log in

I redo the focus mode. To experience it in full delete breezeoptions. To just check out the new action button arrangements load default focus.

Now the default focus should be good for most task without overflowing to the next menu except memory explorer.


A hint to tell user they can change focus. When the button on the lower right is selected.


Now help text is shown below so user no longer have to choose seeing help text and seeing the search setting


redesign the focus menu.


Customizing action is now easier.


Save layout now only save the menu being worked on. You will not overwrite menu then you did not intend to change

With the new default focus user can set visible only to 1 without too much inconvenient. That is the default for new install. This will provide safety for user who may otherwise accidentally activate buttons that are not visible. Without setting visible only to 1 all the buttons that are not in the focus menu but have short cuts can be activated. This negate some of the protection of hiding the buttons in focus mode. If you used to set it to 0 you may want to consider setting it to 1.



The focus file format has not change and all your customization will not be affected with this update.

 

[TomSwitch]

This download link is for members of the Nintendo SWITCH Cheat Codes Download group. Join the group to see it. It's free.

Register Log in

 

[dsrules]

This download link is for members of the Nintendo SWITCH Cheat Codes Download group. Join the group to see it. It's free.

Register Log in

get depth+1 ptr > Add pointers at current depth//this one is confusing to me, sounds like add the same pointers again at the current search depth

last_range > Final offset range//would love to get rid of this option if possible, it causes more trouble for me instead of helping, I often need to adjust both max search range = last range to find pointer on non unity games, I don't think it is needed to limit it even on unity games, or I could probably just leave it at a large offset since the number of Targets are the same

also, if possible to raise the max depth limit to above 12? (yes there are cheats that require depth 14 or 15)
and can't use Jump forward when depth 12 is reached, or at least increase the Jump forward limit?

 

[TomSwitch]

get depth+1 ptr > Add pointers at current depth//this one is confusing to me, sounds like add the same pointers again at the current search depth

You prefer the original? Suggestion to make it easier for user to understand is welcome.

last_range > Final offset range//would love to get rid of this option if possible, it causes more trouble for me instead of helping, I often need to adjust both max search range = last range to find pointer on non unity games, I don't think it is needed to limit it even on unity games, or I could probably just leave it at a large offset since the number of Targets are the same

last range or final offset range more descriptive?
It's there to allow big range and small last range. If you want big you can always leave it big and forget about it. Small one does make you miss some good pointers once in a while, actually only once for me.
I add it to switch to offset 1 range 40000 as my default.
Need to remember that it is there is IMO the only bad thing about it.

also, if possible to raise the max depth limit to above 12? (yes there are cheats that require depth 14 or 15)
and can't use Jump forward when depth 12 is reached, or at least increase the Jump forward limit?

It is very easy, I only need to change PTR_SEARCH_MAX_DEPTH= in the source code and recompile.

If you are ready to test the impact to different pointer search scenarios I can give you that up to 15 version or up to any value you want to do the test on. (Bigger payload means running out of memory faster, different game engine will be affected differently by this, Unity can probably survive to reach the depth you want but others may suffer).

The last change to 32bit offset has bigger impact than increasing the depth limit from 12 to 15. How much have you used the 32bit version? Any concern there?

I can also just change it to 15 and see if there is any complain like I did the 32bit offset.

Post automatically merged: Jul 20, 2026

Added 3 and recompiled

 

[dsrules]

You prefer the original? Suggestion to make it easier for user to understand is welcome.

ptr +1 at least I know it means current search depth +1 more depth (depth 2 > depth 3)
but Add pointers at current depth, to my understanding = depth 2 > depth 2

last range or final offset range more descriptive?
It's there to allow big range and small last range. If you want big you can always leave it big and forget about it. Small one does make you miss some good pointers once in a while, actually only once for me.
I add it to switch to offset 1 range 40000 as my default.
Need to remember that it is there is IMO the only bad thing about it.

It is very easy, I only need to change PTR_SEARCH_MAX_DEPTH= in the source code and recompile.

If you are ready to test the impact to different pointer search scenarios I can give you that up to 15 version or up to any value you want to do the test on. (Bigger payload means running out of memory faster, different game engine will be affected differently by this, Unity can probably survive to reach the depth you want but others may suffer).

The last change to 32bit offset has bigger impact than increasing the depth limit from 12 to 15. How much have you used the 32bit version? Any concern there?

I can also just change it to 15 and see if there is any complain like I did the 32bit offset.

depth limit shouldn't matter much as we much stop searching when the memory limit message shows up, how far it could go depends on the game, I have seen max range 0xb8 ran out of memory at depth 6 or 7 (forgot which game) and many goes up to depth 12 with no problems

32bit is mostly useful on some retro style games or games ported from older gen, I think it is still good to have it


depth 12+ works but when I open Bookmark Menu atmosphere crashs 010000000000100d


update: if there are existing bookmarks with less than depth 13, opening Bookmark menu will not crash if the highlighted bookmark pointer is less than depth 13, it crashes when scroll down to the depth 13 bookmark, btw the max it could go is only up to depth 14

 

[TomSwitch]

ptr +1 at least I know it means current search depth +1 more depth (depth 2 > depth 3)
but Add pointers at current depth, to my understanding = depth 2 > depth 2

Reverted to old button label

depth limit shouldn't matter much as we much stop searching when the memory limit message shows up, how far it could go depends on the game, I have seen max range 0xb8 ran out of memory at depth 6 or 7 (forgot which game) and many goes up to depth 12 with no problems

32bit is mostly useful on some retro style games or games ported from older gen, I think it is still good to have it


depth 12+ works but when I open Bookmark Menu atmosphere crashs 010000000000100d
View attachment 582805View attachment 582806

update: if there are existing bookmarks with less than depth 13, opening Bookmark menu will not crash if the highlighted bookmark pointer is less than depth 13, it crashes when scroll down to the depth 13 bookmark, btw the max it could go is only up to depth 14

I need to make three changes rather than one. Earlier I did not change MAX_POINTER_DEPTH so bookmark memory is not enough which result in the crash you saw. After I changed that I have to change file version of Breezeoptions, this means your file will be wiped, back it up first before running this version. It was a bad decision to make Breezeoptions a binary file, every time the offset of things change it needs to be wiped.

*** BACKUP your Breezeoptions *** before using this version

 

[dsrules]

Reverted to old button label

View attachment 582850
I need to make three changes rather than one. Earlier I did not change MAX_POINTER_DEPTH so bookmark memory is not enough which result in the crash you saw. After I changed that I have to change file version of Breezeoptions, this means your file will be wiped, back it up first before running this version. It was a bad decision to make Breezeoptions a binary file, every time the offset of things change it needs to be wiped.

*** BACKUP your Breezeoptions *** before using this version

3a crashes when open Bookmark menu on any games with bookmark file data

update: new 3a bookmark file works fine, I guess old bookmark files are also not compatiable with the new version

update2: +3 can open +3a bookmarks, but +3a crashes when open pre +3a bookmarks

 

[TomSwitch]

3a crashes when open Bookmark menu on any games with bookmark file data

update: new 3a bookmark file works fine, I guess old bookmark files are also not compatiable with the new version

update2: +3 can open +3a bookmarks, but +3a crashes when open pre +3a bookmarks

Yes, forgot to mention that. Because the size if different the bookmark files are now corrupt. I never put versioning in that so it cause crash. I thought a while back I put a size check to not open bookmark file if size mismatch the internal record, I suppose that wasn't working to help with this incident.

Post automatically merged: Jul 21, 2026

actually it was size in the header vs size of file and not number of bookmark, so it won't work here, only when file is corrupted due to some other error, not change in bookmark size

Post automatically merged: Jul 21, 2026

+3b has a check for old bookmark and will rename them instead of loading them. A new bookmark file will be opened with the new format. 3b has a version in the bookmark file.

 

[jinsheng]

 

[dsrules]

+3b has a check for old bookmark and will rename them instead of loading them. A new bookmark file will be opened with the new format. 3b has a version in the bookmark file.

3b tested ok

 

[TomSwitch]

Turns out that with 3b and probably all versions, you can use jumpbackmatch to create ultra long pointer chain and crash. This version suppose to fix that.

 

[dsrules]

Turns out that with 3b and probably all versions, you can use jumpbackmatch to create ultra long pointer chain and crash. This version suppose to fix that.

when custom shortcuts = 1, are you able to use assign the ZL button?

 

[TomSwitch]

when custom shortcuts = 1, are you able to use assign the ZL button?

ZL is by default assigned to radial mode. If you don't use redial mode then yes. Otherwise your short cut won't work, you can assign and it will work when you clear or change radial_modeKey

press A once to make it blank

View attachment WIN_20260723_22_27_26_Pro.mp4
when you hold ZL the selection is by the absolute position of the left stick. You can quickly more to any button this way. You can let go of ZL for easier precision navigation.

 

[TomSwitch]

@dsrules, it's been about a week since I put the +3C version up for testing, so I'd like to hear your thoughts on it.

There are two areas I'm interested in:

1. Did it break anything besides causing users to lose their custom key setup?
2. Is it worth the effort? Does it provide enough value to justify disrupting existing users who may have spent a lot of time setting up their shortcuts?

I am not in a hurry, so if you want more time to evaluate that is fine.