Jump to content

nok1a

Contributor
  • Posts

    657
  • Joined

  • Last visited

  • Days Won

    14

nok1a last won the day on January 8

nok1a had the most liked content!

Additional Information

  • Device
    SG tab 2

Profile Fields

  • Discord ID
    DreaderThanDread#7100

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

nok1a's Achievements

  1. Can you explain step by step how i need to use the script, i don't know all this assembly editing. And i want to test it out. Editing this is not enough for it to work: It's not even the assembly editing that is the problem. First i want to make sure the script finds the right method. Btw i am sure it took quite some work to make the script but i don't get the purpose. It's supposed to modify methods no ?
  2. nok1a

    Find Hitbox value

    Your right. It's per object. So each time a new player enters the match you must search there xyz as well. This can be fuxed with a script or maybe we find another but better value
  3. nok1a

    Find Hitbox value

    I mean, i think you can find the other ones as well. Not sure. Would have to test it out. Your sure the value is only for one skin? When i edited it there was no issue shooting you or my alt account.
  4. nok1a

    Find Hitbox value

    Let me know if works. And if need anything else
  5. nok1a

    Find Hitbox value

    same code
  6. nok1a

    Find Hitbox value

    yeah join. pass: 11124
  7. nok1a

    Find Hitbox value

    I am not sure if what i did is same as yours. I took the xyz coordinates of the colider of the other player: 0.10576991737F;0.12057503313F;0.10601880401F:9 See if this group search works. However i don't think this increase the hitbox. Just the collider of the object because i am not able to come closer to the enemy then the distance of it's collider. But the damage is there. Im not sure if this group search applies to all characters. For all i know every collider attached to different type of character has a different size.
  8. nok1a

    Find Hitbox value

    Is it possible that you need 3 float values for this to work?
  9. nok1a

    Find Hitbox value

    You right, meta and lib are protected. Is why you can't dump it, but i see the symbol names so normally it should give you the class and field name. But i don't think we should care about their protection. Personally i consider that a modding problem. And i don't do modding. We just try to find the good oil pointers. Can you explain me how you find this hitbox so i can properly replicate? When do i do unknown search, do i need to bit in hitrange or is it just the marker that has to aim on the body? Do i increase, decrease? When?
  10. nok1a

    Find Hitbox value

    Unity, it has libunity.so
  11. nok1a

    Find Hitbox value

    You don't really need to. But did it gave you the field and class name? If so you can then search it with this script: Field Offset Finder (#yyzay1k) Or if you know class name and field you can make your own script, which perhaps looks a bit like this: Finding and changing the field offset using the game Guardian script (#48ezjg21)
  12. nok1a

    Find Hitbox value

    I understand. I don't think it's bad to see if this value you found can be found with field finder: Class name and Field offset searcher (#by23kt0q) And then build a script based on that.
  13. nok1a

    Find Hitbox value

    I'm surprised this actually works. Used to try this on other games but the anticheat detected it. Is it a Unity game?
  14. ah, it only works with gg.getResults(). gg.loadResults(sortedFields) gg.getResults(gg.getResultsCount()) gg.editAll('15', gg.TYPE_FLOAT)
  15. local sortedFields = {} local filter = gg.getValues(WeaponBalanceComponent_reloadIterationTime) for i, v in ipairs(filter) do if (v.value <= 500) and (v.value >= 0.0001) then sortedFields[#sortedFields + 1] = {address = v.address, flags = gg.TYPE_FLOAT} end end gg.loadResults(sortedFields) gg.editAll('15', gg.TYPE_FLOAT)
×
×
  • 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.