Yes
Yes, but need to restart MapHack sometimes
Yes, but need to restart D3 sometimes
No, says it's attached but nothing is visible in game
No, stuck on waiting for process
Line to item - OK
Cooldown numer - OK but it could be better centered
If I helped you, click "Give Thanks!"
There is an issue with cooldown feature
1) Run skill with long cooldown
2) Leave game to menu - there is still cooldown numer
3) Make new game - there is still cooldown numer
4) Hit skill again - number does not change
As in this gif: Imgur
If I helped you, click "Give Thanks!"
Please try this version, should also make the cooldown on primary/secondary buttons centered as well. Attachment 62730
Oh, a patch... I haven't tried yet, but I expect 2.6.1.51663 to break the MapHack.
didnt try latest but .50649 doesnt, hear th is down too
You very cool/ Russia with you
thx for your work and the update, especially the TTS option so I get some sort of acoustic heads-up on acient/primal drops..
could you enable that option for goblins and/or basic (non-ancient) legendaries/sets as well?
didn't see a new update going live since I used to start up D3 without the launcher.. not sure they deployed it on EU servers already anyway,
at least for now I can still use the old 50649 on EU for solo play..
€: ok now on restart i got the pop-up that a new version is available.. but I'm not forced to update (yet), old build still works (limited player pool ofc tho I guess)
Last edited by bloblynx; 08-07-2018 at 05:24 PM.
Mine is stuck on waiting for a D3 process
Me too. Stuck on waiting for a D3 Process.
I'm a programmer and I know the basics of the PE header layout, code pages, etc, and I can use windbg to get addresses, method names, global symbols, etc. What I would really, really appreciate is if Enigma or someone with the knowledge could spread the technical know-how about how they are fetching the guids to look for in the SymbolPatcher, or for that matter, how they know that calling the method at the ImageBase + DataSegment.MemoryManager can be used to create a SmallObjectCache. For instance, how was it discovered that there should be a guid/tag to confirm if you invoke the method at memory location "MemoryContext.Current.ImageBase + SymbolTable.Current.DataSegment.MemoryManager" that reads "D26D4257-778C-449E-A50A-C7B068FB8C85"? What hint did you have that the last version's memory manager was located at address "0x0239BAE0"? And did you just take the first RDATA segment address to get the base DataSegment address of "0x141AF1000"?
From what I can tell, looking through the Diablo III64.dmp file, I'm not quite sure how these guids/tags/checks are being deduced (nor how the memory manager is being located, although I see plenty of heap allocation methods from the process dump, etc.). Is there a trick that you're willing to share so that if something were to happen to Enigma, his legacy could be carried on? I have very useful plugins and additions to Enigma's basic software and I'd like to share it very much, but if the entire community has to wait for the neurons inside Enigma's genius brain to fire up (and there's no backup), it makes me really nervous to release anything knowing I don't have the means or knowledge to fix it if Engima is not around.
If you can't help directly, are there any hints, books, or articles you could point me to? I could seriously help out this community by submitting pull requests - if I could figure out how you are figuring these things out!
Well played Blizzard, almost got us!!
xD