The official one is now the same as my fork. The latest only support remove and no more install. Dmnt will always be tightly coupled to atm version. Version mismatch will likely cause crash.
Thanks for the info, could this be fixed? when Jump to target using a pointer cheat to heap, it doesn't show heap+xxxxxxxx (shows main+xxxxxxxxxx) in Memory Explorer (top left)
Last edited by dsrules,
Is this a new issue with 99e? I remember doing something to allow for heap as a start of pointer chain and I may have affected something with my recent change for preparation of application (as oppose to applet ) pointer search
I think it is something new in beta99e or maybe introduced in pr2, I don't remember seeing that part (main+×××××, 10 digits address) in previous versions
it's a nice feature, knowing which memory region the pointer jumps to
Last edited by dsrules,
they are waiting.
I see what you are referring to. This is a display that I put for me to check the static address in the bookmark.
Every memory explorer instant has an associated bookmark. Every bookmark starts with main/heap/alias followed by a list of offsets that forms the pointer chain. There is also a single legacy offset which I have not use for some time but decided it’s good for the future purpose of application mode pointer search. This legacy offset is basically offset that will reach the target address without more offset
So if you have a pointer that starts from main you will get main + and if you have a pointer that starts from heap you will get heap +. The target may be a heap address but if you pointer starts from main you get main +.
Last edited by TomSwitch,
yeah, currently there is no way to tell which memory region you are in when using Jump to target on a pointer cheat, it would be a good feature to have
oops, I never paid attention to that part lol, only focused on the region+xxxxxx part
Post automatically merged:
@TomSwitch , if alias region, it also shows Memory RW Heap
Last edited by dsrules,
That is true. It shows the segment type. Alias is another abstraction above segment type.
I will consider your request. For now move left will jump back one level and you will see the pointer as A+ if the display mode is smart (default)
Post automatically merged:
@dsrules what your opinion on this.
Here is the general scheme of application pointer search.
You need at least two game session to perform a search. You use bookmark to create dump and also record the target address. When you have two or more dump of the same target you can run Breeze in application mode and pick two dump from a list of dumps you have and proceed to perform pointer search. The results will be added to current bookmark file.
The thing is dumps can be used for multiple targets one at a time. As long as a bookmark has the correct static address you can assigned it for pointer search. The problem is helping users to identify which is the matching bookmark. A bookmark file has the meta of the session recorded when created and that get refreshed when a clean up is performed. If a clean up is performed bookmark recorded from a different session will no longer have the static address as per captured but will get a refreshed static address (i.e may be wrong one).
Here is the question:
Is it better to say user you make sure the bookmark file has only bookmark of the correct session and breeze reject if meta of dump and bookmark file don’t match. Or user use name of bookmark to manually keep track
Application pointer search is going to be bound by memory the number of dump that can be used otherwise it is storage and time bound when it comes to num offset, range and depth. May take a long time but I assume most users that perform pointer search are very patient people
I planned to make it support suspend but it’s going all the way until limit then iterate the next one so go for long search likely won’t give good result in short time.
You can run game to test result and do more search if needed. Dump is frozen in time like the PC base pointer search.
Just like Breeze pointer search I am doing it slow and easy. Thinking about it more than coding anything most of the time
Last edited by TomSwitch,
