I do play on nightmare though and I don't know if that is required for the legendaries to generate.
According to the official wiki it is:
Legendary items are rare and powerful pieces of equipment that drop inside Ancient Rifts and randomly from tougher enemies while playing on Nightmare difficulty.
Wellm yea, I know about that and that's not what I mean. I'm deliberately altering the code past where nightmare is checked on loot generation so I say again: I don't know if nightmare is requited [with the script changes] for legendaries to drop. Either way it'll affect loot quality.
How to use this cheat table?
Install Cheat Engine
Double-click the .CT file in order to open it.
Click the PC icon in Cheat Engine in order to select the game process.
Keep the list.
Activate the trainer options by checking boxes or setting values from 0 to 1
Hey @Master_Builder, which debugger are you using? I have the problem with "Failure determining what ES2-Win64-Shipping.UItemLib::CheatUnlockAll" as well, despite ES2-Win64-Shipping.pdb being in the same folder.
Hey @Master_Builder, which debugger are you using? I have the problem with "Failure determining what ES2-Win64-Shipping.UItemLib::CheatUnlockAll" as well, despite ES2-Win64-Shipping.pdb being in the same folder.
VEH
Though now that you made me look there, I do see an option to "not load pdb files" and if that's checked for you and others, that's one possibility.
I wouldn't think the debugger would be why since it'll load symbols without the debugger being attached.
But my settings if it helps:
Hey Master_Builder, thanks for checking!
Sadly it isnt that easy I was already using the same settings as you.
Are you using by chance any lua plugins/external tools?
Here are md5 checksums of my ES2-Win64-Shipping.pdb: b7cc9b9e0cfff97d2f52049b8e85bc30 and ES2-Win64-Shipping.exe: e902dfa8e7f82a8b3aa24644226cf56fvia md5check.
Hey Master_Builder, thanks for checking!
Sadly it isnt that easy I was already using the same settings as you.
Are you using by chance any lua plugins/external tools?
Here are md5 checksums of my ES2-Win64-Shipping.pdb: b7cc9b9e0cfff97d2f52049b8e85bc30 and ES2-Win64-Shipping.exe: e902dfa8e7f82a8b3aa24644226cf56fvia md5check.
If you want to investigate this further.
I'll check the hashes when I get home.
As for plugins, CE is relatively vanilla. I don't remember adding any third-party plugins or external tools or the like, but it is locally compiled which is something I started doing when they removed the installer-less zip packages to shovel their malware/adware riddled installer.
Though I know I've had stuff like this working long ago before all that started, so I don't think that's the cause.
I do also have visual studio with c++/c#, windows dev kits, and windows debugging tools installed for unrelated projects which may or may not affect this.
I know there's a "symbols search path" something or other on the 'File' menu of the memory browser which may yield different results. (Mine is empty.)
You could try attaching winDbg64 to the process which should also be able to load the PDB.
Soo, after a Deep dive with windbg64, reading stuff up, breaking things horrible, i found a program (ChkMatch), which can check if a .pdb can be used for a program.... and my .pdb is mismatching.
Same program can be used to fix said mismatch, but the file seems to be corrupt - because activating a part of the cheat table that would require the .pdb now crashes the game!
Soo, after a Deep dive with windbg64, reading stuff up, breaking things horrible, i found a program (ChkMatch), which can check if a .pdb can be used for a program.... and my .pdb is mismatching.
Same program can be used to fix said mismatch, but the file seems to be corrupt - because activating a part of the cheat table that would require the .pdb now crashes the game!
I suggest you remove both the pdb and the exe and verify files via Steam. This'll re-DL both, assuming both still exist in the package. (Maybe even verifying again after to ensure no corruption occured in transit.)
My guess is the pdb might have been corrupted in the DL but you normally wouldn't notice this due to the game not requiring it to run. Check hashes afterwards. It's also possible that different regions have different mismatching exe/pdb files. I remember someone earlier saying they couldn't get CE to load the pdb and were in the SEA region.
Pirated copies which alter the exe might also result in the pdb no longer matching.
Hey Master_Builder, thanks for checking!
Sadly it isnt that easy I was already using the same settings as you.
Are you using by chance any lua plugins/external tools?
Here are md5 checksums of my ES2-Win64-Shipping.pdb: b7cc9b9e0cfff97d2f52049b8e85bc30 and ES2-Win64-Shipping.exe: e902dfa8e7f82a8b3aa24644226cf56fvia md5check.