Author | Message | ||||||
---|---|---|---|---|---|---|---|
Re: Quest rule for handling "Cancel" button in dialog?
| Hacker_Alex posted: (8th Mar 2017, 04:43 pm)I'm using Game Trainer Studio, and you are able to some what add custom code I think, but I'm pretty sure you're very limited with what you can do, and there is no documentation of how to do anything.Sordie posted: (8th Mar 2017, 04:34 pm) I'll need to familiarize myself with assembly more, and then I could do this with cheat engine I'm sure. You can do quite a bit with cheat engine and the trainer creator, but I've just been lazy to bother learning, and checking into it. Callum Yea, I can understand why this is not a good way to go about it now. I never considered the mentioned potential issues in doing it this way. --- EO Resources/Guides: â—„ eobud.boards.net â–º
|
Re: Quest rule for handling "Cancel" button in dialog?
| callum posted: (8th Mar 2017, 03:21 pm) Just for the record EO.Addons does nothing more than what you call "hexing the client". Most of what EO.Addons does is edit the memory inside the client, much like Shaynes program does only he achieves similar results for way less effort because he takes the time to follow pointers back where as I just go the long way around and replace code. Most hacks he does are way more efficient than EO.Addons. The thing where EO.Addons shines is it's ability to work with executable code rather than just values in memory. The most complicated part is the "CodeSize" function that can disassemble IA86 machine code, following JMPS, JE, JNE, JG RETS, etc.. until it works out the size of a procedure. It can then take functions of the client and move them somewhere else (adjusting relative jmp's and pointers) replacing them with new code provided by an addon whitest preserving the functionality of the original code. Basically allowing addons to insert their own code at any point in the client and still allowing the original code to be executed. But!!!! My point is this is all done through nothing more than "hexing the client". All it's doing is reading and writing memory in the client like shayne does. Anything EO.Addons does could be implemented with shaynes app. Infact, it's about time we worked together XD EDIT: "Disassemble IA86 machine code" is an exaggeration. It knows instruction sizes and the op-codes of instructions that branch and how to follow them =P --- http://sordie.co.uk http://twitter.com/@SordieEO
|
Re: Quest rule for handling "Cancel" button in dialog?
| Apollo posted: (8th Mar 2017, 08:41 pm)Hacker_Alex posted: (8th Mar 2017, 04:43 pm)Sordie posted: (8th Mar 2017, 04:34 pm) Pretty sure he didn't mean EO when he said "other game I play with private servers" in the first paragraph. @Sordie &Shayne I'm definitely not accusing you guys of anything, please don't think I was aiming at at you guys in the last post. In fact you guys are at the other end of that argument where you've both made contributions that help the community. As much as I love the interest in client editing lately I'm still rooting for an official c++ client release.
|
Re: Quest rule for handling "Cancel" button in dialog?
| Sordie posted: (9th Mar 2017, 02:40 am)I'd love to learn to do the types of things you do. I really wouldn't even know where to start though. =dcallum posted: (8th Mar 2017, 03:21 pm) Exactly because of what you've stated basically, it would be neat to do something more complex and versatile, then simply editing the actual values in memory. It would be really cool to make the client behave more so how you want, kinda like how you do with your addons. Don't think that I know so much, because I don't.. At least 90% of what I know and do with client modification, is trial and error, and logical guessing. I find the odd new trick to help ease the debugging process, and look for patterns in memory to help also. I'm still trying to wrap my head around all the different functions within the eo client. There is so much to go through.. It's hard to know which functions do what sometimes, and which modifications would apply to which function. I couldn't really do much to help you currently, as I have very little experience in programming/assembly, but I can provide any addresses/opcodes you may need. Feel free to ask if there is something specific. Maybe I can help more in the future also once I really get into assembly, and learn more important stuff. Callum Don't worry, I don't take offense very easily anyways, especially over the internet.. I never thought your intent was to offend anyways.. xD I agree about finally having a custom client done in c++. That would be the best end result. It will be a long time before a fully functional client is actually released. That is why I mess with debugging and modifying the client. Bypass as many client side limitations as possible, while we await a custom client. It's all we can do for now unfortunately. --- EO Resources/Guides: â—„ eobud.boards.net â–º |