AdminChat
AdminChat allows admins to have private conversations about users or any other server issues without disrupting the public or letting everyone see what they are discussing.
Updating to 1.3+
Please note, that the permission nodes have all changed as of this update! By default, the plugin creates an "adminchat" in the channels.yml, and this has the same format as previous versions of adminchat. The perm node to use this chat will be adminchat.channel.adminchat
Features:
- Let all admins online talk to each other privately
- Configurable format for the chat
- Allows creation of multiple channels
- Allows choosing the command for the channel
- Automatic update checking
Upcoming features (1.5.0)
- Individual Read/Send permissions per channel
- A mute command for either one or all channels, as well as unmuting
- Muting for a specified amount of time.
Configuration:
Config.yml: update-check:
- Default: true
- Checks for updates to adminchat on server startup, and will message ops/players with all perms on startup (if true) prefix:
- Default: "&a[&cAdminChat&a] "
- Prefix for plugin messages (for example automatic chat and updates)
Channels.yml
channels: channelname: command: 'chancmd' format: '&aEXAMPLE: {NAME}: &c{MESSAGE}'
You can make as many channels as you want within the channels.yml file. The "command" line will be the command you use in-game (along with <command-name>toggle), and the "format" line will be how it is presented in-game. Please note you should always include {NAME} and {MESSAGE} in the file exactly with the curly braces or the two will not show up.
Commands:
- /adminchat reload - reloads AdminChat, getting fresh values from the configuration files.
- /<channel-command> <message> - send a message to a private channel Ex. /ac What's going on in adminchat today?
- /<channel-command>toggle - toggled chatting within a private channel Ex. /actoggle
- /<channel-command> - same as above, toggle chatting within a private channel Ex. /ac
Permissions:
- adminchat.* - Grants all privileges for AdminChat
- adminchat.channel.<channel-name> - Allow a player to send messages to a private channel and read it
- adminchat.channel.* - Allows a player to send messages to and read from all channels
- adminchat.reload - Allow a player to reload AdminChat
@Speedyspro
If you can, send me a PM with some slightly more concrete clarifications on the issue.
Ooops i accidently cloned the repository, you can delete it.
Sorry :)
@1Rogue - Are you sure that Permissions are right? Because in my server Moderators can't read the private admin chat but can read the messages, but when I OP one of them, they can read messages that they send.. I'm using last version
@Minecraftian_Servers
I usually code plugins using as little of the API as possible so to future-proof them (more or less). This plugin should be able to run fine unless there's a severe overall to the chat system in the future.
Still working on the next update to allow for muting and other things.
@Minecraftian_Servers
Works for me using the latest spigot!
Does this work for 1.7.2? Using latest Spigot.
@Queketth
What version are you using?
I have a problem that, the correct people can send messages on the channels which I have set up but they are unable to see the chat (even what they are sending themselves!) I am running 1.6.4 Spigot and Ive tried on Bukkit and it makes no difference :(
Hey may you update plugin to 1.6.4 and 1.7.2 by the way it is awesome!
@Herpeto
It already is.
Can You make it this plugins can compatible with essentials groupmanager?
@grid21
Hm, strange. From the looks of it the plugin was unable to get the necessary channels (although it should have disabled). Is there a channels.yml in the folder plugins/Admin-chat ?
If not, make sure there isn't write-protection. If you still cannot manage to get the plugin working at this point, just create a new file under that folder named "channels.yml" and place the following inside of it to start:
Got an error as soon as I loaded your plugin. I hadn't even gotten to configure it.
18:47:30 [SEVERE] Error occurred while enabling Admin-Chat v1.3.0 (Is it up to date?) java.lang.NullPointerException at com.rogue.adminchat.command.CommandHandler.setExecs(CommandHandler.java:115) at com.rogue.adminchat.AdminChat.onEnable(AdminChat.java:93) at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:217) at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:457) at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:381) at org.bukkit.craftbukkit.v1_6_R2.CraftServer.loadPlugin(CraftServer.java:282) at org.bukkit.craftbukkit.v1_6_R2.CraftServer.enablePlugins(CraftServer.java:264) at org.bukkit.craftbukkit.v1_6_R2.CraftServer.reload(CraftServer.java:609) at org.bukkit.Bukkit.reload(Bukkit.java:277) at org.bukkit.command.defaults.ReloadCommand.execute(ReloadCommand.java:23) at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:192) at org.bukkit.craftbukkit.v1_6_R2.CraftServer.dispatchCommand(CraftServer.java:523) at net.minecraft.server.v1_6_R2.PlayerConnection.handleCommand(PlayerConnection.java:954) at net.minecraft.server.v1_6_R2.PlayerConnection.chat(PlayerConnection.java:872) at net.minecraft.server.v1_6_R2.PlayerConnection.a(PlayerConnection.java:829) at net.minecraft.server.v1_6_R2.Packet3Chat.handle(SourceFile:49) at net.minecraft.server.v1_6_R2.NetworkManager.b(NetworkManager.java:296) at net.minecraft.server.v1_6_R2.PlayerConnection.e(PlayerConnection.java:116) at net.minecraft.server.v1_6_R2.ServerConnection.b(SourceFile:37) at net.minecraft.server.v1_6_R2.DedicatedServerConnection.b(SourceFile:30) at net.minecraft.server.v1_6_R2.MinecraftServer.t(MinecraftServer.java:590) at net.minecraft.server.v1_6_R2.DedicatedServer.t(DedicatedServer.java:226) at net.minecraft.server.v1_6_R2.MinecraftServer.s(MinecraftServer.java:486) at net.minecraft.server.v1_6_R2.MinecraftServer.run(MinecraftServer.java:419) at net.minecraft.server.v1_6_R2.ThreadServerApplication.run(SourceFile:582)
@thequestingbeast
So what you're saying is you would like something like...
Permissions to read and permissions to speak be separate? I.e. someone could talk into a chan, but not read it, and vice-versa?
I could probably throw that in 1.3.1 with individual perm nodes for those actions. Wouldn't be too difficult.
I have been in need of a chat that default can talk into but only admins can see. I would love to see it have a configurable title for the chat.
It's a bug that will be fixed with the 1.3.0 release of adminchat that I will be pushing out today. In the meantime, using /actoggle will allow for spaces.
In /ac <text>, it doesn't count spaces. Same problem as rocky123xo.
Command: /ac Look at bob, it's suspicious
Output: [AC] Kanegae: Lookatbob,it'ssuspicious
I can't really get a paste of it, but after about a minute, spaces seem to take no effect. IE: /ac Hey what's up Would normally print: ADMIN: rocky123xo: Hey what's up but instead prints ADMIN: rocky123xo: Heywhat'sup
Any ideas? Didn't used to do this.
@dotapurex1 What do you mean by invisible? Do you have an example of the group you have permissions for that you are testing with? (You can upload to http://pastie.org/ )
the chat seems to be invisible with the latest version