new update danger zone not working. what is the offset now?

macacodobem commented 5 years ago

For me too, don't working after danger zone updating. need change 0xAC34; I think

jefcostaa commented 5 years ago

Anything work here, I tried 00 to 100 but nothing

diogosilva212 commented 5 years ago

For PC is 0xA3F8, maybe someone can "convert"...

macacodobem commented 5 years ago

not working 0xAC38

diogosilva212 commented 5 years ago

@imoplex broooo!

macacodobem commented 5 years ago

@aKalisch where are you?

macacodobem commented 5 years ago

@jefcostaa Are sure u tried 00 to 99? or another fake news? because 0xAC38 not working

diogosilva212 commented 5 years ago

We just need someone who can adjust the "0xA3F8" to mac...

macacodobem commented 5 years ago

wrong

ethano8225 commented 5 years ago

lol you cant really just "convert" it to mac. the dude tried 38 but it didnt work lol he even said that

diogosilva212 commented 5 years ago

On the previous update the guy said "Computed by looking at the difference in iGlowIndex offset between previous and this update." And one said "in fact, I saw the last 3 changes. realized the variable was being incremented by 16 (in hexadecimal)"

diogosilva212 commented 5 years ago

I don't know... I tried to post on "unknowncheats" forum, but they didn't approve my comment lol

diogosilva212 commented 5 years ago

Someone posted it and said "Computed by looking at the difference in iGlowIndex offset between previous and this update" xD

diogosilva212 commented 5 years ago

That's the problem, we don't know the method...

ethano8225 commented 5 years ago

well it went up 24 so try whatever that is (like 34+24, idk hexadecimal) right? lmao

diogosilva212 commented 5 years ago

It was 0xAC00, then 0xAC10, then 0xAC20 and then 0xAC34...

diogosilva212 commented 5 years ago

I'm pretty sure this is so easy for whoever understands the basics of this... I'm feeling dumb.

diogosilva212 commented 5 years ago

But don't try all those numbers. For Pc it was 0xA310, 0xA330, 0xA344 and now is something completely different: 0xA3F8

diogosilva212 commented 5 years ago

I don't know nothing about this, unfortunately

macacodobem commented 5 years ago

Will the "unknowncheats" staff help with the problem? u got send the topic In forum?

ethano8225 commented 5 years ago

oh then just try to look upevery pc csgo pointer for the past few years and if there is another F and we also have the numbers for that same update we should be able to guess

diogosilva212 commented 5 years ago

They didn't approve my reply on the "Structs offsets" forum, where the pc ones where posted, don't know...

ethano8225 commented 5 years ago

actually hold up, i think it changed by going down 21 points, we could try that (like make 34 into 13)

diogosilva212 commented 5 years ago

Nop, didn't work.

ethano8225 commented 5 years ago

idk just an idea... imma go to bed now lmao gotta wake up real early tmrw

diogosilva212 commented 5 years ago

@aKalisch @imoplex @paulinelymorgan someone heeeelp

ghost commented 5 years ago

ill have a look into it... gimme half an hour

diogosilva212 commented 5 years ago

I maybe have something to help. We just need the pattern scanner and then convert the decimal number to hexadecimal

diogosilva212 commented 5 years ago

For mac, this is the decimal on previous updates: 0xAC00 44032; 0xAC10 44048; 0xAC20 44064; 0xAC34 44084

ghost commented 5 years ago

just use a for loop to iterate over...

diogosilva212 commented 5 years ago

@fugiefire that's chinese to me bro, sorry...

ghost commented 5 years ago

and its not incrementing in a pattern, its dependent on what comes before in the binary.

macacodobem commented 5 years ago

@fugiefire come to save us!

diogosilva212 commented 5 years ago

What I was saying was that before, on this hack, you could use this tool (https://github.com/gabsens/Pattern-scanner-for-OSX) to discover the offset. Once you had that value, you only had to convert to hexadecimal...

diogosilva212 commented 5 years ago

Save us, please @fugiefire <3

amcgregor commented 5 years ago

As an open source developer (not of cheats, sadly) it is onslaught threads like this that cause me the greatest distress, and shake whatever faith in humanity I may have still possessed. (No, I don't know the offset; have some patience, people.)

ghost commented 5 years ago

^ yes please can everyone have a lil patience and not tag us?

diogosilva212 commented 5 years ago

@amcgregor dude, we're just trying to figure this out on our own. Personally, I don't know shi*. It's exactly to avoid tagging people like you that we're trying to solve this...

ethano8225 commented 5 years ago

I mean they the smart ones right lmao

diogosilva212 commented 5 years ago

Yup, but they weren't here before, so we tried :) Now we wait.

ghost commented 5 years ago

i think its either ac49 or ac96 lemme try

ghost commented 5 years ago

nvm its neither lol

ghost commented 5 years ago

tried 49 so prob 96

ghost commented 5 years ago

lol my b then

ghost commented 5 years ago

tf does strstr() do? @amcgregor

diogosilva212 commented 5 years ago

Lmao just saw that on the previous two updates, people in here just got lucky cause the value incremented the same (decimal) xD

ghost commented 5 years ago

huh?

diogosilva212 commented 5 years ago

In one update, the decimal value of "m_iGlowIndex" went from 44032 to 44048 (+16) so in the next update some guy added more 16, making it 44064 and it actually worked

diogosilva212 commented 5 years ago

On the next one, someone saw that on the Pc value it was +20, so added +20 on 44064 and it worked again xD

ethano8225 commented 5 years ago

maybe it’s -16? Idk how work lmao

iseekwonderful / csgoGlow

new update danger zone not working. what is the offset now? #263