STEAM GROUP
ExploitFinders ExploitEve
STEAM GROUP
ExploitFinders ExploitEve
1
IN-GAME
3
ONLINE
Founded
16 February, 2016
Language
English
Showing 1-2 of 2 entries
0
Finding exploits 101
Finding exploits can be tedious but I will give you some tips to make it more bearable, at first sight what it looks like a place where you can reach it ends up that there was an invisible wall. With the help of some console commands you won’t have this problem anymore.

First of all you need to create a server where you can test without being disturbed and freely, for that you have to press the cross in the corner of search for servers. Beware that there is a bug (yay! you found one :P) that if you put that the maximum players are 1 (this may seem logic because you are going to be alone) the server will lag. This is because the game tries to spawn bots but it can't so it pops some errors and makes the server super laggy.

Choose the map and put a password to the server (so that nobody enters), once you have created the server go and take a coffee because it will take more time than usual to load the map since it's not just doing that but also the server itself.

The first thing you have to do is type in the console
sv_cheats 1
now you can do anything you want without restrictions (everything you can do with the console of course). Now you want to stop that timer on top of your screen, for that type
mp_tournament 1
then write
mp_disable_respawn_times 1
if you die you won't have to wait.

Depending on what you want to do you may want to avoid dying for that there are some commands:
  • The command I most use is
    hurtme -100000
    the number must be negative because otherwise you will hurt yourself (and nobody would like you to get hurt). This command will give you a overheal of 100000, the bigger the number is the bigger the overheal it will be, note that if the number is too big you will die.

  • If you use the
    buddha
    command you will always survive with 1HP (unless you type "kill" of "explode" in the console). Before using this command you have to know that if you are at 1HP explosions won’t do anything and with anything I mean that you can't rocket jump or sentry jump (I think that mini sentries can't push you either).

  • The last command is
    god
    the name is self explanatory: you won't die, like a god.

Now instead of running around like a headless chicken trying to place teleports outside the map, you should use this two commands:

  1. vcollide_wireframe 1
    this command allows you to see the collision of props, if you don't see these blue lines in a prop it's very probable that it won't have collisions. There is another way to know if a prop has collisions, just shoot at it, if bullets hit the object: it has collisions. If not, it doesn't.
  2. r_drawclipbrushes 1 or r_drawclipbrushes 2
    This command will show you the map collisions, with this commands you will be able to see the invisible walls around the map. The differences between each other are that r_drawclipbrushes 1 will show you just the corners as lines (even though walls which is quite annoying), the other one instead shows the collisions as pink walls.

If you need bots just type "bot" in the console and one will join the game, remember that they will alternate the team they join which means that they will try to keep the teams balanced. With
mp_autoteambalance 0
you will disable the autobalance. With
bot_stop 1
, you will disable the AI of the bots.

It might be a good idea to put this last command: mp_restartgame 1 , this way you will restart the server and all the commands will be reloaded.

Instead of having to write this code every time you what to find bugs you could create a cfg and execute it, for that you will need notepad. Inside write the commands, the game executes the in order so the first one has to be sv_cheats 1 but the rest can be in any order. After you have finished save it as .cfg, you can put the name you want. For example: glitch.cfg . Make sure you don't save it as glitch.cfg.txt. Once you have done that paste it inside the folder C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf\cfg . When you are in-game just type exec NAMEOFTHEFILE.cfg , in our case it would be exec glitch.cfg . This way you have saved time.

This is all you need to find bugs, now go and break the game!!! (bugs were already there but whatever :) )
0
Rules
Showing 1-2 of 2 entries