How to make working checkboxes and editboxes in trainer menu?

marek1957

Expert Cheater
Dec 16, 2017
81
0
6
#1
Hi People,
I was looking for tutorials about how to make a trainer in Lua language with checkboxes and editboxes but I only found tutorials about making trainer with hotkeys. I don't wanna use hotkeys, I just wanna make a trainer with working checkboxes and editboxes. If anyone can help me? I was trying to do something by myself but checkboxes are not working and edit boxes are not working.

I just have a script for manually write amount of money:


So like yu can see, I need checkbox with editbox to get this script working properly.

If someone have good tutorials about making trainer in lua language with checkboxes and editboxes, I will be very grateful.

My CT table:
http://www47.zippyshare.com/v/8vKIDJuH/file.html
 

marek1957

Expert Cheater
Dec 16, 2017
81
0
6
#4
Blayde, Last question --> I know how to save memory region but I don't know how to open once again two memory regions from cheat engine and then compare them. I need that info because sometimes I don't have CT table but I am using other people trainers to get to know how they are working - so I think that my idea will work if I open the game, then open the Cheat Engine, then go to Memory View and I will save all memory region, then I will run a trainer, activate one function and once again save all memory region to next compare two memory regions to see the changes in codes. Do you know maybe how can I open this saved memory region to compare them if in any memory region are changes?
 

Blayde

Expert Cheater
Aug 25, 2017
220
1
16
#5
marek1957 post_id=28430 time=1513688351 user_id=11389 said:
..... I don't know how to open once again two memory regions from cheat engine and then compare them...
You catch me. :lol:
I have never used memory compare (maybe once). I can not help you. Sorry
marek1957 post_id=28430 time=1513688351 user_id=11389 said:
...then I will run a trainer, activate one function and once again save all memory region to next compare two memory regions to see the changes in codes.
Don't do that. You will learn nothing and ..... It's some kind of stealing.
 
Top Bottom