-
Active Member
anyone could get the codegenerator to work to update all offsets for 2.4.3? For me its crashing
-
Active Member
@Dolphe, I saw your reply in FK forum saying that you will release a 64-bit version too. Were you able to find all offsets of the 64-bit client?
-
Contributor
Originally Posted by
johnbl
@Dolphe, I saw your reply in FK forum saying that you will release a 64-bit version too. Were you able to find all offsets of the 64-bit client?
The offsets is not the problem in 64bit, the thing is every collection / Allocator / structs etc has changed. So you cannot just compile it to x64 and change offsets and it will work.Enigma.Memory also needs to be able to handle long adresses instead of ints ( 4 vs 8 byte pointers):
I might release Enigma.X64 haven't decided yet, initially I wont.
Basically after every pointer offset will shift +4 ( next item ), works maybe 75% of the times because they also have some padding in 32bit that has been truncated to a 64bit or even removed.
Summary: No point of me to release offset, everything will break anyways.
-
Post Thanks / Like - 1 Thanks
johnbl (1 members gave Thanks to Dolphe for this useful post)
-
Legendary
It's updated for 2.4.3.42655 (32-bit) now. Enjoy
-
Post Thanks / Like - 2 Thanks
johnbl,
reciol (2 members gave Thanks to enigma32 for this useful post)
-
Member
Thank you very much! My little maphack just came back to life.
-
Banned
thank you for the update!!!
-
Post Thanks / Like - 1 Thanks
ilexpit (1 members gave Thanks to ThornStorm for this useful post)
-
this new update is welcome. thank you very much <3
-
Post Thanks / Like - 1 Thanks
hazar (1 members gave Thanks to Snickers? for this useful post)
-
Member
Thanks for your work on this project enigma. I'm curious if we will see a 64 bit version as well. Keep up the good work bud =)
-
Legendary
Originally Posted by
jusdaveman
Thanks for your work on this project enigma. I'm curious if we will see a 64 bit version as well. Keep up the good work bud =)
I'm curious too :3
-
Contributor
hi, is it possible to access AABB of actors assets? how can i get them to draw bounding boxes around mobs?
-
Contributor
d3.codegen new addresses
hi, I have run the codegen project and it updated enigma SDK for 2.5 diablo III client (with some missing addresses) i didnt check the offsets, but
this is what i have so far (credits to @Enigma32)
Code:
//#error Could not find AttributeDescriptors :( Running generator again with a minidump present might help
public const int AttributeDescriptors = 0x00000000;
//#error Could not find LevelArea :( Running generator again with a minidump present might help
public const int LevelArea = 0x00000000;
//#error Could not find LevelAreaName :( Running generator again with a minidump present might help
public const int LevelAreaName = 0x00000000;
public const int VideoPreferences = 0x01E0F438;
public const int SoundPreferences = 0x01E0F4D8;
public const int HotkeyPreferences = 0x01E0F528;
public const int GameplayPreferences = 0x01E0F9A8;
public const int SocialPreferences = 0x01E0FA10;
public const int ChatPreferences = 0x01E0FA40;
public const int MapActId = 0x01FEAED0;
public const int SNOGroupsByCode = 0x02059EA0;
public const int SNOGroups = 0x02059FB8;
public const int ObjectManager = 0x0205C0F0;
public const int ObjectManagerPristine = 0x0205C0F4;
public const int ApplicationLoopCount = 0x0205C16C;
public const int LocalData = 0x0205D3A0;
public const int ContainerManager = 0x02124644;
public const int MessageDescriptor = 0x02124650;
Last edited by dabnoj; 03-22-2017 at 05:23 AM.
-
Post Thanks / Like - 1 Thanks
yelax (1 members gave Thanks to dabnoj for this useful post)
-
Member
Unfortunately I'm unable to get to the Expandable Container of ActorCommonData. Either the layout of ObjectManager has changed so that x7C8_Storage is not really Storage. Or Storage has changed so that x158_Ptr_232Bytes_ActorCommonDataManager is not actually a pointer to the actor common data manager. Or the ActorCommonDataManager has changed and x00_ActorCommonData is no longer a pointer to the ActorCommonData expandable container.
OR, they are getting rid of ActorCommonData in favor of Actors and Objects (although I can still couldn't retrieve either a container of actors or objects...) I also got the same offsets as you (although I did get some of the missing values due to using a dump file.
PS:I also had no luck using the following on ObjectManager:
public Ptr<ExpandableContainer<Actor>> x988_Ptr_RActors { get { return ReadPointer<ExpandableContainer<Actor>>(0x98; } }
The same went for:
public Ptr<ActorManager> x98C_Ptr_816Bytes_ActorManager { get { return ReadPointer<ActorManager>(0x98C); } }
Both eventually show themselves as not what they totally appear to be....
Last edited by owen654321; 03-22-2017 at 08:02 PM.
-
Active Member
Hello,
just substract 0x10 :
public Ptr<ExpandableContainer<Actor>> x988_Ptr_RActors { get { return ReadPointer<ExpandableContainer<Actor>>(0x988; } }
become
public Ptr<ExpandableContainer<Actor>> x978_Ptr_RActors { get { return ReadPointer<ExpandableContainer<Actor>>(0x978; } }
etc.
NOTE : ActorCommonData struct is smaller by 0x8 in 2.5.0
-
Post Thanks / Like - 1 Thanks
dabnoj (1 members gave Thanks to bastiflew for this useful post)
-
Member
Originally Posted by
bastiflew
Hello,
just substract 0x10 :
public Ptr<ExpandableContainer<Actor>> x988_Ptr_RActors { get { return ReadPointer<ExpandableContainer<Actor>>(0x988; } }
become
public Ptr<ExpandableContainer<Actor>> x978_Ptr_RActors { get { return ReadPointer<ExpandableContainer<Actor>>(0x978; } }
etc.
NOTE : ActorCommonData struct is smaller by 0x8 in 2.5.0
Can I ask how you figured these things out? I tried looking at memory dumps - is there a better way? Trial and error? Advice would be GREATLY appreciated, and then I can assist with providing this information in subsequent updates/releases.
-
Legendary
Updated for 2.5.0
MapHack demo should be working.
-
Post Thanks / Like - 3 Thanks