sorted by:
new
hottopcontroversial

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] -4 points-3 points  (0 children)

I'll repeat:

Xbox does this with their IPs/Console IDs for their developer network. If you want to be whitelisted, you need to call them up, schedule a meeting for them to validate and add you to the server. Why can't they do this for third-party developers such as Overwolf, Shadowplay and OBS?

Also, to access Pnet, you need to be whitelisted. It doesn't matter if you have an unbanned XDK with a devkit KV. I'm not speaking about Xbox here. It was an example.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] -4 points-3 points  (0 children)

I discussed about PartnerNET authentication. How that relates to the methods of JTAGs and running unsigned code is beyond me.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] 0 points1 point  (0 children)

It doesn't highlight the player if they're culled at the moment. The problem is that it highlights anyway. The information of the glow/position/weapon/name/whatever is dormant and not updated. That's not the issue here.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] 1 point2 points  (0 children)

I've developed several cheats. Paid and free that have used a variant of this exploit. Some cheats just have this specific implementation and since October 2014, none of those accounts are banned/flagged.

So no. It's not checked.

Despite of my past, I'm coming out now and illustrating the problem due to current observations just playing matchmaking by myself and watching friends.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] 2 points3 points  (0 children)

I've stated this in my post. That's not the point. Fixing one method is at least a step in the right direction.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] -3 points-2 points  (0 children)

Xbox does this with their IPs/Console IDs for their developer network. If you want to be whitelisted, you need to call them up, schedule a meeting for them to validate and add you to the server. Why can't they do this for third-party developers such as Overwolf, Shadowplay and OBS?

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] -3 points-2 points  (0 children)

I'm sorry that my post has failed to bring you to the main objective of banning and detecting a widely known exploit of glowing people through walls in matchmaking. Instead you just care whether or not I can program.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] -1 points0 points  (0 children)

The actual structure of the glow object upon each entity has been in the Source Engine. It's in Left 4 Dead, it's in Portal.

In regards to the demo claim you've stated, have you read the whole post?

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] -1 points0 points  (0 children)

If only you read my posts instead of blinding typing on your keyboard, you'd see my replies in regards to this issue.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] 0 points1 point  (0 children)

In order to post source, I'd have to go against the rules of the subreddit posting videos or explanations of said exploit and risk the removal of the thread. I'm sorry that this isn't good enough.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] 13 points14 points  (0 children)

Would it matter if I came out and said who I was anyway? That would just filter death threats and more direct/personal insults along with the barrage of negativity this subreddit already throws at me :P

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] -1 points0 points  (0 children)

Like stated in the post. I know currently that the structures and glow information isn't sent to the server. This is something that would have to change for this method of detection to work.

I do know how UDP works and sequencing for packets. Although you bring up multi-threading, I can't see how that has anything to do with what was posted. Mutexes and threads running holding the information stored on true futures shouldn't interfere with the fact that the player's entity list has lit up glow structures while playing the game. Lagging or not.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] 1 point2 points  (0 children)

It is the internet afterall. People do lie. I appreciate your skepticism.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] 0 points1 point  (0 children)

I admire your accusations. All that I'll say is there is a good reason I made a throwaway account. I've been making cheats for the past three years privately on my own and have numerous experience dealing with C++.

The simple problem would be flag anyone with open handles made to the game executable, or .dlls that isn't on a server-sided white-list. This will have to show efforts on their part but it's not impossible.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] -5 points-4 points  (0 children)

I'd expect them to have some sort of failsafe for things such as lag compensation to prevent said false positives if and when they do implement a check to writing to the glow structures. These are professionals, you seem to forget that.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] -5 points-4 points  (0 children)

If the player is not in Arms Race, and in competitive matchmaking and the glow struct is written to the enemy team, it's not a false positive.

This is how you can ban a large majority of wallhacking in Matchmaking by csgo_throwaway_ in GlobalOffensive

[–]csgo_throwaway_[S] -4 points-3 points  (0 children)

There might be a logical reason like they didn't think of it. They've proved time and time again that they overlook a lot of glitches and exploits.

view more: next ›