I'm not sure what it is you figured out, but... You can control what flag/type has what access to what commands in the netmux.conf file (or whatever it's called). For example, here's what we had at Fallen World (copied from elsewhere, we didn't actually use Builders there):
access @dig builder
access @dig/teleport builder
access @open builder
access @create builder
access @destroy builder
access @quota builder
function_access create builder
function_access destroy builder
function_access link builder
Alternately, as I think they did on Reno (and elsewhere?), you can create commands and place them on the staff global. The command basically just runs @dig
, but does so with inherit access from your wiz. You could also, also just create a new object that's locked, or a new command that checks, for a certain attribute or flag or even just a list of dbrefs. The command would be something like +dig
that just runs like @dig
, but, again, with wiz-inherit access.
Hope that helps!
Edit #3: On all the games I have helped run (BITN, Fate's Harvest, Fallen World), we just chose a builder and gave them Wiz access and told them not to break anything. They didn't break anything. 