Every CS2 player eventually hits the same wall: the in-game settings menu just does not expose enough control. You cannot set a custom FPS cap from a dropdown, you cannot write a warmup routine that spawns bots and unlimited ammo, and you cannot force a crosshair color that is not one of the six presets. All of that lives behind the developer console and a plain text file called autoexec.cfg. This tutorial walks through enabling the console, setting CS2 launch options in Steam, and building a working autoexec.cfg from scratch, with a complete file you can copy at the end.
Why CS2 Launch Options and Console Commands Still Matter in 2026
CS2 runs on the Source 2 engine, and Source 2 still exposes most of its tuning through console variables rather than menu toggles. Launch options change how the executable starts before the engine even loads a map: they can skip the intro video, force a specific refresh behavior, or preload the console itself. Console commands, by contrast, run after the game is live and control things like crosshair size, netgraph telemetry, and practice-server cheats. The two systems are separate but they work together, and most competitive players use both.
The reason this still matters years after CS2 replaced CS:GO is that Valve carried the underlying console architecture forward almost unchanged. Valve’s own Counter-Strike 2 console commands reference still documents the same variable naming scheme CS:GO players used for a decade, which is why old crosshair codes, binds, and netgraph settings mostly still work without modification. The CS2 FPS boost steps most players search for are really console commands and launch options in disguise, and a well-built autoexec.cfg is the difference between retyping ten commands every time you open the game and having them apply automatically the moment CS2 starts.
What has changed is discovery. CS:GO players leaned on a decade of forum threads and wiki edits; CS2 launched with a smaller, scattered body of documentation, so a lot of players are re-learning commands they used to take for granted. That is the gap this tutorial fills: a start-to-finish path from a stock CS2 install to a working, version-controlled config, using only settings that are documented and safe to run on official Valve servers.
Prerequisites: What You Need Before You Start
You do not need administrator rights or any third-party software for this setup. Here is what to have ready before Step 1:
- Steam client installed and signed in, with CS2 already downloaded (any current Steam client build works; Steam auto-updates itself).
- CS2 fully updated through Steam. Valve pushes CS2 updates automatically when you launch the game through Steam, so there is no separate version to track.
- Windows 10 or 11, or a Linux/SteamOS install running CS2 through Proton. File paths differ slightly, both are covered below.
- A plain text editor: Notepad on Windows, or something like Notepad++ or VS Code if you want syntax highlighting. Do not use a word processor like Word, since it can insert hidden formatting characters.
- About 30-40 minutes for the full setup, plus a few minutes each time you want to tweak the file afterward.
- No Steam Guard changes or special permissions required; everything here happens inside a folder you already have full read/write access to.
One more thing worth confirming up front: this guide only touches client-side settings. It will not get you VAC banned, and none of the commands here require sv_cheats on a live matchmaking server, since cheat-protected commands only work on local or LAN servers you control.
It also helps to know where CS2 stores its own release notes before you start changing settings. Valve publishes patch notes and any console-relevant changes through the official Counter-Strike news feed, and if a specific console variable in this guide ever stops behaving as described, that feed (along with the developer console commands wiki) is the fastest way to confirm whether Valve changed it in a recent update.
Step 1: Enable the Developer Console in CS2 Settings
The console is disabled in the UI by default on a fresh CS2 install. Open CS2, go to Settings, then the Game tab, and set Enable Developer Console to Yes. This single toggle is what unlocks the console keybind; skipping it is the single most common reason people think console commands “do not work” in CS2.
Step 2: Open the Console and Run a Test Command
With the console enabled, press the tilde key (~) to open it. On some non-US keyboard layouts the console key can be in a different physical position, in which case you can rebind it under Settings > Keyboard/Mouse > Console Key. Type a harmless command to confirm it is working:
fps_maxPressing Enter with no value after a command name prints its current setting rather than changing anything. You should see console output similar to this:
"fps_max" = "0"
- Frame rate limiter.If you see that kind of response, the console is live and ready for the rest of this walkthrough.
Step 3: Set Your Steam Launch Options
Launch options are set outside the game, in Steam. Right-click Counter-Strike 2 in your Steam library, choose Properties, stay on the General tab, and find the Launch Options field near the bottom. This box accepts a space-separated string of flags that get passed to the CS2 executable every time Steam starts it.
A Practical CS2 Launch Options String
A common baseline string combines a handful of flags that skip startup friction and force your autoexec to run:
-novid -nojoy -forcenovsync +fps_max 0 +exec autoexec.cfgHere is what each flag does: -novid skips the Valve intro video on launch. -nojoy disables joystick/controller polling, which some players include to shave a small amount of input overhead if they never use a controller. -forcenovsync disables vertical sync at the driver level rather than leaving it to the in-game setting. +fps_max 0 removes the frame rate cap entirely, letting your GPU render as many frames as it can (swap the 0 for a number like 240 or 400 if you want an actual cap instead). +exec autoexec.cfg tells CS2 to run your autoexec file the moment it finishes loading, which is what makes every command in the rest of this guide apply automatically instead of manually.
One flag people frequently paste in from old CS:GO guides is -tickrate 128. It is harmless to include, but it only affects local offline servers you host yourself; it has no effect on Valve matchmaking or Premier servers, since server tickrate there is fixed on Valve’s side.
Steam also documents its own general launch-options syntax outside of any specific game, and it is worth skimming once, since the same dash-and-plus conventions apply across most Source and Source 2 titles listed on the Counter-Strike 2 store page. Steam’s launch options help article covers how the client parses this field and what happens if you enter a flag it does not recognize (Steam passes it through to the game silently rather than rejecting it, so a typo in a launch option will not throw an error, it will just do nothing).
Step 4: Locate or Create Your autoexec.cfg File
CS2 still reads its config folder from the legacy Counter-Strike Global Offensive path. On Windows, the default location is:
C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\If you installed Steam or your game library on a different drive, adjust the drive letter and path accordingly, right-click CS2 in your Steam library and choose Manage > Browse Local Files to jump straight there. On Linux/SteamOS running CS2 through Proton, the same folder sits under your compatdata prefix, typically something like ~/.steam/steam/steamapps/compatdata/730/pfx/drive_c/Program Files (x86)/Steam/steamapps/common/Counter-Strike Global Offensive/game/csgo/cfg/.
Inside that cfg folder, create a new text file, name it exactly autoexec.cfg, and make sure Windows is not silently appending .txt to the end. In File Explorer, turn on View > File name extensions so you can confirm the filename does not read autoexec.cfg.txt, since that single hidden extension is one of the most common reasons an autoexec silently fails to load.
How CS2 Loads Configs: The Order That Decides What Wins
Before writing more commands, it helps to know that CS2 is reading from more than one file, and the order matters. If two files set the same command to different values, whichever one runs last overwrites the earlier value. Understanding this order stops a lot of “why did my setting reset” confusion later.
| File | When It Runs | Typical Use |
|---|---|---|
| config.cfg | Automatically, on every launch, before autoexec.cfg | Written by CS2 itself from your in-game menu changes; not meant to be hand-edited |
| autoexec.cfg | On launch, only if +exec autoexec.cfg is in your launch options | Your own persistent settings: crosshair, netgraph, binds |
| <mapname>.cfg (e.g. de_mirage.cfg) | Whenever that specific map loads, after autoexec.cfg | Map-specific overrides, like a different radar zoom on a particular map |
Because autoexec.cfg runs after config.cfg, anything you set in autoexec.cfg will always win over a conflicting value CS2 wrote into config.cfg from the settings menu. That is exactly why autoexec.cfg is the right place for anything you want to survive a settings-menu change or a fresh install: it is not touched by the game’s own auto-save behavior, only by you.
Step 5: Write Your Crosshair and HUD Commands
Open autoexec.cfg in your text editor and add one command per line, exactly as you would type them into the console. A basic crosshair block looks like this:
cl_crosshairstyle 4
cl_crosshairsize 2
cl_crosshairthickness 1
cl_crosshairgap -1
cl_crosshaircolor 1
cl_crosshairdot 0
cl_crosshair_drawoutline 1Each line is a separate command, and there is no semicolon or comma needed between them; the game reads the file one line at a time. If you already have a crosshair code shared by a pro player or teammate, you can paste it directly into the console once to preview it live, then copy the individual cl_crosshair commands into autoexec.cfg once you are happy with how it looks.
Step 6: Add Netgraph and Performance Telemetry Commands
Netgraph gives you a live readout of ping, choke, and loss in the corner of the screen, which is useful for diagnosing whether a bad round was a connection issue or a mechanical one. Add:
net_graph 1
net_graphpos 2
cl_showfps 1net_graph 1 turns on the network graph overlay, net_graphpos 2 centers it at the bottom of the screen instead of the far corner, and cl_showfps 1 adds a simple frame rate counter if you want a lighter-weight alternative to the full netgraph. If your goal is squeezing out extra frames rather than just monitoring them, the dedicated CS2 FPS boost walkthrough covers render-side settings this guide does not.
Step 7: Build a Warmup and Practice Config
This is where console commands go beyond cosmetics. On a local offline server (never on live matchmaking) you can enable cheat-protected commands to build a practice routine: unlimited ammo, no reload delay, and full grenade inventory. Start a local map from the main menu’s practice mode, open the console, and run:
sv_cheats 1
sv_infinite_ammo 1
mp_free_armor 1
mp_roundtime 60
mp_warmup_pausetimer 1
bot_stop 1
bot_kicksv_cheats 1 unlocks the cheat-protected command set on that local server only. sv_infinite_ammo 1 removes reload limits so you can drill spray patterns without stopping. mp_free_armor 1 spawns you with full armor and a helmet automatically. mp_roundtime 60 stretches round length so you are not rushed. mp_warmup_pausetimer 1 freezes the warmup countdown so it never forces a restart mid-drill, and bot_kick clears any bots from the server if you added them earlier for aim practice. You would not put sv_cheats in your main autoexec.cfg, since it does nothing (and Valve blocks it) on official servers; instead, save these lines as a second file, something like practice.cfg, and load it manually with exec practice.cfg only when you are on a local server.
Adding Bots for Target Practice
If you want moving targets rather than a static spray pattern, add bots to the same local server before you start drilling:
bot_add_ct
bot_add_t
bot_difficulty 2
bot_stop 0bot_add_ct and bot_add_t spawn one bot on each side, bot_difficulty 2 sets them to a moderate skill level (0 is easiest, 3 is hardest), and bot_stop 0 lets them actually move and shoot back instead of standing still. Run bot_kick from the earlier block whenever you want to clear them out and reset the server for a clean warmup.
Step 8: Load Your Config Automatically and Verify It Worked
Because your Steam launch options already include +exec autoexec.cfg from Step 3, the file loads every time CS2 starts, with no manual action needed. To confirm it actually ran, open the console right after the main menu loads and check the value of a setting you configured, for example:
net_graphIf autoexec.cfg loaded correctly, the console should echo back "net_graph" = "1" instead of the default 0. You can also force a manual reload at any time without restarting the game by typing exec autoexec directly into the console (the .cfg extension is optional when using the exec command).
Step 9: Bind Keys for Fast In-Game Adjustments
Binds let you toggle a command with a single keypress instead of opening the console mid-round. Add these near the bottom of autoexec.cfg:
bind "F5" "toggle net_graph 0 1"
bind "F6" "toggle cl_crosshairsize 2 3"
bind "KP_ENTER" "buy vest;buy vesthelm"The first two lines flip a setting between two values every time you press the key, which is handy for quickly comparing crosshair sizes without retyping numbers. The third line is a buy bind, chaining two buy commands with a semicolon so a single keypress purchases armor or a helmet-and-vest combo depending on what you can afford that round.
Step 10: Protect Your Config From Being Overwritten
CS2 updates occasionally reset config.cfg (the file Valve writes automatically from your in-game menu changes), but they do not touch autoexec.cfg since it is a file you created and the game only reads from it, never writes to it. Still, it is worth keeping a backup copy of autoexec.cfg outside the Steam folder entirely, for example in a cloud-synced folder, since a full CS2 reinstall or Steam library move will wipe the cfg directory along with everything else in it.
The Complete Working autoexec.cfg
Here is every command from the steps above combined into one file you can copy directly into autoexec.cfg. Save it, confirm your Steam launch options include +exec autoexec.cfg, and restart CS2 once to apply everything at once.
// ---- Crosshair ----
cl_crosshairstyle 4
cl_crosshairsize 2
cl_crosshairthickness 1
cl_crosshairgap -1
cl_crosshaircolor 1
cl_crosshairdot 0
cl_crosshair_drawoutline 1
// ---- Netgraph / performance ----
net_graph 1
net_graphpos 2
cl_showfps 1
// ---- Binds ----
bind "F5" "toggle net_graph 0 1"
bind "F6" "toggle cl_crosshairsize 2 3"
bind "KP_ENTER" "buy vest;buy vesthelm"
// ---- Confirm the file loaded ----
echo "autoexec.cfg loaded"That last echo line is a small trick worth keeping in every config you write: it prints a plain confirmation message to the console the instant the file finishes executing, so you know at a glance whether it ran without having to check individual variable values.
Putting It All Together: What a First Launch Looks Like
With every step above finished, here is what actually happens the next time you start CS2, in order. Steam reads your launch options string and starts the executable with -novid, -nojoy, and -forcenovsync already applied, so the client skips straight past the intro video. The engine finishes loading, and because +exec autoexec.cfg is part of that same string, it immediately reads your cfg file line by line: crosshair variables first, then netgraph and FPS display settings, then your binds, then the echo line at the end.
If you open the console at the main menu at this point and everything loaded correctly, you should see the confirmation text from the echo command near the bottom of the console history:
autoexec.cfg loadedFrom there, joining a match immediately shows your custom crosshair and, if you enabled it, the netgraph overlay in the corner you set with net_graphpos. Pressing F5 or F6 (or whatever keys you chose in Step 9) toggles those settings live without needing to reopen the console. On a local server, F9 or F10 (if you built the aliases from the advanced tips and pre-match routine sections) run your full practice or warmup chain in one press instead of the seven or eight individual commands they represent.
That is the entire point of moving from typing commands manually to a maintained autoexec.cfg: every session starts from the exact same known state, and the only thing left to do manually is play.
CS2 Launch Options and Console Commands Quick-Reference Table
Keep this table handy while you customize your own config beyond the defaults used above.
| Flag or Command | Type | What It Does |
|---|---|---|
| -novid | Launch option | Skips the Valve intro video on startup |
| -nojoy | Launch option | Disables joystick/controller polling |
| -forcenovsync | Launch option | Forces vsync off at the driver level |
| -console | Launch option | Opens the developer console automatically on boot |
| +fps_max 0 | Console command | Removes the frame rate cap entirely |
| +exec autoexec.cfg | Launch option | Runs autoexec.cfg the moment the game finishes loading |
| net_graph 1 | Console command | Shows the live ping/choke/loss network overlay |
| sv_cheats 1 | Console command (local only) | Unlocks cheat-protected commands on a server you control |
Adjusting the Setup for Different Hardware
The baseline launch options and autoexec.cfg above work on almost any setup, but a few tweaks are worth making depending on your monitor and system.
High Refresh-Rate Monitors
If you play on a 144Hz, 165Hz, or 240Hz monitor, an uncapped fps_max 0 can occasionally produce more tearing than a fixed cap that matches or slightly exceeds your refresh rate. A common adjustment is capping a few frames above your panel’s rating, for example fps_max 246 on a 240Hz screen, which keeps the render pipeline consistently fed without wasting GPU cycles on frames the monitor cannot display anyway.
Windowed and Borderless Play
If you alt-tab often to check Discord or a second monitor, add -windowed -noborder to your launch options string. This runs CS2 in a borderless window sized to your desktop resolution, which switches away from the game almost instantly compared with true fullscreen exclusive mode, at a small and usually unnoticeable cost to input latency.
Laptops and Steam Deck
On a laptop with both integrated and dedicated graphics, make sure CS2 is set to run on the dedicated GPU through your Windows graphics settings or your GPU vendor’s control panel; launch options cannot force this themselves. On Steam Deck or another SteamOS handheld, the launch options field works identically to desktop Steam, but remember the cfg folder path runs through the Proton compatdata prefix described in Step 4, not a native Linux path.
Common Pitfalls When Setting Up CS2 Console Commands
- Saving the file as autoexec.cfg.txt. Windows hides known file extensions by default, so a file named “autoexec.cfg” in Notepad’s save dialog can actually save as “autoexec.cfg.txt” without any visible warning. Turn on file extensions in File Explorer to catch this.
- Forgetting +exec autoexec.cfg in launch options. Creating the file is not enough by itself; without that flag (or a manual exec command every session), CS2 never reads it.
- Putting sv_cheats commands in the main autoexec. These lines are ignored on matchmaking and Premier servers and will do nothing there, so keep them in a separate practice config you load manually on local servers only.
- Mixing up console commands and launch options syntax. Launch options use a leading dash or plus sign (-novid, +fps_max 0); console commands typed directly into the in-game console do not use that prefix at all.
- Editing the file while CS2 is running. Changes you save to autoexec.cfg will not apply until you either restart the game or manually run exec autoexec in the console.
- Assuming -tickrate 128 changes matchmaking behavior. It only affects servers you host locally; live Valve servers control their own tickrate regardless of your launch options.
Troubleshooting Console and Launch Option Issues
Even a correctly written config can run into one of these issues. Work through them in order before assuming something is broken at a deeper level, since most of the time the cause is one of the same handful of small mistakes rather than a genuine CS2 bug.
- The tilde key does nothing. Confirm Enable Developer Console is set to Yes under Settings > Game; the keybind is inactive until that toggle is on.
- Console opens but commands print “unknown command.” Check for typos, and remember cheat-protected commands like sv_cheats-gated ones will not exist as usable commands unless sv_cheats 1 is already active on that server.
- autoexec.cfg does not seem to load at all. Re-check the file location, the exact filename (no .txt), and that +exec autoexec.cfg is actually saved in the Launch Options field in Steam, not just typed and left unsaved.
- Launch options field appears empty after you set it. Steam sometimes needs the Properties window fully closed (not just clicked away from) before it commits changes; reopen it to confirm your string saved.
- Crosshair settings revert after a match. This usually means a duplicate, conflicting cl_crosshair line exists later in the same file, since CS2 applies config lines top to bottom and the last one wins.
- FPS cap does not seem to apply. Confirm no in-game setting under Video > Advanced is also setting an FPS limit, since a menu-set value can conflict with the one from your launch options.
- Netgraph shows but numbers look frozen. This is typically a local network hiccup rather than a config problem; check your connection separately before touching commands again.
- Binds do not fire in-game. Make sure the key is not already bound to something else earlier in the file or in the in-game keybind menu, since a later bind in the same file overrides an earlier one for the same key.
- Config works on Windows but not after switching to Linux/SteamOS. Double check the Proton compatdata path, since it is a different folder from the native Windows path and CS2 will not find a file left in the wrong one.
- A reinstall or Steam “verify integrity of game files” wiped your config. Verifying game files checks and restores the game’s own installed files, and it can regenerate a fresh cfg folder in the process, which is exactly why the backup habit from the advanced tips section matters. Restore autoexec.cfg from your saved copy and reconfirm the +exec flag is still set in launch options, since a verify pass does not touch Steam’s launch options field, but a full uninstall/reinstall does clear it.
Advanced Tips: Aliases, Per-Map Configs, and Safer Backups
Once the base setup above is working, a few extra techniques make a config genuinely easier to maintain long-term.
Command Aliases
The alias command lets you bundle several commands under one custom name, which keeps binds short and readable:
alias "practicemode" "sv_cheats 1;sv_infinite_ammo 1;mp_free_armor 1"
bind "F9" "practicemode"Now pressing F9 on a local server runs all three commands from Step 7 at once instead of typing each one separately.
Per-Map Configs
CS2 will auto-execute a config file that matches a map’s name, if one exists in the cfg folder. Creating a file named exactly de_mirage.cfg, for example, lets you load map-specific crosshair or radar settings automatically whenever that map loads, without touching your main autoexec.cfg.
Versioned Backups
Keep dated copies of autoexec.cfg (autoexec_2026-08.cfg, for instance) in a synced folder outside the Steam directory. If a future patch or a game repair through Steam wipes the cfg folder, you can restore your exact setup by copying the latest backup back in and renaming it, rather than rebuilding every command from memory.
Rolling Back If Something Goes Wrong
If a change leaves your settings in a state you cannot untangle, the safest reset is to close CS2, rename autoexec.cfg to something like autoexec_old.cfg so it stops loading, and restart the game. CS2 will fall back to whatever config.cfg already has stored plus its own defaults for anything neither file sets, giving you a clean baseline to rebuild from using the steps above.
Building a Repeatable Pre-Match Routine
Once the individual pieces from Steps 1 through 9 are in place, the last useful step is chaining them into a single routine you run before every session instead of thinking about each command separately. This is where the alias command from the advanced tips section earns its keep: instead of remembering seven separate steps, you collapse them into one keypress.
alias "warmup_routine" "bot_kick;bot_add_t;bot_add_ct;bot_difficulty 2;bot_stop 0;mp_roundtime 60;mp_warmup_pausetimer 1"
bind "F10" "warmup_routine"Pressing F10 on a local server now clears any leftover bots, adds a fresh pair, sets their difficulty, and extends the round timer in one action. Pair that with the crosshair and netgraph block from your main autoexec.cfg, which is already loading automatically thanks to +exec autoexec.cfg in your launch options, and a full pre-match warmup goes from a multi-minute manual chore to something that takes a few seconds before you queue.
It is worth testing this routine once on a local server before relying on it, since a typo inside an alias definition (a missing semicolon, a misspelled command) will silently fail on just the broken segment rather than throwing an error for the whole alias. Run each command individually first if the alias does not behave the way you expect, then reassemble it once every piece is confirmed working on its own.
Comparing Your Setup Against Other CS2 Progression Tools
A tuned console setup pairs naturally with the ranking and matchmaking systems CS2 uses to sort players. If you are also trying to understand where your account currently sits, the breakdown of CS2 Premier versus Competitive rank explains how the two ranked modes score performance differently, and the comparison of CS2 ranks against ESEA and FACEIT covers how third-party matchmaking platforms interpret skill outside Valve’s own system. If you specifically use Premier mode, the piece on Premier rank versus Faceit level maps the two scales against each other directly.
None of those systems read your autoexec.cfg directly, matchmaking rank is determined by in-match performance, not client settings, but a consistent, distraction-free HUD and a warmup routine you actually run before queuing both remove small, avoidable variables from a session. If you eventually want to host your own server rather than just tuning the client, the CS2 dedicated server setup walks through standing up a private box where sv_cheats and practice configs apply without any of the local-server restrictions covered in Step 7 of this guide.
Frequently Asked Questions
Do CS2 launch options slow down my startup time?
No, the flags covered in this guide (-novid, -nojoy, -forcenovsync) either skip a step or disable a check, so if anything they shave a small amount of time off launch rather than adding to it.
Can I use the same autoexec.cfg on multiple computers?
Yes. Since autoexec.cfg is just a plain text file, copying it into the cfg folder of any CS2 install (Windows or Linux/Proton, matching the correct path) reproduces the exact same settings.
Will sv_cheats commands get me VAC banned?
No, as long as they are only run on a local or private server you control. sv_cheats simply does not function on Valve matchmaking or Premier servers, so there is no way to activate it there in the first place.
Why does the game say “unknown command” for something I typed correctly?
This usually means the command is cheat-protected and sv_cheats is not currently set to 1 on that server, or there is a small typo. Console commands are case-insensitive but must be spelled exactly right otherwise.
Does +fps_max 0 cause screen tearing?
It can, since removing the frame cap combined with vsync disabled (-forcenovsync) means frames are not synced to your monitor’s refresh cycle. If you notice tearing, set fps_max to a fixed number close to your monitor’s refresh rate instead of 0.
Can I open the console with a controller instead of a keyboard?
No, the console requires a keyboard bind. If you play with a controller plugged in alongside a keyboard, the console keybind still works normally since it is a separate input from controller navigation.
Do I need to redo this setup after every CS2 update?
No. Updates can occasionally reset config.cfg, the file CS2 writes from in-game menu changes, but they do not delete or overwrite autoexec.cfg, since that file is never written to by the game itself.
What is the difference between a launch option and a console command?
A launch option is set in Steam and applies before or during startup, using a dash or plus-sign prefix. A console command is typed inside the running game (or placed in a .cfg file) and can be changed at any point during a session without restarting CS2.
Can autoexec.cfg break my game if I make a mistake?
Not in a way that requires a reinstall. Worst case, a bad line is skipped or an unwanted setting applies, both of which are fixed by editing the file again or renaming it temporarily, as covered in the rollback tip in the advanced section above.
Do I need a different autoexec.cfg for Premier mode versus Competitive?
No. autoexec.cfg applies at the client level regardless of which mode you queue into, since crosshair, netgraph, and binds are personal settings rather than mode-specific ones. The differences between Premier and Competitive come from how each mode scores and matches you, not from anything in your local config files.
