My SRB2 is glitching even without any mods open

[Greg]

When I open SRB2 it says "command XXX does not exist", this happened right after I downloaded SRB2 Smash, and since then it always gives me these same command errors.
I'm worried about him
afraid of ruining my modding experience

Post automatically merged: Mar 21, 2026

This happens sometimes, at least it happened once today, actually it only happened once, but even then, it was without any mods open. I clicked on "srb2win.exe" and a bunch of non-existent commands appeared. Will this happen again?

Post automatically merged: Mar 21, 2026

I think it's best to leave this alone for a while. Maybe it's just a problem with the mod, or with SRB2? I don't know, I think it's best to just forget about it.

 

[nikoberry]

this is normal, it's just console variables either made by Lua (or from custom builds) bearing the CV_SAVE (basically "write this to config.cfg") flag.
SRB2 redoes the config file from scratch every time it "saves" it (the config), so you can actually ignore this entirely.

If you do want to keep them, you could probably make a new file and paste the cvar lines that gave the notice to then later `exec <filename>.cfg` it, or use `saveconfig` (you can use `loadconfig` later, note that after loading, closing will NOT save to a different file).

you can also just give the `-config` parameter to the executable and give a full path to the config file you wanna use (it'll save to this).

 

[Greg]

this is normal, it's just console variables either made by Lua (or from custom builds) bearing the CV_SAVE (basically "write this to config.cfg") flag.
SRB2 redoes the config file from scratch every time it "saves" it (the config), so you can actually ignore this entirely.

If you do want to keep them, you could probably make a new file and paste the cvar lines that gave the notice to then later `exec <filename>.cfg` it, or use `saveconfig` (you can use `loadconfig` later, note that after loading, closing will NOT save to a different file).

you can also just give the `-config` parameter to the executable and give a full path to the config file you wanna use (it'll save to this).

I found this really interesting, so I could create a software (a copy of SRB2) with a configuration file, for example, srb2.pk3, with a save option like "change the name of sonic to onic," and it would always work?

 

[DylanDude]

I found this really interesting, so I could create a software (a copy of SRB2) with a configuration file, for example, srb2.pk3, with a save option like "change the name of sonic to onic," and it would always work?

No, because Sonic's name is controlled via a resource file, not the player's options file. The game would still boot though, it would just print a message to the console telling you that the "command" didn't work lol

 

[Greg]

No, because Sonic's name is controlled via a resource file, not the player's options file. The game would still boot though, it would just print a message to the console telling you that the "command" didn't work lol

I think it's best to create a separate topic just for that (in this case, some questions and some things I wanted to do).

 

[nikoberry]

I found this really interesting, so I could create a software (a copy of SRB2) with a configuration file, for example, srb2.pk3, with a save option like "change the name of sonic to onic," and it would always work?

the config file isn't code, it's just console variables with their string value as they get executed line by line on startup, for instance:

// SRB2 configuration file.
execversion "56"
modfilter "None"
musicpref "Digital"
midimusic "Off"
digimusic "Off"
sounds "On"
playmusicifunfocused "Yes"
playsoundsifunfocused "Yes"
1upsound "Sound"
resetmusicbyheader "Yes"
resetmusic "On"
surround "Off"
precachesound "Off"
stereoreverse "Off"
fpscap "Unlimited"
maxportals "2"
translucenthud "9"
earthquake "Off"

(cut short for brevity)

so for instance earthquake gets set to off, 1upsound to Sound, etc...

think of it as the game setting stuff you wouldnt want to manually set again every time you started the game (say, your fov, controls, renderer, etc - even though you could do it with an autoexec.cfg, that would still be annoying to manually change)
the whole file basically gets "inserted" into the console, and the variables are set to the values within the quotes (if they exist (else the unknown command notice) or if the value does ("(x) is not a possible value for (y)")).

 

[Greg]

the config file isn't code, it's just console variables with their string value as they get executed line by line on startup, for instance:

// SRB2 configuration file.
execversion "56"
modfilter "None"
musicpref "Digital"
midimusic "Off"
digimusic "Off"
sounds "On"
playmusicifunfocused "Yes"
playsoundsifunfocused "Yes"
1upsound "Sound"
resetmusicbyheader "Yes"
resetmusic "On"
surround "Off"
precachesound "Off"
stereoreverse "Off"
fpscap "Unlimited"
maxportals "2"
translucenthud "9"
earthquake "Off"

(cut short for brevity)

so for instance earthquake gets set to off, 1upsound to Sound, etc...

think of it as the game setting stuff you wouldnt want to manually set again every time you started the game (say, your fov, controls, renderer, etc - even though you could do it with an autoexec.cfg, that would still be annoying to manually change)
the whole file basically gets "inserted" into the console, and the variables are set to the values within the quotes (if they exist (else the unknown command notice) or if the value does ("(x) is not a possible value for (y)")).

So, in order to do what I want in SRB2, I have to mess with its code (the game's code) and then change things in the game. Like, I go into the game's code, change anything, let's say, for example, hmm, like changing the DSJUMP location to DSSPIN. I think I'll really have to open another thread.

Post automatically merged: Mar 22, 2026

the topic for this conversation