[FlaminSarge]

Can you use CheckCommandAccess in the command callbacks so that sm_bhme and sm_bh use the override settings for their full counterparts, since they're just alias commands?

Also, nit, sm_setbh and sm_resetbh aren't in the main post's command list.

[Chaosxk]

Thanks, added sm_setbh, sm_resetbh and convar sm_blackhole_ff to O.P.

Is it really needed to add CheckCommandAccess when the alias commands can be added to admin overrides?

[FlaminSarge]

Originally Posted by Chaosxk Thanks, added sm_setbh, sm_resetbh and convar sm_blackhole_ff to O.P. Is it really needed to add CheckCommandAccess when the alias commands can be added to admin overrides?

Yeah, so my point was, if your setup is meant to be an alias setup (sm_bh -> sm_blackhole -> Command_Blackhole), then CheckCommandAccess would make sense. If it was instead supposed to be (sm_bh -> Command_Blackhole, sm_blackhole -> Command_Blackhole; the commands aren't intended to be aliases of each other), then it wouldn't. The capability to add the aliases to admin overrides is there, but logically, an alias of a command should have the same access as the base command itself.
Based on your intentions for the commands, treating them as aliases may or may not make sense.

(Also serves as idiot-proofing if somebody puts an access override for sm_blackholeme but not sm_bhme, then complains that people have access to it even though they've clearly not set things up properly).