To open the console:

1. Open settings.
   
2. Open Keyboard/Mouse
   
3. Toggle 'Allow Developer Console`
   
4. Press `

Most of the commands will require you to put this command in before to work:

Companion Cube: ent_create_portal_companion_cube

Cube: ent_create_portal_weighted_cube

Reflector Cube: ent_create_portal_reflector_cube

Old Cube: ent_create_portal_weighted_antique

Edgeless Safety Cube: ent_create_portal_weighted_sphere

Turret: npc_create npc_portal_turret_floor

Turret wife (Fat turret): prop_dynamic_create npcs/turret/turretwife

Frankenturret: ent_create prop_monster_box

Wheatley : ent_create npc_personality_core

UNUSED Wheatley GLaDOS: prop_dynamic_create npcs/glados/glados_wheatley

Wheatley GLaDOS: prop_dynamic_create npcs/glados/glados_wheatley_newbody

Wheatley GLaDOS boss: prop_dynamic_create npcs/glados/glados_wheatley_boss

GLaDOS: prop_dynamic_create npcs/glados/glados_animation

Water: ent_create_paint_bomb_erase

Repulsion Gel: ent_create_paint_bomb_jump

Propulsion Gel: ent_create_paint_bomb_speed

Conversion Gel: ent_create_paint_bomb_portal

Rocket: fire_rocket_projectile

Energy Pellet: fire_energy_ball

Door: give prop_testchamber_door

Laser: ent_create env_portal_laser (Always faces one way, use reflector cube)

Funnel Emitter (Does not include funnel): ent_create prop_tractor_beam

Camera Security Camera: ent_create npc_security_camera

Pedestal Button: ent_create prop_button

Error: ent_create prop_dynamic


Kill yourself: kill

Kill your partner: kill <partner name>

Fly and have no collision: Noclip

Portals Can Be Placed Anywhere: sv_portal_placement_never_fail (0=off, 1=on)

change_portalgun_linkage_id <A number> // Changes the set of portals your portal gun shoots. Having 4 or more visible portals produces some cool glitches at the risk of crashing your game.

cl_leveloverview 1/2/3 // Shows a top-down 2d version of the map you are on, following the camera. 1 Is least zoomed out, 3 is most zoomed out.

Close game: quit


Rotate objects: ent_rotate (rotates by 1° by default. the amount of numbers you add at the end is how many degrees it rotates.)

Change Portal Size: portals_resizeall (width) (height) // (default is 33 55)

Change Gravity: sv_gravity // Default = 600

Change Game Speed: host_timescale // Default = 1

Change Frankenturret Velocity: sv_monster_turret_velocity // Default = 100

Remove Objects (can crash game if not deleting certain objects): ent_remove

Shake // Shakes your screen.

Enter a certain map: Map <map name> // For when you are in the menu, names of maps here https://wiki.sourceruns.org/wiki/Portal_2_Maps

Change the map you are in: Changelevel <map name> // Names of maps here https://wiki.sourceruns.org/wiki/Portal_2_Maps

mat_wireframe 1 // Shows a wireframe of every model in the map.

mat_leafvis 1 // Shows the visleaf you are standing in with a blue box.

r_drawclipbrushes 1 / 2 // Draws clip brushes. 1 Draws the outline of them, 2 draws them fully solid.

vcollide_wireframe 1 // Draws all model hitboxes.

This section of the guide is for people who know how to use the console well. I'm giving this command it's own section because of it's complexity and vast potential.

This command can do a lot. If you have a basic understanding of the I/O system in Hammer, you should be able to master this fairly quickly. ent_fire is merely a crushed down version of Hammer's I/O system. If you know how to use the I/O system, you should be able to just learn how this works by playing with it in the console. But for all of you who don't use Hammer, I made this section for a reason.


ent_fire can send outputs to entities the same way entities can send outputs in Hammer. The format is as simple as:

ent_fire <target entity> <action> <value> <delay>

So, if you had a cube named cube1, and you wanted to change the colour of it to red 5 seconds after firing the command, you would enter:

ent_fire cube1 color "255 0 0" 5

Let me break down this quickly,

ent_fire - The command itself.
cube1 - The name of the target enity.
color - The action.
"255 0 0" - The colour to change it to.*
5 - The delay

* Colour in source uses the regular RGB system. The quote marks are only needed if the target entity or value has spaces in them. They are not needed if the value has no spaces.

The main problem here, is that if you don't have a good idea of the I/O system, it will be hard to geta grasp of this command. I'll come back to this section soon, but if you want to learn more about this powerful command in the meantime, I recommend learning Hammer.

I'm gonna be talking about binds for a while, so here you go!

Bind a command to a key: bind <key> <command> Example: bind n noclip
Have a space in the bind? Do this: bind <key> "<command>" Example: bind 1 "ent_fire !picker skin 1"

Binding is pressing a button to run the command. So you won't need to use bindtoggle to use showtriggers_toggle because that toggles when you enter it.

Have a bind like sv_cheats 1? Use this command:
bindtoggle <key> <command> Example: bindtoggle u sv_cheats
This will work like the last one with the spaces, though I can't think of any bindtoggle commands with spaces.

I'm not really updating this guide unless anybody wants anything specific. There are plenty of guides like this out there, this one is mainly personal reference for me.