WoW Forever Console Commands: Max Camera Distance, Nameplates and Useful CVars

Some of the most useful settings in World of Warcraft never made it into the Options window. You change them with console variables (CVars) typed into chat after /console. This guide lists the WoW Forever console commands players use most, starting with max camera distance, and gives each one a plain explanation, a safe value and the command to undo it. It also flags the commands that are reported not to work in Forever, and the values that come only from single player tests. Checked on 8 November 2026 for WoW Forever 1.60.1. Forever is built on the modern client, so retail CVar names apply, but Blizzard can change limits in any patch.

Short answer

• Type /console cameraDistanceMaxZoomFactor 2.6 for a longer camera; one beta tester reached 3.34, but higher values are not confirmed.
• Check any value with /dump GetCVar("name") before you change it, and write the old number down.
• Undo one change with /console cvar_default name; undo every CVar with /console cvar_default.
• /console volumeFog 0 no longer removes fog in Forever; Blizzard removed that behaviour during the beta.
• Settings sync to Blizzard's servers, so deleting the WTF folder does not always bring the defaults back.

How console commands work

1. Open chat and type /console, a space, the CVar name, a space and the value, for example /console scriptErrors 1.
2. Press Enter. Most CVars apply at once; graphics ones sometimes need a moment or a restart.
3. Read the current value with /dump GetCVar("cameraDistanceMaxZoomFactor").
4. Some CVars are protected: they cannot be changed in combat, and a few only accept the /run SetCVar("name", value) form. If /console seems to do nothing, try that form out of combat.

Values are saved in _forever_\WTF\Config.wtf and in per-account and per-character cache files under _forever_\WTF\Account. Edit those only with the game closed, because the client rewrites them on logout. Since many settings are also stored server-side, a fresh WTF folder is not a guaranteed reset.

Max camera distance

cameraDistanceMaxZoomFactor multiplies the furthest the camera can zoom out. On the modern client the default is 1.9 and the documented range is 1 to 2.6, which works out at roughly 39 yards, and the Warcraft Wiki says the camera stops at 39 yards even if the product is higher. Classic clients allowed up to 4.

Value	What you get	Status in Forever
1.9	Default zoom	Default on the modern client
2.6	Documented modern maximum	Safe starting point
3.34	Further zoom, if the 39-yard stop does not apply	Reported by one player in the beta forums, not confirmed
4.0	Classic-style maximum	Posted by players; may be capped lower

1. Type /console cameraDistanceMaxZoomFactor 2.6.
2. Scroll the mouse wheel all the way out.
3. If you want to test more, try 3.34, then check with /dump GetCVar("cameraDistanceMaxZoomFactor"); if the camera stops at the same spot, the client capped it.
4. Reset with /console cvar_default cameraDistanceMaxZoomFactor.

The value should stay saved between sessions. If it reverts after a relog, put the command into a macro and press it once per login; the macros guide shows how.

Nameplates, combat and interface CVars

CVar	What it does	Suggested value	Notes
nameplateMaxDistance	How far away enemy nameplates appear	41	One beta player reported a default of 20; the default and maximum are not documented for Forever
nameplateMaxVerticalDistance	Hides nameplates of units far above or below you	Leave default	Added in the Forever beta; 0 turns the check off
SpellQueueWindow	How early you can queue the next spell, in milliseconds	Default, or no lower than about 200 plus your ping	Default given as 400; forum posts suggest 120 to 150
scriptErrors	Shows Lua error pop-ups from addons	1 while testing, 0 after	Useful when hunting a broken addon

Advice on SpellQueueWindow differs: forum posts go as low as 120, while modern-client guides warn that a window shorter than your ping plus about 200 ms leaves gaps between casts. Nameplate range and visibility also live partly in the Options window, covered in interface and keybind setup.

Graphics CVars and what no longer works

These go beyond the graphics menu. Lower them for FPS, raise them for screenshots.

CVar	What it does	Values players use
groundEffectDensity	Grass and small plants	0 for FPS, up to 256 for detail
groundEffectDist	How far grass is drawn	40 to 140 for FPS, 500 for detail
weatherDensity	Rain and snow particles	0 off, 3 full
ResampleAlwaysSharpen	Extra sharpening, helpful with a lower render scale	1 on, 0 off
maxFPS / maxFPSBk	Frame cap in the foreground and background	Monitor refresh rate / 30

Blizzard's beta development notes of 24 September 2026 removed "a setting that could disable fog in an unintended manner". Since then players report that /console volumeFog 0 does nothing or only works for a moment. Treat it as gone and use the graphics options instead. For the full menu, read the best graphics settings for FPS.

Common problems

Problem	What helps
Camera stops zooming at the same point	You hit the client cap; go back to 2.6
Command typed, nothing changed	Check the spelling with /dump GetCVar("name"); try /run SetCVar("name", value) out of combat
Settings back to old values after reinstall	Server sync restored them; reset with /console cvar_default name
Fog still heavy	volumeFog was removed; lower view distance or adjust brightness instead
Game looks wrong after many tweaks	Run /console cvar_default to reset every CVar, then redo the few you want
Error pop-ups everywhere	Set /console scriptErrors 0 once you have found the faulty addon

Tips

• Change one CVar at a time, so you know which one helped or hurt.
• Keep a text file with every command you use and its old value.
• Use the in-game options first, since they survive patches better than hidden CVars.
• Do not copy long "ultra" CVar lists from videos without checking what each line does.
• Recheck your camera and nameplate values after each major patch, because limits can change.
• Avoid "FPS booster" tools that rewrite config files outside the game.

ForeverBot and this setup

Camera and nameplate CVars do not interfere with ForeverBot, and a longer camera simply helps you see the route. Leave interface scaling and other UI CVars at sensible values so the bot window and game text stay readable. The ForeverBot first-run setup covers the rest. Be honest with yourself about the risk: automation breaks Blizzard's rules and Blizzard bans accounts for it.

FAQ

What is the max camera distance command in WoW Forever?

Type /console cameraDistanceMaxZoomFactor 2.6. That is the documented maximum on the modern client the game runs on. One player in the beta forums reported 3.34 working, but this is not confirmed, so test it and check with /dump GetCVar("cameraDistanceMaxZoomFactor"). Reset with /console cvar_default cameraDistanceMaxZoomFactor.

Does volumeFog 0 work in WoW Forever?

Not reliably. Blizzard's beta notes from 24 September 2026 removed a setting that could disable fog in an unintended way, and players since report that the command does nothing or reverts at once. Use the graphics options, lower view distance or adjust brightness instead.

How do I reset all console commands to default?

Type /console cvar_default to reset every CVar, or add a name to reset only one. Deleting the WTF folder is not enough on its own, because character and account settings are synced to Blizzard's servers by default and come back on the next login.

Can console commands get me banned?

We found no reports of bans for changing CVars with /console; they are part of the client and many players use them. The risk comes from third-party programs that edit game files or memory, which are against the rules. Stick to commands typed in chat.