|
|
| (97 intermediate revisions by 52 users not shown) |
| Line 1: |
Line 1: |
| − | {{Cleanup|vg}}
| + | #REDIRECT [[Cheating]] |
| − | [[File:Wallhack.jpg|thumb|200px|right|Wallhacking on [[2Fort]]]] | |
| − | {{Quotation|'''The Administrator'''|You were always a disappointment...|sound=Announcer_am_lastmanforfeit02.wav}}
| |
| − | | |
| − | '''Hacking''' is the means by which players can give themselves an unfair advantage over others through running programs which alter the game code. [[Valve]] have a strict policy against hackers in place with their VAC system (Valve Anti-Cheat system) and are able to suspend suspected players from all VAC-supported servers, including those in ''Team Fortress 2''. Hacking and players of such can be easily avoided by playing exclusively on VAC supported servers, yet it is not uncommon for them to enter these servers. Furthermore, VAC experiences a delay in issuing bans towards hackers, meaning a suspect could continue hacking for a number of days.
| |
| − | | |
| − | It should be noted that certain actions or instanced may not constitute as hacking. For example, server administrators that use or abuse console commands are not hacking but merely abusing their position. Players that make use of various glitches or exploits are not hacking, as the issues are in the game and not accessed through the use of a program. Users that experience high latency are, also, not hacking. Most servers will have policies in place of such things, and players are encouraged to approach the server administrators or moderators if they have an issue.
| |
| − | | |
| − | ==Types of Hacking==
| |
| − | ===Aim (Aimbot)===
| |
| − | | |
| − | The program automatically locks onto player's hit boxes in the most viable position to the user. This can be identified by how the user's view will either shake wildly whilst still maintaining direct hits, or will appear to seamlessly follow other players regardless of speed or distance.
| |
| − | | |
| − | An alternative of the Aimbot is the Triggerbot. Here the user will appear to instantly fire once their crosshair passes over viable targets. This may be used in conjunction with the Aimbot. The program may also be used for [[Sticky Bomb]]s which can be identified if the suspected [[Demoman]] is in another area of the map.
| |
| − | | |
| − | ===Texture/Wall===
| |
| − |
| |
| − | This allows the user to see the silhouettes of players through walls and other surfaces possibly through modifying the transparency of map textures and the visibility of player textures. It will therefore appear that the user is aware of other players even when no indication of their presence was made. A phenomena known as 'pre-firing' can also occur where the user will fire at a location before he would otherwise do so. For example, a Demoman using a Wall Hack may shoot [[Grenade Launcher|grenades]] at a doorway prior to the player walking through them. This can be difficult to differentiate from normal player behaviour. Another example is, when the user 'traces' (follows) a non-visible player through a wall or surface with their crosshair before they are able to see them. Then once the player appears in their line of sight, the user is already aimed at them. This is often the case with Snipers using a Wall Hack.
| |
| − | | |
| − | ===Speed===
| |
| − | | |
| − | The user's movement speed is increased beyond the normal capacities of the class used. This can extend to increased weapon fire speed. This is often obvious to spot, as the user will be moving beyond the maximum movement speed available in the game. The user, however, may also set the speed to only slightly above the maximum for a class, making it more difficult to discover.
| |
| − | | |
| − | ===Invulnerability===
| |
| − | | |
| − | It will appear to others that the user will either never or take longer than usual to die if under constant fire. This will be more clear if there is no viable healing source nearby such as a Medic or Dispenser, or if they are hit by weapons that would otherwise kill them such as a [[Scout]] against a [[Crit]]ical Rocket.
| |
| − | | |
| − | ===Critical===
| |
| − | | |
| − | This is where the user will attack with a higher critical percentage than that of the 5% base. The player may therefore be firing unlimited Critical hits without an obvious means such as an [[ÜberCharge]].
| |
| − | | |
| − | ===Weapons===
| |
| − | | |
| − | This will allow the user to equip and use weapons that would otherwise not be available to that class, such a [[Scout]] with a [[Minigun]]. Note that this can be a plugin for a Randomizer server, in which case all players will have this effect.
| |
| − | | |
| − | ===Oneshot hacks===
| |
| − | | |
| − | Any hit that the user deals against another player will result in an instant kill, no matter what weapon was used. Easier to identify if low damage weapons such as a [[Pistol]] are used.
| |
| − | | |
| − | ===Unlimited ammo===
| |
| − | | |
| − | Often hand in hand with the Invulnerability, this will allow the user infinite amounts of ammo. This can be seen where the user will not attempt to reload even after firing the maximum number of shots of their weapon.
| |
| − | | |
| − | ===Spawn===
| |
| − | | |
| − | Here the user will manipulate the game in such a way as to generate props or items in a place that may block a route. This can be obvious for players experienced with the map who may notice things out of place. The type of items spawned can range from minor props to ragdolls and gates.
| |
| − | | |
| − | [[Category:Gameplay]]
| |
