[INFO/CHAT] Notificator 0.2 - Command, Death, Region Announcements [1060]

Discussion in 'Inactive/Unsupported Plugins' started by 2n3904, Sep 8, 2011.

  1. Offline

    2n3904

    <font color="rgb(0, 0, 0)"> Notificator - Command, Death, Region Announcements</font>
    <font color="rgb(0, 0, 0)">---------------------------------------------------------------------------</font>
    <font color="rgb(0, 0, 0)">Version 0.2</font>

    A little plugin for those who want everyone on your server to know what everyone else is up to. Made because of a request by jasonsj10.

    ...And to play around with handling a submitted plugin before I go and release my big plugin project:<font color="rgb(0, 0, 0)"> Battlefields!</font>

    Notificator allows three types of event notifications (maybe more if you'd like some) which it will broadcast to all players on the server (or on just that world):
    * Commands

    - * Broadcast command usage to everybody! Notificator lets you either set up a default message of your choice that displays the command used to everyone, or set up unique messages for particular commands.

    * Regions (WorldGuard Required!)

    - * Broadcast player movement to everybody! Notificator lets you either set up default entry/exit messages of your choice that can display the worldguard region name, or set up unique messages for particular regions.

    * Deaths

    - * Notificator also lets you broadcast the cruel fates of other players to everyone can have a good laugh at their untimely demise. Supports custom messages for all types of deaths - mob specific, PvP, randomness (fire, falling, drowning etc.)

    For sneaky admins who don't want everyone to know what kind of shenanigans they are mixed up in, Notificator also allows a few permission nodes, which should be self-explanatory as far as their function. Supports both PermissionsBukkit and Permissions 3:


    Show Spoiler
    notificator.silent (all)
    notificator.silentdeaths
    notificator.silentcommands
    notificator.silentregions


    The configuration file is lengthy. Here's how it looks by default (lots of comments to help you along in your exciting set-up adventure):
    Code:
    Config File said: 
    # -----------------------------------------------------------------------------
    #  CONFIG FILE : Notificator
    # -----------------------------------------------------------------------------
    # Author : 2n3904
    # Release Date : 9/10/11
    # Version: 0.2
    # -----------------------------------------------------------------------------
    # Make sure to check with a YAML parser! No tabs! My advice is to copy a similarly indented line
    # then edit the text ONLY. This should prevent most common errors.
    # -----------------------------------------------------------------------------
    # Permission Nodes:      notificator.silentdeaths, notificator.silentcommands,
    #                        notificator.silentregions
    # -----------------------------------------------------------------------------
    
    # Display on all worlds, or just the one the player is in?
    betweenworlds: false
    # Display message to player that triggered it?
    displaytosender: true
    # Prefix for all announcements made by this plugin:
    prefix: ''
    # Suffix for all announcements made by this plugin:
    suffix: ''
    
    # -----------------------------------------------------------------------------
    #  Command Announcements
    # -----------------------------------------------------------------------------
    # The numbers correspond to the number of arguments. For example, '/tp from to' has two arguments
    # 'from' and 'to'. In this case, you would put the command name under '2'. Or if you want '/tp to'
    # (one argument) put it under '1'. Put all commands that have the form '/command' with no arguments
    # under '0'. The text next to the command name is the message to be sent.
    
    # Send a default message for all commands instead those listed
    defaultcommandmessages: false
    # Default message
    defaultcommandmessage: '&4This is the default command message. You used <command>!'
    # Messages to send (examples included):
    commands:
        '0':
            time: '&6<player>&f glanced at their watch!'
        '1':
            tpa: '&6<player>&f asked <playerargs1> for outgoing teleport permission!'
            tpahere: '&6<player>&f asked <playerargs1> for incoming teleport permission!'
            tp: '&6<player>&f teleported to <playerargs1>!'
            warp: '&6<player>&f warped to <args1>!'
        '2':
            tp: '&6<player>&f teleported <playerargs1> to the player <playerargs2>!'
            warp: '&6<player>&f warped <playerargs2> to <args1>!'
    permissions:
        tp: essentials.time
        tp: essentials.tp
        tpa: essentials.tpa
        tpahere: essentials.tpahere
        warp: essentials.warp
    
    # -----------------------------------------------------------------------------
    #  Region Announcements
    # -----------------------------------------------------------------------------
    # NOTE : MUST HAVE WORLDGUARD INSTALLED TO USE THESE
    # These are a list of all the region names that you want announced. Simply place the region name
    # under 'regions' and then edit the enter and exit messages to your desire. Alternately, you can
    # define a default reigon message for all regions and ignore the specific ones.
    
    # Use default messages instead:
    defaultregionmessages: false
    # Default messages:
    defaultregionentermessage: '&f<player> has entered the region <region>!'
    defaultregionexitmessage: '&f<player> has left the region <region>!'
    # List of regions to announce:
    regions:
        example:
            enter: '&6<player>&f has entered this custom message area!'
            exit: '&6<player>&f has left this custom message area!'
    
    
    # -----------------------------------------------------------------------------
    #  Death Announcements
    # -----------------------------------------------------------------------------
    # Below are the types of deaths and the messages associated with them. For players killed by mobs, use
    # 'entity'. The variable '<cause>' will be altered to match whatever entity killed the player. If the death
    # was from PvP, the pvp message will be sent with '<cause>' being the player's name.
    
    # Enable death messages:
    deathmessages: true
    # Messages to send:
    death:
        drowning: '&4<player> has drowned!'
        cactus: '&4<player> has been killed by a plant!'
        fall: '&4<player> has fallen to their death!'
        tntsplosion: '&4<player> has been vaporized by TNT!'
        creepersplosion: '&4<player> has been vaporized by a creeper!'
        lava: '&4<player> has been incenerated by lava!'
        fire: '&4<player> has burned to death!'
        lightning: '&4<player> has been struck down by lightning!'
        suffocation: '&4<player> has suffocated to death!'
        suicide: '&4<player> has committed suicide!'
        void: '&4<player> has fallen into the endless void!'
        entity: '&4<player> has been slain by a <cause>'
        pvp: '&4<player> has been slain by <cause>'
        unknown: '&4<player> has been been mysteriously killed!'
    
    Read the comments for more info on what the different settings are. Note that Notificator supports custom variables in the messages (ask if you think of more to add):

    <player> - Shows the player who caused the announcement
    <world> - Shows the name of the world the player is in
    <argsX> - Shows the argument of the command given by the number 'X'. For example, if you type a command '/command blah dah', <args2> will display as "dah". Used only for command messages.
    <playerargsX> - Same as argsX, however it will try to match the argument to a player online. If it finds nothing, it cancels the announcement. For example '/command blah duc' when 'Duck' is a player will replace 'duc' with 'Duck'. Used only for command messages.
    <command> - Displays the command name. For example '/command wheee' will replace <command> with 'command'. Used only for command messages.
    <region> - Displays the region name. Used only for region exit/entry messages.
    <cause> - Used only for entity/pvp death messages. Displays who/what killed them.

    <font color="rgb(255, 102, 0)">C<font color="rgb(255, 0, 0)">o</font><font color="rgb(51, 153, 102)">l<font color="rgb(153, 51, 102)">o</font><font color="rgb(51, 102, 255)">r</font>s</font> <font color="rgb(0, 0, 0)">in messages are supported (The standard &1-9, &a-f scheme)</font></font>

    <Edit by Moderator: Redacted mediafire url>

    Changelog:
    Version 0.2 (9/9/11)
    * Added permission nodes for command announcements

    - * Will only announce the command id the player has the permission node defined for that command in config. If no node is defined, will announce always.

    Version 0.1 (9/8/11)
    * First release.
     
    Last edited by a moderator: Nov 12, 2016
  2. Offline

    jasonsj10

    Thank you so much for replying and doing the request i put out. This is amazing. Please bukkit accept this plugin
     
  3. Offline

    jasonsj10

    Are you updated this to 1.8 when RB comes out?
     
  4. Offline

    BlancoLanda

    Hi! This is good, but... Why don't you do premissions notificator.notify , notificator.notifydeaths, ...? better than notificator.silence ... because admins can't see notifys when having all permissions enabled. :S
     
  5. Offline

    2n3904

    The silence only silences the notifications that stem from something you do - with those permissions you'd still see other people's notifications. The notificator.notify makes sense when you use permissionsbukkit (where you can set it false for admins despite inheritance) but for perms 3 it fails. Thats why I did it this way. But yes, it is kind of quirky.

    I'll change the permissions up a bit to add a few more options.

    Also, need to fix the display names always showing the REAL name of the player.

    Sure, it probably won't break on the update though.

    I'll take care of these things in a second and Ill test it on the latest Bukkit dev, to see if I need to do anything for 1.8.
     
  6. Offline

    jasonsj10

    Well, Did you know they added a built in Death Notifier? Is it possible to disable it and still use this? (CB: 1149)
     
  7. Offline

    jasonsj10

    Umm, Will you update it so it says when Endermen and Cave Spiders kill it says?
     
  8. Offline

    blasterweb

    Ahh, it doesn't work, but I'm assuming that you don't need a "permissions" file, since every player in my server is admin?
    I can define regions very fine in WorldGuard and such, but can't get Notificator to work with it. I have defined my region to to "done1".

    Code:
    # -----------------------------------------------------------------------------
    #  Region Announcements
    # -----------------------------------------------------------------------------
    # NOTE : MUST HAVE WORLDGUARD INSTALLED TO USE THESE
    # These are a list of all the region names that you want announced. Simply place the region name
    # under 'regions' and then edit the enter and exit messages to your desire. Alternately, you can
    # define a default reigon message for all regions and ignore the specific ones.
    
    # Use default messages instead:
    defaultregionmessages: false
    # Default messages:
    defaultregionentermessage: '&f<player> has entered the region <region>!'
    defaultregionexitmessage: '&f<player> has left the region <region>!'
    # List of regions to announce:
    regions:
        done1:
            enter: '&6<player>&f has entered this custom message area!'
            exit: '&6<player>&f has left this custom message area!'
    
        example:
            enter: '&6<player>&f has entered this custom message area!'
            exit: '&6<player>&f has left this custom message area!'
    
    Can anyone tell, why it doesn't work?
     
  9. ...........Video or picture would be nice...

    @blasterweb Do you have permissions,groupmanager? Do you have worldedit and worldguard? You need these plugins: Worledit,Worldguard,and Permissions (or groupmanager from essentials)

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 19, 2016

Share This Page