Adding extra hitbox to maps to stop aim bot? GUID Bans better?

[Web*]

Im unsure about the way that Cheats and VAC run, But taking some time looking into it I think I know a little. With a aimbot the cheat is obviously reading in real time where the other players on the map are, after digging into some videos on youtube is seems that these cheats can be made to aim at different parts of the players, ie headshots, chest shots etc.

Could VAC/Valve add a random "ghost player" close to each player, so then when the aimbot is activated it will aim at that "ghost" rather than the player?

As you can see im not too familar with it but building on this idea may lead somewhere.

Next, why not have a GUID/HWID ban? As games such as CS:GO are so cheap some people dont mind getting banned and just opening a new account and cheating again, surely the downsides to GUID/HWID Bans get out weighed by the benifits? It seems to work for other companies, just a thought

[Chara the Explorer]

the Portaller님이 먼저 게시:

We're assuming that the cheat is inactive or that I was playing a different game (say, CS:S) that the cheat managed to not affect (say it was for TF2).

Aaah, Okay then, thought it would be a good idea to clear that up.

[Pillerpusher]

This sounds really good, actually

[Web*]

Ill try and clear something up, with a GUID/HWID ban it would be for the specific game, so if you were banned in CS:GO you could still play CS:S etc

If your brother got banned on your account its a bit of tough luck really, when you sign up to steam you agree that you will keep your login details secure and that if you share them willingly and someone else causes a issue its still the account holders fault.

I bet VAC have heard every excuse under the sun, when mistakes have been made (just a few days ago in fact) VAC knew what had happened and reinstated all the accounts, that was a server error their end not false positives from the anti cheat.

Cafe accounts have different rules to personal accounts, but that does not mean that they have also agreed to do their best to prevent cheating.

Unlike other anticheats VAC do not run instant bans, they are checked over time, I believe that this is to give time to check for new coding bugs from updates etc that could cause the flag. So you may be cheating today but not recieve the ban until 2 weeks time. This is more than fair considering they are giving the player the benifit of the doubt over buggy code.

The idea with the "ghost" player I had and just thinking about it a little more could work, imagine having a "twin" that it attached to you, you dont know it is there, and it has unlimited HP, the twin would be 1.2 the size of yourself, so no matter what angle you look at it the "ghost" would always bit that little bit closer to the enemy, this would then be point 1 for the aimbot to lock onto.

[(SOGA) SouthernBoy]

IT does not matter tho if the account was banned and any member or etc had been rejected for play because of the ban. It does matter why the ban was given in the first place, in which I already stated, that machine and or hardware is not a viliable way to determine a VAC ban for many stated reasons, but can be usefull for other purposes.

As far as the ghost effect, this means that more code would have to be added to such games and may lead to more false coding events, so the concept maded, may be sound does not mean it is a good thing to do and use as a VAC ban tool. (AS stated cheat dev would notice this backdoor and try to utlize it too).

Thanks for atleast trying to help with the problem of cheating anyways and any ideas should be considered, but not neccessaryly incorporated.

[Satoru]

The false premise is that GUID/HWID are

1) Unique
2) Uniquely identify something
3) Are not circumventable

Which isn't true. All anti-cheat mechanisms are based on SERVER SIDE authentication targets. The server can uniquely identify accounts in some way and then use a blacklist to remove them from the system.

HWID/GUID are CLIENT SIDE systems. The client has to generate some ID locally and then servers that tot the system. This means that these IDs are not unique and cannot be counted on to be verified. They are mainly used to prevent collisions.

Note do not mistake HWID/GUID bans as being equivalent to 'console bans' issues on Xbox live or PSN. These are again server controlled because the serial # of the console CANNOT BE ALTERED since it's fused into the system. Thus ensuring that you have an absolute 1:1 correlation between a piece of hardware and your blacklist.

[(SOGA) SouthernBoy]

Satoru님이 먼저 게시:

The false premise is that GUID/HWID are

