krinsdeath / chatsuite Goto Github PK

The plugin hooks into Multiverse to automatically detect any aliases you've set up for your worlds, instead of using those ugly and bulky underscored names (world_nether?). It also migrates colors, and can be configured to your taste.

I tried to create a channel with /ch create owner, and saw this:
http://pastebin.com/SBRk23qh

Through the use of /cs create (channel), /cscreate (channel) or /csc (channel), users will be able to create (and automatically join) their own chat channels, and invite their friends to have private group conversations.

The ability to create these channels is allocatable via permissions, but defaults to ops only.

How come ChatSuite is disabled (and has been for a long time) on the Multiverse Jenkins? If I want the latest changes, do I have to download and compile it myself now?

Also, as an aside, you should add ChatSuite to dev.bukkit.org! It's a lot better than most of the chat plugins on there.

Whenever players leave and re-enter, they cannot see any chat. Reloading fixes the issue, but is a pain.
Players can see the chat normally when they first join.

With op_fallback set to false, and assuming a group called "foo":

Chatsuite determines if a player is a member of group "foo" by checking the permission nodes chatsuite.groups.foo and group.foo. chatsuite.groups.foo is registered by chatsuite and defaulted to false; group.foo is not, and the default for an unknown permission is that it returns true for ops. Thus ops will appear to be in group foo unless the group.foo permission is explicitly negated.

Formats don't seem to be working, I'm trying to get rid of the channel name (I only want one channel) and no matter if I use the global format or the group-specific format option in config.yml it doesn't seem to have any effect.

Dont know how (or if) you can delete these. Issue isnt really relevant anymore.

It seems superfluous for the default format to display the channel name, when allow_channels is set to false, because I think that means there will only be one (Global) channel?

Via the use of the basic command /cs (or /cs help), your users should be able to understand the ins (and outs) of this plugin with relative ease. The commands will be documented well, and will include a localization file from which it draws its messages, meaning you (the admin) can customize the messages or translate them to new languages.

By typing /cs afk (message), /csafk (message) or /csa (message), users can toggle their AFK status. Server admins can enable or disable the ability to set a custom away message, or enable or disable that user's auto-responder via flags in the configuration file.

Not yet fully done, but so far the public API should be very simple and very powerful. ChatSuite will attempt to be the last plugin to modify an event (through Priority.Highest). By using the methods provided (getFormat() and setFormat()), any plugin developer should be able to inject changes to the format with little difficulty, and through resetFormat(), change them back to their defaults.

I run a very quiet server where people can sometimes be idling for hours, and my users have requested timestamps in chat

http://img.127001.org/img/2013-06-04_14.19.47.png

The timestamp in the screenshot was obtained with

new SimpleDateFormat("HH:mm").format(new Date());

I could send a PR, but I'm not sure whether you'd want to cache the SimpleDateFormat object rather than create it anew each time, or what token you'd want to use for the timestamp (%time breaks the single-letter-is-abbreviation-of-longer-word convention you have)

When I change world with /mvtp <world> the world prefix isn't updated.

Using the %fn modifier causes this error. When I instead use%n everything works perfectly. I have yet to try %dn but I have a feeling it will work.

Probably relevant: I don't have any prefixes/suffixes set in players.yml.

Let me know if you need more information such as configuration files.

Custom chat channels for players, including world-specific ('local' chat) and global channels ('server wide'), as well as custom channels specified by players.

Creation of chat channels can be tailored to users with permissions.

By default, users will have access to global chat (server wide) and their own world's chat.

finished

By typing /cs whisper (message), /cswhisper (message) or /csw (message), users can whisper between each other, in privacy, across worlds. Server admins can set specific worlds to disallow whispering, or disallow whispering altogether, via the config.

When using privileges and chatsuite the group prefix will not update automatically when the users group is changed. You have to force chatsuite to reload in order for it to be updated.