Nameless Players

Nameless Players 1.1.0

Sign in to download
Hides player names, replacing them with a blank or custom text
Documentation License Changelog (1) Version History Discussion
This plugin hides player names in both above their heads and in chat, creating a more anonymous gameplay experience. The default replacement is an invisible character, but it can be customized.

Note: Fully compatible with Better Chat plugin.



Permissions

  • namelessplayers.use - Allows a player to have their name replaced with the custom text as configured.

Configuration

JSON: 
{
  "Version": "1.0.0",
  "Name Replacement": "\u200B"
}
  • Name Replacement - The text that replaces player names. Default is \u200B (invisible character). You can set this to any custom string.
  • Like
Reactions: (Manky)sieve
Author
VisEntities
Downloads
15
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

Latest updates

  1. 1.1.0

    Default behavior now leaves player names unchanged unless a player has the namelessplayers.use...
Read more…
Back
Top
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Make sure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart

Cart

Total -