1) Unique
2) Uniquely identify something
3) Are not circumventable

Which isn't true. All anti-cheat mechanisms are based on SERVER SIDE authentication targets. The server can uniquely identify accounts in some way and then use a blacklist to remove them from the system.

HWID/GUID are CLIENT SIDE systems. The client has to generate some ID locally and then servers that tot the system. This means that these IDs are not unique and cannot be counted on to be verified. They are mainly used to prevent collisions.

Note do not mistake HWID/GUID bans as being equivalent to 'console bans' issues on Xbox live or PSN. These are again server controlled because the serial # of the console CANNOT BE ALTERED since it's fused into the system. Thus ensuring that you have an absolute 1:1 correlation between a piece of hardware and your blacklist.

You are right Satoru !

But even a console which has been given away and or sold to someone else, may in affect cause what is known as a false positive, and should not be use as absolute 1.1 correlation. This is one of the problems with that type of banning system too.

[The Longest Rose]

Web님이 먼저 게시:

If your brother got banned on your account its a bit of tough luck really, when you sign up to steam you agree that you will keep your login details secure and that if you share them willingly and someone else causes a issue its still the account holders fault.

But I did not agree that I will never allow anyone else to play a game on their account on my computer.

[Silicon Vampire]

You did agree that anything that happens with the account, you are responsible for...

[Satoru]

(SOGA) SouthernBoy님이 먼저 게시:

You are right Satoru !

But even a console which has been given away and or sold to someone else, may in affect cause what is known as a false positive, and should not be use as absolute 1.1 correlation. This is one of the problems with that type of banning system too.

Back in my home town, every other street corner had someone doing console mods. The guys at Gamestop always knew when an Xbox Live ban wave happened. Because mysteriously overnight EVERYONE would be coming in to 'trade in' their xbox console. A used xbox console was basically a banned one.

But the above aside, xbox only banned modded consoles, so there wasn't really any false positives there. The console is modded, and therefore is banned. Being sold to someone else isn't relevant from their perspective.

[(SOGA) SouthernBoy]

Satoru님이 먼저 게시:

(SOGA) SouthernBoy님이 먼저 게시:

You are right Satoru !

But even a console which has been given away and or sold to someone else, may in affect cause what is known as a false positive, and should not be use as absolute 1.1 correlation. This is one of the problems with that type of banning system too.

Back in my home town, every other street corner had someone doing console mods. The guys at Gamestop always knew when an Xbox Live ban wave happened. Because mysteriously overnight EVERYONE would be coming in to 'trade in' their xbox console. A used xbox console was basically a banned one.

But the above aside, xbox only banned modded consoles, so there wasn't really any false positives there. The console is modded, and therefore is banned. Being sold to someone else isn't relevant from their perspective.

I was agreeing with you and just added the statement that using (whether console or not) machine and or hardware is not the way to go for a VAC ban. lolo ("A false positive" used in my statement was referring to a ban, not the reason per say of the ban.)

[The Longest Rose]

Silicon Vampire님이 먼저 게시:

You did agree that anything that happens with the account, you are responsible for...

Correct, therefore if I get banned because someone messed with their account on my computer, that violates the contract as it did not occur on my account. This is why VAC will never hardware ban. It would, of course, be acceptable to have VAC check your hardware to go from normal scans to super-mega-powerful scans.

[Silicon Vampire]

But your account can only be affected if you join a VAC secure server.

Your computer, it's security and what's on it is also your responsibility.

[<(Z)>KingTut]

Im just saying aimbot is the most annoying ♥♥♥♥ in the whole world...technically this is a feasible solution but would cause a myriad of issues like being able to predict where the second hit box is and then just anihilating them from around a corner or something

[Carlsberg]

The area of ram the game occupies should be protected, nothing should be allowed to modify it. that would negate any third party software. physical game file modification can already be protected.

[UnKn0wN]

You can stop aimbots from working if you add other hitboxes into entities for the Source engine I believe that's what SMAC does anyway.