Re: Minecraft Dungeons Item Edit (MS Store and Launcher)
Posted: Thu Nov 26, 2020 6:21 am
My game crashes when i try to change the item my game crashes do you have any suggestions?
Community Cheat Tables of Cheat Engine
https://fearlessrevolution.com/
Use the file MichaelJMAD posted a few days ago with updated items. Its a few posts up.Ghost Jays wrote: ↑Thu Nov 26, 2020 6:21 amMy game crashes when i try to change the item my game crashes do you have any suggestions?
It doesn't workMichaelJMAD wrote: ↑Thu Nov 19, 2020 12:16 amOk co it appears the one of to 2 scripts are working
A friend and I have been testing and it seems that the Dungeons-Win64-Shipping.CTDungeons.CT = MS Store Version (Build: 1.5.0.0_4841501)
Dungeons-Win64-Shipping.CT = Launcher Version (Build: 1.5.0.0_4841501)
is throwing an errorNot sure really what needs to be done to fix thatError while scanning for AOB's : INJECT_EquipmentEdit Error: Not all results found
We have updated the Item IDs for the Dungeons.ct
And the IDs should be the same for the win64, however the above-stated means we cant test It.
This is still the OPs script I take no credit for that, CPT_Mike updated the IDs and I tested. I am unable to work out the issues with the win64 version
Code: Select all
aobscanmodule(INJECT_EquipmentEdit,Dungeons-Win64-Shipping.exe,4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8 12) // should be unique
alloc(newmem,$1000,"Dungeons-Win64-Shipping.exe"+87A37B)
Yea this worked, however, I still cant change the item. I can add enchants and change the lvl, etc. However, i cant change the item to another item. Ideas why?aSIMetrical wrote: ↑Tue Dec 01, 2020 6:19 amSo it appears with the 1.6.0.0_1983486 update the array of bytes for Dungeons-Win64-Shipping.exe has changed particularly the last byte:
4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8 "02" which resulted in the "Not all results found" error. After searching for the array of bytes of "4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8", less than 20 records appeared, I disassembled the memory region of each result, one at a time, and added a breakpoint at the beginning of the array and clicked on an item my inventory. If the breakpoint wasn't hit, I knew it wasn't the correct array.
Anyhow long story short, in my case at least, it turns out the new byte is 12. That being said, updating lines 11 through 12 in the table that MichaelJMAD posted to the following worked for me.
Though, I have found that any "graphical" updates as far as the icons go will not update unless you reload the map or exit to the main menu and reload.Code: Select all
aobscanmodule(INJECT_EquipmentEdit,Dungeons-Win64-Shipping.exe,4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8 12) // should be unique alloc(newmem,$1000,"Dungeons-Win64-Shipping.exe"+87A37B)
If someone else is able to try this and let me know if it also worked for them, it would be appreciated.
Okay, so I apologize for the delay, I was testing this at 1:00 in the morning my time. I was dead tired and after testing, I realized that there are Two Arrays of Bytes that have 12 at the end. Therefore a conflict may occur which, can cause some issues. There are two other arrays that are unique:TBC_Miles wrote: ↑Tue Dec 01, 2020 7:37 pmYea this worked, however, I still cant change the item. I can add enchants and change the lvl, etc. However, i cant change the item to another item. Ideas why?aSIMetrical wrote: ↑Tue Dec 01, 2020 6:19 amSo it appears with the 1.6.0.0_1983486 update the array of bytes for Dungeons-Win64-Shipping.exe has changed particularly the last byte:
4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8 "02" which resulted in the "Not all results found" error. After searching for the array of bytes of "4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8", less than 20 records appeared, I disassembled the memory region of each result, one at a time, and added a breakpoint at the beginning of the array and clicked on an item my inventory. If the breakpoint wasn't hit, I knew it wasn't the correct array.
Anyhow long story short, in my case at least, it turns out the new byte is 12. That being said, updating lines 11 through 12 in the table that MichaelJMAD posted to the following worked for me.
Though, I have found that any "graphical" updates as far as the icons go will not update unless you reload the map or exit to the main menu and reload.Code: Select all
aobscanmodule(INJECT_EquipmentEdit,Dungeons-Win64-Shipping.exe,4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8 12) // should be unique alloc(newmem,$1000,"Dungeons-Win64-Shipping.exe"+87A37B)
If someone else is able to try this and let me know if it also worked for them, it would be appreciated.
Code: Select all
aobscanmodule(INJECT_EquipmentEdit,Dungeons-Win64-Shipping.exe,4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8 52) // should be unique
alloc(newmem,$1000,"Dungeons-Win64-Shipping.exe"+88083B)
Code: Select all
aobscanmodule(INJECT_EquipmentEdit,Dungeons-Win64-Shipping.exe,4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8 92) // should be unique
alloc(newmem,$1000,"Dungeons-Win64-Shipping.exe"+8808FB)
Yea it still crashes when i try to change an item, maybe the item list isnt up-to-date so it breaks? Is there a more current version of the cheat tables? When I click on an item to change it, it shows the item ID and a number string, then i select the item i want it to be and it's the text name. I dont know if this affects anything.aSIMetrical wrote: ↑Wed Dec 02, 2020 1:02 amOkay, so I apologize for the delay, I was testing this at 1:00 in the morning my time. I was dead tired and after testing, I realized that there are Two Arrays of Bytes that have 12 at the end. Therefore a conflict may occur which, can cause some issues. There are two other arrays that are unique:TBC_Miles wrote: ↑Tue Dec 01, 2020 7:37 pmYea this worked, however, I still cant change the item. I can add enchants and change the lvl, etc. However, i cant change the item to another item. Ideas why?aSIMetrical wrote: ↑Tue Dec 01, 2020 6:19 amSo it appears with the 1.6.0.0_1983486 update the array of bytes for Dungeons-Win64-Shipping.exe has changed particularly the last byte:
4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8 "02" which resulted in the "Not all results found" error. After searching for the array of bytes of "4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8", less than 20 records appeared, I disassembled the memory region of each result, one at a time, and added a breakpoint at the beginning of the array and clicked on an item my inventory. If the breakpoint wasn't hit, I knew it wasn't the correct array.
Anyhow long story short, in my case at least, it turns out the new byte is 12. That being said, updating lines 11 through 12 in the table that MichaelJMAD posted to the following worked for me.
Though, I have found that any "graphical" updates as far as the icons go will not update unless you reload the map or exit to the main menu and reload.Code: Select all
aobscanmodule(INJECT_EquipmentEdit,Dungeons-Win64-Shipping.exe,4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8 12) // should be unique alloc(newmem,$1000,"Dungeons-Win64-Shipping.exe"+87A37B)
If someone else is able to try this and let me know if it also worked for them, it would be appreciated.
andCode: Select all
aobscanmodule(INJECT_EquipmentEdit,Dungeons-Win64-Shipping.exe,4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8 52) // should be unique alloc(newmem,$1000,"Dungeons-Win64-Shipping.exe"+88083B)
I stated in my last post however, you will need to click off and click back on the item to see the change. The icon in the menu will not update until you either reload the map or exit to the main menu and come back in.Code: Select all
aobscanmodule(INJECT_EquipmentEdit,Dungeons-Win64-Shipping.exe,4C 8B 03 48 8D 54 24 30 48 8B C8 48 8B F8 E8 92) // should be unique alloc(newmem,$1000,"Dungeons-Win64-Shipping.exe"+8808FB)
As for not being able to change the item, I don't know the cause as it worked for me. Try either of those options and see if it works better for you. They both worked for me.
Code: Select all
[ENABLE]
aobscanmodule(INJECT_EquipmentEdit,$process,80 79 08 00 48 8B F9 0F 85 * * * * 48 * * * * E8)
alloc(newmem,$20,INJECT_EquipmentEdit)
alloc(newmem2,$2000,1100000000)
label(p_equip)
label(code)
label(return)
newmem:
code:
mov [p_equip],rcx
cmp byte ptr [rcx+08],00
mov rdi,rcx
jmp return
p_equip:
dq
INJECT_EquipmentEdit:
jmp newmem
nop 2
return:
registersymbol(INJECT_EquipmentEdit)
registersymbol(p_equip)
newmem2:
[DISABLE]
INJECT_EquipmentEdit:
db 80 79 08 00 48 8B F9
unregistersymbol(INJECT_EquipmentEdit)
unregistersymbol(p_equip)
dealloc(newmem)
dealloc(newmem2)
Since, I don't own the game & gamepass is unavailable in my region & it's stupidly tedious to buy gamepass in my case...
Cake-san wrote: ↑Thu Dec 03, 2020 4:26 amSince, I don't own the game & gamepass is unavailable in my region & it's stupidly tedious to buy gamepass in my case...
So, what's the error that you get when trying to activate the table in ms store version ? I read that some people mentioned about the game object being obfuscate in latest update of ms store version but I can never clarify nor find for solution since I don't have that version....