Jump to content

Lover1500

Ascended
  • Posts

    283
  • Joined

  • Last visited

  • Days Won

    13

Lover1500 last won the day on December 9

Lover1500 had the most liked content!

Additional Information

  • Android
    9.x (Pie)
  • Device
    Oppo

Recent Profile Visitors

10,303 profile views

Lover1500's Achievements

Community Regular

Community Regular (8/14)

  • Very Popular Rare
  • Dedicated Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

190

Reputation

  1. Lover1500

    reload value

    autowin={} --this function is to search your value function searchAutowin() --here you search your value --Let it be we get 1 result. autowin = gg.getResults(1) end --if autowin have a member, then it wont search again. if #autowin==0 then searchAutowin() end --now you have readymade autowin value. --edit like that if you want to edit 0. autowin[1].value = 0 gg.setValues(autowin) You can use many ways for this. not this method only. for better explanation, you can upload a video how you get that value. then its more understandable what to write in script.
  2. @Yuukis such rare information. I'll block pc in my scripts now. just kidding XD
  3. not possible. i think. becuz every field offset values are always in A region. not in Ca.
  4. if you extract the zip file, you'll see dump.cs there
  5. @blocxits dump.cs. i showed how to get it in above video. can use il2cppdumper.com
  6. @blocx you'll know when you mod a game. sure
  7. This is getting dump.cs. This is how i check class name and field offset. you can also learn what is il2cppdumper for and modding.
  8. Actually, i make this script for modders. in dump.cs, the value you find will be like this. search class PlayerProfile check the field offset 0x104. its your value. If you want use hooking, aim that offset. I'll also make a script how you can get the value using update void. So please wait a while.
  9. View File Class name and Field offset searcher Sometimes, we could find the value with gg. But in dump.cs, we dont know which value under which class is the right one for modding. Testing one by one takes time. In those cases, how did you continue your modding journey? This script do search the class name and field offset of the value. So you will easily know what one to be editted. Usage -search your value. -when you get the value, run script. -script will give you class and offset of that value. Submitter Lover1500 Submitted 12/09/2021 Category Tools  
  10. Version 2

    942 downloads

    Sometimes, we could find the value with gg. But in dump.cs, we dont know which value under which class is the right one for modding. Testing one by one takes time. In those cases, how did you continue your modding journey? This script do search the class name and field offset of the value. So you will easily know what one to be editted. Usage -search your value. -when you get the value, run script. -script will give you class and offset of that value.
  11. Dont use gg.getTargetInfo() then. its only for selected process. Do a function that check every process. by yourself. proc/pid etc
  12. You cant. because you editting values in memory. after you edit, it will change. Either using second gg or using other memory viewer can see it. Ahh i see why you ask to check running processes. You are going to detect second gg and if it is running, you will stop your values to edit. like that? wont be easy to detect gg.
  13. You mean gg.getTargetInfo()? can get process name etc from it. yeah. i think it cant be stopped. depend on how you edit values. if you edit hex in Xa, its so easy to find with second gg. What relates between checking running process and protecting against from second gg? i cant imagine what you want.
  14. very good tutorial for me. hope you also do for offsets
  15. We dont understand what you mean too. it will be great if you explains more clear. This is what i think you need. may be wrong ok.lua
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.