DispNameChanger
About
DispNameChanger is a plugin that lets you easily change your display name or any other player's display name. In the current context of Bukkit, that means the username that is displayed on death, when you talk, etc etc etc. Optionally, if Spout* or TagAPI**
is installed on the server, this plugin will change the display name above a users head.
*
Do note that the Spout Client, SpoutCraft, is required to see this change.
**
TagAPI has some restrictions in how it works in changing the display name. Please see the TagAPI page for limitations.
Quote from SniperFodder:IMPORTANT If you would like help with the plugin that is perfectly fine. However, to assist everyone better, please open a ticket if you believe there is a bug. If you would like support for another plugin, or a feature suggestion, also please open up a ticket. I can not properly support everyone in the comments section. Everyone is also free to post questions in the forum. I generally get back to people within 1 day. If I'm not answering questions in the forum, or on the main page, please feel free to highlight me on the bukkit forums; same username.
Latest Version
Download the latest compiled version of the plugin here. Source Code (GitHub Repository)
- Plugin Version: 6.0.0 | May 11th, 2013
- Bukkit Compatibility: Recommended Build: 1.5.2-RC0.1
Beta Version
Download the latest compiled beta version of the plugin here.
- Plugin Version: None Currently Live
- Bukkit Compatibility: N/A
Known Issues
These are the currently known issues. For more information please check the ticket system.
- Names that are right at 16 characters and have the prefix option enabled will be truncated by the plugin.
- Commands with Display Names don't work in server console (yet).
- If a killer's in-game name is the same as any words previous to the name in a death message, the wrong word will get replaced with the displayname.
Frequently Asked Questions
Users can find the FAQ to this plugin here.
Features
This is the current feature set of the plugin.
- Change the display name of a specified player, including yourself.
- Can use spaces in name by surrounding with quotes ""
- Supports Bukkit SuperPerms
- Persistence: Display names last through session changes (Thanks to Sammy)
- Supports Colors (Thanks to itsacoshop247)
- Spout: If installed, changes player's names above heads (Only if the client is using SpoutCraft).
- Ability to toggle title integration as well as announcements on name change
- New TagAPI: If installed the plugin will use TagAPI to replace the name above a players head.
- Please see the TagAPI page for a features list in how it works with Vanilla Servers.
- If Spout and TagAPI are both enabled on a server, TagAPI Support will be disabled in preference of Spout.
- Ability to toggle kick/quit/death message integration.
- Scoreboard/PlayerList integration
- All display names must be unique
- Localization now added!
- English
- French
- If you would like to translate the plugin into your language, please check this page here.
- DispName Prefix: Users can now turn on a Prefix that will be prepended to user names to signify that a username has been changed.
- Prefixes can now be colored.
- Display Names can be used in other commands like /kick and /tp.
- Command Filtering to prevent all names being replaced in commands.
- Display names can be globally announced, either to everyone or only those with the 'dispname.announce' permission node.
- Can restrict usage of the following chat Style codes using the following nodes:
- Bold | dispname.color.bold
- Italic | dispname.color.italic
- Magic | dispname.color.magic (Random characters)
- Strikethrough | dispname.color.strike
- Underline | dispname.color.underline
- Can restrict the usage of all Chat color codes.
- Can list all users with changed display name.
- Choose when to save Display Names!
- Completely disable saving! (Will warn user if this happens).
- Display List Command now Paginated!
- Pagination can be disabled by setting pagination to 0.
Possible Features
- Censorit Integration
- Suggestions?
More Information
You can find more about the plugin on the projects GitHub Wiki page. This includes commands, permission nodes, and the like.
Credits
Credit is needed where credit is due.
- captainawesome7 | Original Author
- itsatacoshop247 | Contributor
- Daxiongmao87 | Contributor
- Luke Zwekii | Contributor
- Sammy | Contributor
- bearbear12345 | Contributor
- morganm | Contributor
ChangeLog
Current change log for the plugin, last 2 versions.
[ ! ] Signifies a change or Bug Fix.
[ + ] Signifies the addition of something.
[ - ] Signifies the removal of something.
Version 6.0.0
- [ ! ] Resolved Reset Name Bug
- [ ! ] Resolved killer's Name being used instead of Display Name.
- [ + ] Added TagAPI Support.
- [ - ] Removed some left over debug lines.
Version 5.9.0
- [ ! ] Resolved bug with Command filter not properly filtering when number of commands to filter was greater than 0.
- [ + ] Added Ability to toggle spout title integration, as well as spout announcement for name changes.
- [ + ] Added Configuration options to config.yml for spout integration.
- [ + ] Converted project to Gradle. Building is as simple as ensuring you have Gradle installed, and calling gradle build on the plugin. The project can also easily be converted to a maven project if you so choose as well since the directory structures are roughly the same.
- [ - ] Removed some left over debug lines.
If you have questions, concerns, or just generally want to talk about the plugin, please do so here. Otherwise, general comments are welcome on the main page.
In your latest release there is a massive amount of spam in the console. It outputs 4 lines when someone who has a display name logs on. Would it be possible to have the console messages disabled or have a config option to do this.
Thx
Update - A link to the console readout that I get when using the /checkname command http://pastebin.com/raw.php?i=ZqfcWAyR This has 7 lines in the console.
@sandervdwest
I've pushed out a beta version of the plugin with the ability to use Display names in Commands now.
You can find the link either on the files page or above in the project description.
Post any bugs you find to the ticket system please.
@sandervdwest
Jascrod is correct. It is on my todo list. Using display names in commands is not such a simple feature to integrate. I have to monitor all commands for display names and re-execute them with the real names.
@sandervdwest
"Possible Features Display names used in commands"
Maybe you should read the description -.-
I don't know if I'm the first one finding this but if you kick somebody or do some other command you still have to type the old name of the player...
I would have installed this plugin in my server if there was a possibility to use the changed name in commands like /kick and so on.
Alright, I've pushed out v5.3 for use by everyone. Do note that I can not guarantee that this version will work with your current config/database files. So if you have any issues try deleting them. If all else fails, post a ticket.
This was a major overhaul of most of the files within the plugin. I shuffled methods around, added functionality, changed behavior.
One thing i would like to note for everyone: If you try to use the Prefix with colors, scoreboard integration, and colors within your displayname, your Displayname will turn up VERY short. This is because the Playerlist has a max 16 characters for the name. This includes color codes!
Furthermore, I think I ironed out most if not all of the bugs. Please let me know right away if you encounter any bugs during your usage so I can try to fix them. I think I got everything squared away, but I can not guarantee that either. I spent a good chunk of time on this ( ~ 8 hours) and I'm dead tired.
Attention Everyone:
I recently discovered a critical error on my part in relation to how I handle Color Codes. I removed advertised functionality accidentally awhile back and have come to the conclusion that this needs to be re-added. The functionality is in relation to manually adding chat colors to nick names. Please reference: ColorCode Ticket
I will be pushing a HotFix with this change, as well as a fix for prefixes not being able to manually set by users in a few hours.
For those of you that have been turned down ChatColor wise within nicknames, I apologize for that. I fatally misread some code, and the user base has paid for it. I still whole heartily endorse the use of ColorMe for coloring nicknames, but now you will be able to regain the ability to add the color codes in manually.
Thanks to everyone that kept bugging me about this feature.
Pushed out a new version. File needs approval. Link in the description for those impatient.
@vsams14
And it works with that option?
<<reply 571788>>
And I’m a noob. Right in Essentials config file, it says
“# Disable this if you have any other plugin, that modifies the displayname of a user.
change-displayname: true”
I don;t know how I didn’t notice this earlier…
You were correct, the issue was Essentials. Is there any chance that you could try to make this Essentials compatible (once this mess with 1.2 updates is over)?
I really like the essentials spawn tools, like changing the spawn point and setting warps. Of course if you don’t want to change your code just for one person, that is also understandable.
Regardless, I just tested the newest version, and it definitely changes my chat name! Now just to wait for Spout to update…
vsams14
@silentdojo
Yea.... Somehow I fucked up my jardesc file (which eclipse uses for easy building of jar files) and included the LIB and Release folder. So I was including the bukkit API and SpoutPlugin api in the jar O_o.
Thanks for catching that. It fixed a problem I was having with building my plugin.
@SniperFodder
LOL I was like well I'm sure you just forgot something. And I wasn't trying to use a 7 MB file just to change names. Thx for the quick update.
@silentdojo
Sunuva biscuit eating noob. I'll re-upload it. Stupid piece of shit jardesc file.
Did you notice the latest build is about 7 MB?
In case no one was paying attention to the ticket, I pushed an update out. Right now I'm still confused as to why that error is being thrown, but it should be fixed for now.
Also just a note to everyone out there that uses spout on their servers: I have not tested this plugin with spout. I couldn't find a stable enough build to test against. There are probably some bugs that need to be fixed, but I can't fix them until Spout Devs push an update out.
@Jythri
Hahaha fucking brilliant. I hate you bukkit team....
It's broken, with CraftBukkit R6.
I get an error when I launch the server, and in-game, not only do I not have my old permissions, I cannot apply new ones.
Here's the relevant part of the log:
@monsoue
Nope.
Unless something is broken, then I won't be doing any updates for awhile yet.
any update on 1.2.2 or R6?