ETS2 Console Commands and Developer Camera Guide

The ETS2 developer console is useful when you need diagnostics, route testing, screenshots, or controlled troubleshooting. It is also easy to misuse if you edit config files casually or run commands on the profile you care about.

Start with a backup. If you only want to repair a damaged truck or recover a stuck delivery, read ETS2 /fix Command and Service Recovery first. The console is a stronger tool, so treat it with more caution.

What the Console Is Good For

Use the console for controlled tasks:

1. Checking game state while troubleshooting.
2. Testing camera positions for screenshots.
3. Moving the developer camera for route observation.
4. Testing time or weather in a repeatable way.
5. Diagnosing whether a profile, mod, or route behaves differently after a change.

SCS documents many console commands on its modding wiki. That page also notes that its command list can be incomplete, so use it as a technical reference instead of a promise that every command is suitable for normal profiles: SCS Modding Wiki Console Commands.

Enable the Console Safely

Typical setup:

1. Close ETS2.
2. Open your ETS2 user folder.
3. Copy config.cfg somewhere safe.
4. Open config.cfg in a plain text editor.
5. Find uset g_developer and uset g_console.
6. Change both values to 1.
7. Save the file.
8. Launch ETS2 and test on a spare profile.

If you cannot find the file, use Where Are ETS2 Profiles, Saves, Mods, and Logs Stored? before editing anything.

Developer Camera Basics

The developer camera is useful for screenshots, route observation, and checking a scene without driving through it repeatedly. Keep the purpose narrow:

1. Use it to inspect a delivery area before practicing.
2. Use it to frame screenshots for a guide or bug report.
3. Use it to confirm whether a route issue is visual, traffic-related, or caused by mods.

Do not rely on developer-camera movement to finish normal career jobs. It can hide real driving problems such as bad route planning, poor braking distance, or wrong cargo choice.

Safer Command Habits

Follow these rules:

1. Run one command at a time.
2. Save before testing.
3. Avoid commands you do not understand.
4. Do not copy command blocks from old videos.
5. Keep a short note of every value you changed.
6. Revert config changes if the test is finished.

If a command changes time, position, traffic, or profile state, test it away from valuable cargo.

Common Mistakes

Mistake	Better Choice
Editing config while ETS2 is open	Close the game first
Testing on your main career	Use a spare profile
Running many commands at once	Change one variable at a time
Treating old command lists as current	Check a reliable technical source
Using console tools to mask mod crashes	Fix the mod stack and load order

When To Avoid the Console

Avoid console work when:

1. You have no backup.
2. You are mid-delivery with valuable cargo.
3. A modded profile already crashes.
4. You are trying to fix a TruckersMP or online service issue.
5. You only need a normal setting from the options menu.

For most players, in-game settings, profile backups, and Steam file verification are safer first steps. Use the console when you know what you are testing and how to undo it.