The descriptions for e. g. shaderexp and buildcubemaps show up as -- when using /listCmds, rather than evaluate a q3shader expression (RB_EvalExpression) and generate cube probes for reflection mapping, is this supposed to happen?

The descriptions for e. g. shaderexp and buildcubemaps show up as -- when using /listCmds, rather than evaluate a q3shader expression (RB_EvalExpression) and generate cube probes for reflection mapping, is this supposed to happen?

Can't reproduce. Are you sure you're building and running the right code?

I'm certain of that.

Apparently, it works properly with auto-completion, but not with listCmds:
Regular usage:

 ]/listcmds gfx
 0 commands
 ]/listcmds shader
 0 commands
 ]/listcmds build
   build an old style vm command
 1 commands
 ]/listcmds gl
   globalservers --
 1 commands

Auto-completion:

 ^3-> ^*/shader
    shaderexp  evaluate a q3shader expression (RB_EvalExpression)
    shaderpath cvar - "^*" - text - path to load GLSL source files at runtime
 ^3-> ^*/build
    build         an old style vm command
    buildcubemaps generate cube probes for reflection mapping
 ^3-> ^*/gl
    globalservers --
    glsl_restart  recompile GLSL shaders (useful when shaderpath is set)
 ^3-> ^*/listcmds g
    g_                  
    gfxinfo             dump graphics driver and configuration info

OK so there's a bug with listCmds that it won't show commands without a flag.

static ListCmdsCmd listCmdsRegistration("listCmds", BASE, "lists all the commands", ~(CVAR|ALIAS));

But I don't see -- anywhere with the migrated commands.

But I don't see -- anywhere with the migrated commands.

This works fine on my end after a full rebuild.

OK so there's a bug with listCmds that it won't show commands without a flag.

Yeah, found the same issue.