The Ravenous Bugblatter Beast of Traal
Stupid, but extremely ravenous!

Name Management Plugin - Version 3.3 - Overview

Filename: plugin_blatt_name

Offline Manual

You are reading this offline manual for this plugin. The links to the right navigate through the offline information. The links above and to the left link to www.ravenousbugblatterbeast.pwp.blueyonder.co.uk. If you downloaded the plugin from somewhere else, or downloaded it some time ago, I recomend you check for an updated plugin. Note that the on-line manual may have been updated even if the plugin hasn't.

Overview

The Name Management Plugin regulates the names of players that connect to your server. This can be used for a number of purposes:

  • To prevent players using the default name for your game mod such as 'Player' or 'Private', which can lead to multiple players in the game with similar names - Player, (1) Player, (2) Player etc. causing confusion, and to Player sitting at the top of your server stats.
  • To prevent players using very short names, such as "." which means you don't notice their name appear on the screen when you aim at the camping gits.
  • To prevent players attempting to exploit Half-life/ Counter-strike/ Admin Mod script loop holes (many of which are fixed anyway). Many admin commands allow you to use either a player id, wonid or name to identify a player. Some players give themselves a numeric name which may match another players id or wonid, hence causing you to issue the commands on the wrong player.
  • To make player names easier to read and/ or type.
  • To identify players who are ghosting - i.e. can see each others screen/chat. The plugin can modify their name with a 'LAN Tag' to indicate who is ghosting, announce warnings to the other players, and automatically switch on/off forced chase camera mode.
  • To prevent players from changing their name whilst connected. (personally, I wouldn't recommend this)
  • If Logd is present on the server, the plugin will not alter a players name until after they have chosen a team, so that they get a change to see the information messages explaining why it has happened.

Each of these functions can be independently enabled and disabled by the admin, and a number of options can be modified to control how stringent the restrictions are.