This is something that should have been automatic for a long time. No
building for people who have a certain name prefix. In our case, we would
use it to prevent unnamed players from building, without having to
!denybuild them.
Advantages of an automatic system are that players would not have to wait
for an admin to !allowbuild them, they would just have to rename and then
they could build the same as ever before.
The system would work by use of 2 cvars.
g_noBuildPrefix "" <-- Prefix which defines who can and cant build.
Basically anyone with this in the beginning of the name cannot build. In
our case, this would be set to UnnamedPlayer, and the server would ignore
the noob numbers.
g_noBuildMsg "" <-- The message which is displayed to users who match the
string above. This would be cvar to allow server operators to set it, as
they may use it for something other than unnamed building
Original issue reported on code.google.com by Paradox460 on 28 May 2008 at 8:34
```
This is something that should have been automatic for a long time. No
building for people who have a certain name prefix. In our case, we would
use it to prevent unnamed players from building, without having to
!denybuild them.
Advantages of an automatic system are that players would not have to wait
for an admin to !allowbuild them, they would just have to rename and then
they could build the same as ever before.
The system would work by use of 2 cvars.
g_noBuildPrefix "" <-- Prefix which defines who can and cant build.
Basically anyone with this in the beginning of the name cannot build. In
our case, this would be set to UnnamedPlayer, and the server would ignore
the noob numbers.
g_noBuildMsg "" <-- The message which is displayed to users who match the
string above. This would be cvar to allow server operators to set it, as
they may use it for something other than unnamed building
```
Original issue reported on code.google.com by `Paradox460` on 28 May 2008 at 8:34
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Original issue reported on code.google.com by
Paradox460on 28 May 2008 at 8:34