[CHAT] Multicast v1.08 - Simple channels for ops/admins [600-818]

Multicast - Simple channels for ops/admins
Version: v1.09

Need to chat with your ops/admins but don't want a full-scale channel system? Multicast integrates with Permissions to chat with groups. The default setup is

Code:

o=Ops
a=Admins

The server now has two channel codes, "o" and "a", referring to the named channels "Ops" and "Admins". The channel name is purely cosmetic!

So far, there is no relationship between the channels and the groups. This relationship is defined by granting access in "Permissions/config.yml":

Code:

multicast.o.send
multicast.o.receive
multicast.a.send
multicast.a.receive

On my own server, members of the "ops" group has access to send on both channels but only receive on "o". Administrators ofcourse have '*' so they can send and receive on any channel.

Now, to chat with my ops, I simply type

Code:

/multicast o This important info can only be read by ops and admins

This simple Permissions-controlled setup means you can grant permissions directly to users if you want to create "multicast groups" that are not limited to or inherited by groups.


Features:

• Configurable commands once more!
• Configurable channels
  
• Integrates with Permissions 2.5.4
• Not limited to groups, grant send/receive permissions to individual players

Download http://minecraft.atc.no/plugins/Multicast.jar
Recommend you combine this with http://minecraft.atc.no/plugins/RegexFilter.jar
Source code is included

Changelog

• 1.00 - Original release
• 1.01 - Changed plugin namespace
• 1.02 - Removed the "stupidly long constructor" as per Bukkit team recommendation
• 1.03 - Dynamic commands are no longer supported. Plugin adapted by implementing a /multicast command. This makes it a little more cumbersome but there are solutions.
• 1.04 - Eaten by the cookie monster
• 1.05 - Fixed deprecated calls to Permissions. Version 2.5.4 is now required.
• 1.06 - Dynamic commands supported once more. Yay!
• 1.07 - Removed debug messages that were accidently left in. Oops.
• 1.08 - Fixed a bug causing Permissions 2.6 to misbehave.
• 1.09 - /multicast command now works properly from the server console.

TODO

This plugin will be updated to work with built-in permissions. Other than that I aim to keep it as simple as possible. If you want a full-fledged channel system, I recommend you look elsewhere.

As with all my plugins, the source is included with no strings attached. Have fun!

 

this is nice. exactly what i needed without all the other junk of other plugins

 

please update your OP to reflect the standards http://forums.bukkit.org/threads/plugin-release-submission-guidelines.1755/

 

If you still have issues with my OPs, please be specific ok?

oh, and
Picky, picky.

 

Are you using onCommand? You mention that you can configure the command to use..

 

No this plugin uses onPlayerCommand() for now. Not exactly sure how I'll solve this with onCommand() but I'm sure the solution will require creative use of aliases. *scratches head* Perhaps a command + channel name, like "/multicast o <message>" and then an alias "/o" -> "/multicast o". I don't even know how aliases will work...

So much for keeping it simple.

 

I was asking because I have the same problem, and cant think of a solution given the design of the bukkit interface is optimized for fill and all that it will be using.

 

lol wut?

check out my wool give plugin for oncommand usage, or check out scrapbukkit

 

I know how to use onCommand() but it means all commands have to be declared in "plugin.yml".

= no user-configurable commands.

 

I know how to use onCommand; my plugins actually use it. The problem is the YML that is being enforced for registration of the command, as said FloydATC

 

I was about to make this myself. Nicely done.

 

I have just posted v1.01, this is a minor but required update because the Bukkit team now requires that no plugins be defined in the *.bukkit namespace for security reasons. If the plugin suddenly stops working with a new Craftbukkit build, this is why.

There are no changes to the code itself.

 

Thx for the source code
Any copyright or will to receive credits ?

 

No restrictions but credits would be nice

 

Well I nearly finished coding my plugin, I erased a bit of everything from your plugin but it inspired me much at the begining so i'll credit you

Btw, if you're interested by my Release 0.1 :
http://forums.bukkit.org/threads/ch...create-and-manage-multiple-channels-440.6404/

 

The onPlayerCommand() callback is gone as expected so dynamic commands are no longer possible. I have just posted a new version (v1.03) which changes the way the plugin works:
"/o message" is now "/multicast o message"
"/a message" is now "/multicast a message"

But... this totally defeats the purpose of Multicast doesn't it? Yes and no. Combine this plugin with my RegexPlugin or any other plugin that lets you define aliases or macros. With RegexPlugin I simply added the following to rules.txt:

Code:

match ^\!o
then replace multicast o
then command

match ^\!a
then replace multicast a
then command

The result of combining Multicast and RegexPlugin in this way?
"/o message" is now "!o message"
"/a message" is now "!a message"

 

You should try onCommandPreprocess, or register both o and a in your plugin.yml file
http://forums.bukkit.org/threads/new-command-interface-everything-is-broken.6397

 

I hate the idea of plugins registering one-character commands but hadn't noticed the post about getCommand(), thanks for the tip. Will give it a shot right away, thanks for the tip!

 

I still can't get dynamic commands to work, but here's a small update (v1.05) which fixes deprecated calls to Permissions. Note that this means version 2.5.4 is now recommended, other versions may or may not work.

 

You should try onCommandPreprocess() in the PlayerListener class to get your dynamic commands work.

 

Yay, finally got around to actually implementing onCommandPreprocess(). Still kept the old /multicast command workaround so as to not break anything but the plugin will now work as it used to do back in version 1:

If you define a channel "o" (named "Ops" or whatever) then you can once again talk on that channel using

Code:

/o your message here

The version number is 1.06

Update: I accidently left some excess debug messages in the .jar, version 1.07 fixes this.

 

Ouch. I made a BAD mistake in the Permissions interface, switching player and world names. This causes Permissions 2.6 to start dropping YML files all over the place in an attempt to deal with the funny requests.

Multicast version 1.08 fixes this, sorry for any inconvenience this may have caused.

 

I love you ! But can you add support colors ?

 

Please excuse my density; colors where?

 

For exemple, i have 'Guarde' canal chat, i love to change it to [Guarde] and sorry i'm french ​

 

I have nothing against the french, in fact I love your fries ;-)​

Colored channel names already work, just put the usual minecraft color codes in settings.txt like so:​

Code:

# command=Channelname
a=§1Admins§f
o=§4Ops§f

In this example, the channel names would appear as Admins and Ops.

 

Okay thanks ! i'll just try it and seems to no work :s

 

That's odd... I tried it on my own servers before posting just to make sure and it worked here. I tried it again with the [] characters and that works too. My first thought is that maybe your text editor is using a different character set, encoding or something that breaks the § sigil, but then you should atleast see the incorrect code or something. Try some different character combinations and let me know if you find the solution.

Oh and keep in mind that Multicast.jar needs to be reloaded for changes in settings.txt to take effect.

 

I use notepad++ :/

 

Make sure the file is saved in plain ASCII mode, nothing fancy like UTF-8.