Tags
Creators
Details
2.0.3
Compatibility
Changes
ChatNameColor 2.0.3
A major update has been implemented.
Overview
- Previously, only the name could be changed (though it was possible to force it into the config file), but now the name can be changed entirely via command.
- The commands have also been fundamentally changed.
NameEdit Command List
Main Command: /nameedit or /ne
Group Commands
グループ全体の設定を管理します。
/ne group list
Displays all existing group names.
/ne group create <groupName>
Creates a new group.
/ne group delete <groupName>
Deletes the specified group.
/ne group join <groupName> [playerName]
Adds a player to the group. Omitting the player name adds the command user.
/ne group leave <groupName> [playerName]
Removes a player from the group. Omitting the player name removes the command user.
/ne group edit color <groupName> <color>
Sets the base name color for the group. (e.g., red, blue, gold)
/ne group edit firstname <groupName> <text>
Sets the prefix appended to the names of players belonging to the group. Color codes (e.g., &c) can also be used.
/ne group edit aftername <groupName> <text>
Sets the suffix appended to the names of players belonging to the group.
/ne group edit name <groupName> <newName>
Bulk changes the display name of players belonging to the group to a name different from their individual MCID. Player Commands Overrides group settings with individual player settings.
/ne name <playerName> <newName>
Changes the display name of the specified player.
/ne firstname <playerName> <text>
Sets a personal prefix to be placed before the specified player's name.
/ne aftername <playerName> <text>
Sets a personal suffix to be placed after the specified player's name.
/ne color <playerName> <color>
Sets the color of the specified player's name individually.
/ne reset <playerName>
Resets all personal settings (name, prefix, color, etc.) and group memberships for the specified player.
General Commands
Manages settings for the entire plugin.
/ne reload
Reloads config.yml to apply changes to the server.
/ne luckperms <true|false>
Toggles integration with LuckPerms. (Requires server restart for full configuration changes to take effect)
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:RZkJYX53:SwzsvdW5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RZkJYX53:SwzsvdW5"
}

