Inactive [CHAT] iChat 2.4.4 - Custom Chat Formatting [1337]

Discussion in 'Inactive/Unsupported Plugins' started by Drakia, Feb 24, 2011.

Thread Status:
Not open for further replies.
  1. Offline


    iChat 2.x - Custom Chat Formatting
    Version: 2.4.4
    CraftBukkit: 1337

    Plugin Support:
    Permissions 2.x
    Permissions 3.x

    If you are requesting help, post your entire server log (From the time it opens, until somebody talks), your entire Permission config file (As well as what it's named), and iChat config files. This information is REQUIRED for me to help you. <-- Post configs there when asking for help

    Custom chat formatting.
    Based on the idea of iChat v1.5 by Nijikokun.
    Includes code and concepts from mChat by MiracleM4n <>

    Before downloading: iChat 2.4.x has quite a few changes over the 2.3.x branches. All permissions plugins are handled in one plugin, and they all operate in relatively the same way now. This means you WILL need to redo your configs.
    Download (Direct JAR):

    Supports Permissions (Both 2.0 and 2.1), and SuperPerms handlers (PermissionsBukkit, bPermissions, and PermissionsEx).
    Allows you to specify a prefix/suffix/variable for users and groups on a per-world or global basis.
    A user-specific prefix/suffix/variable will take priority over a group prefix/suffix/variable, a world-based prefix/suffix/variable will take priority over a global prefix/suffix/variable.
    Unlimited amount of custom variables for use in chat format.
    Colors are supported in all parts of the formatting and chat text.
    Usable health bar and health amount in the formatting.
    Support for formatting of /me

    Message formatting is defined in the file plugins/iChat/config.yml
    The message formats can contain characters, color codes, and variables.
    To use colors use the standard Minecraft color codes found here:

    Available variables:
    +prefix - The prefix for this user, or this users group if they don't have one defined.
    +suffix - The suffix for this user, or this users group if they don't have one defined.
    +name - The users name
    +displayname - The users display name (Set by plugins such as Towny)
    +iname - The iChat formatted player name (Defined by iname-format)
    +group - The users group
    +healthbar - A visual health bar for this user
    +health - The users current health value (Between 0 and 20)
    +message - The message the player typed
    +world - What world the player is currently in
    +time - Timestamp, configurable in config.yml. Uses the format for SimpleDateFormat -

    Example (Default):
    iname-format: '[+prefix+group+suffix&f] +displayname'
    message-format: '+iname: +message'
    me-format: '* +name +message'
    date-format: 'HH:mm:ss'
    handle-me: true
    Example date-format (Default):
    date-format: 'HH:mm:ss'

    As of iChat 2.4.0 there have been a few changes in the way variables and groups are handled.

    As of iChat 2.4.3 native groups are supported in Permissions 2.x/3.x, PermissionsBukkit, bPermissions, and PermissionsEx.

    Variables are now defined in variables.yml in the iChat directory. This includes prefixes, suffixes, and custom variables.
    You can define an unlimited number of custom variables for groups and users, if these variables contain the static variables such as +prefix,
    +suffix, +health, etc then those variables will be replaced with their respective values.
    If a variable does not exist then it will be replaced with a blank string.

    As of iChat 2.4.4 you can now specify world-specific variables. To specify a per-world group or user variable (Prefix, suffix, or variable) you just specify it under the world as shown in the 'world' example in the default variables.yml below. Anything specified in the parent 'users' or 'groups' nodes will be considered global for all worlds.

    Default variables.yml:
    # iChat Variable Config
    # This is now the only method for defining variables
            prefix: '&e'
            prefix: '&c'
            suffix: ''
            prefix: ''
            suffix: ''
          prefix: '&a'
    Default config.yml:
    handle-me: true
    date-format: HH:mm:ss
    message-format: '+iname: +message'
    me-format: '* +name +message'
    iname-format: '[+prefix+group+suffix&f] +displayname'
    To make a group colored:
            prefix: '&4'
            suffix: ''
    message-format: '[+prefix+group&f] +name: +message'
    To make a single username colored:
            prefix: ''
            suffix: '&1'
    message-format: '[+prefix+group&f] +suffix+name&f: +message'
    As you can see, suffixes and prefixes can be used anywhere, in any combination. In this example we use prefix as a method for coloring group names, while suffix is used to color individual users. On our server we have prefixes such as "&f[&2Mod&f] " so that we can have custom tags per group instead of just the groups name. There is no end to the combination of things you can do, please TRY things before you come asking for someone else to do it for you. There are too many combinations of things for me to answer every question about how to color specific things.
    I will not be offering answers to questions such as "How do I color names?" or really anything else to do with specifics of formatting. It's pretty straightforward what you can do, and if you can't take the time to experiment then I'm not going to take the time to answer your questions.

    iname-format - The format used for +iname (Default: '[+prefix+group+suffix&f] +displayname')
    message-format - The format used for basic chat (Default: '+iname: +message')
    date-format - The format used for +date (Default: 'HH:mm:ss')
    me-format - The format used for /me commands (Default: '* +name +message')
    handle-me - Whether to handle /me commands (Default: true)

    ichat.color - Allow this group/user to use color in their chat messages.
    ichat.reload - Allow this group/user to use "/ichat reload"

    /ichat reload - Reload the iChat config file

    Q) Why is my custom message format not working? I just get the default output. Or output with no variables filled in.
    A) If you're using Permissions 2.1, make sure your Permissions config file is named "{worldname}.yml" where {worldname} is the name of your world. If you're using Permissions 2.0, make sure your Permissions config is named config.yml

    Q) How do I set the brackets color to the same as the group?
    A) Normally you have the brackets in the message-format variable, but you can just as easily move them into prefix/suffix and that way they can be per-group colored!

    Q) Why is my entire string colored? I just put a color code beside +name!
    A) A color code will persists until another color code is encountered, or the end of the line is reached. To change the line back to white use &f after the variable/string you want colored.

    Q) Why are my OPs names red?
    A) Essentials has this functionality built in. Change "ops-name-color" to 'none' in your Essentials config file.

    Q) Why does {PluginX} not work with iChat?
    A) There's a good chance it does, but you need to use +displayname instead of +name.

    Q) Why does Towny not work with iChat?
    A) iChat no longer uses %1$s for the player name, it uses player.getName() and player.getDisplayName(), until such a time that Towny is updated to use the proper method of setting a players name (Set their displayName) it will not work with iChat.

    [Version 2.4.4]
    - Updated to new FileConfiguration class
    - Fixed bypass exploit for colors in messages
    - Multi-world support for variables.yml
    - Resolved an issue with /me not reloading player variables
    [Version 2.4.3]
    - Permissions overhaul. No longer require group.{name} node unless not using a permissions handler
    [Version 2.4.2]
    - Fixed issue with inheritance in Permissions
    - Implemented start of online time variable. Need output format.
    [Version 2.4.1]
    - Remove plugin-specific group referencing. All groups are now managed via group.* nodes,
    the exception being pure Permissions 2.x/3.x
    - Fixed /ichat reload not reloading variables.yml
    - Updated /me to use BroadcastMessage
    [Version 2.4.0-final]
    - Took out variable caching, there's no hook for PermissionChange.
    - Updated README to include info on group.* nodes
    [Version 2.4.0-beta]
    - Merged all branches into one
    - Supports Perms 2.x/3.x, SuperPerms, GroupManager
    - Added a more advanded API based on the mChat API
    - Massive thanks to MiracleM4n for code and concepts
    - All variables are now retrieved from variables.yml instead of Permissions
    - Removed censor code
    [Version 2.3.2-p3]
    - Set Permissions as a dependency in plugin.yml
    - Added Permissions 3 support to the -p3 jar
    [Version 2.3.1]
    - Added iChat.ichat.parseChat(Player, String, Format) API
    - Added hook for /me chat formatting using the "me-format" config option
    [Version 2.3.0]
    - Added external iChat.ichat.parseChat(Player, String) API
    [Version 2.2.3]
    - Added +displayname/+d for player.getDisplayName()
    [Version 2.2.2]
    - Updated to latest RB
    [Version 2.2.1]
    - Updated how Permissions is loaded
    [Version 2.2.0]
    - Added the ability to have an unlimited amount of variables in message-format
    - Changed versioning scheme
    [Version 2.11]
    - Now uses per-world permissions information
    [Version 2.10]
    - Allow admins to enable color on a permissions basis
    [Version 2.09]
    - Another small update to Permissions (Returned false when I should have returned true)
    [Version 2.08]
    - Pushes PacketCollisions PermVersion change. Fixes issues with 2.5.2
    [Version 2.07]
    - Added +time tag
    [Version 2.06]
    - Added +world tag
    [Version 2.05]
    - Ignore whether the plugin is GM, just treat everything as Permissions! Means you need FakePermissions.
    [Version 2.04]
    - Added the ability to use variables in the suffix and prefix (More customizeable messages)
    [Version 2.03]
    - Verify that all available variables aren't null before calling parse
    - Fixed crash caused by color code at end of message (Basic fix, added a space)
    [Version 2.02]
    - Fix for possible NPE
    [Version 2.01]
    - There's a bug in Permissions 2.1 in getPermissionString, switched to getUserPermissionString
    [Version 2.00]
    - Initial re-write of Niji's plugin.
    - Added Permissions 2.0/2.1, and GroupManager support.[/b]
    FFS2309, Lolmewn, wassilij and 12 others like this.
  2. Offline


    The only reason it was there was to carry-over the feature from Niji's iChat. To me it was completely pointless, and bare-bones, too many people were requesting expansion (As in make "ass" censor "ass", "as s", "a s s", etc, without censoring "assassin") and so I decided to just straight up remove it, I don't consider it to fall under the Chat Formatting moniker anyways.
  3. Offline


    Pex is not supported, but what if I use the Permissions 3 bridge from PEX? Will it work?
  4. Offline


    From three posts back:
    "As of this release native group names are no used as opposed to group.{name} nodes for Permissions, PermissionsBukkit, bPermissions and PermissionsEx."
    From the first post:
    "Supports Permissions (Both 2.0 and 2.1), and SuperPerms handlers (PermissionsBukkit, bPermissions, and PermissionsEx)."
    From the first post, yet again:
    As of iChat 2.4.3 native groups are supported in Permissions 2.x/3.x, PermissionsBukkit, bPermissions, and PermissionsEx.

    It's like people refuse to read..
  5. Offline


    Can someone post me an example for this? I tried to make it work but I just couldn't.
  6. Offline


    How do I get my groups colored if I'm using bpermissions?

    Seems I posted too soon. I figured it out. :)
  7. Offline


    Before 1317, my server would be [Admin] Name :

    now it's just the <Name>

    I'm using GM and tried changing the config to world but no use!!
  8. Offline


    I have Permissions 2.x and 1317 craftbukkit with IChat updated. Why doesnt it take the prefixes and stuff from the Permissions group file and use it as in game.
    I dont understand the variable thing

    [EDIT]: Permissions 3.x
  9. Offline


    Put this in variables.yml :
            name: Mod
            prefix: '[&1Ali3n&f]&1'
            suffix: ''
  10. Offline


    Now in game it says
    [[Ali3n] Mod] name:
    [FACTION [Ali3n] Mod ] name:
  11. Offline


    Well just change your format to:
    message-format: '+prefix+name&f: +message'
  12. Offline


    I recently upgraded to 2.4.1 and now titles defined in users.yml for permissions don't work. Any way to get these working again? Thanks, Sam

    EDIT: 2.4.3, sorry
  13. Offline


    Read the first post.
  14. Offline


    So iChat no longer works with users.yml in Permissions at all?
  15. Offline


    Read the first post.
    ZachBora likes this.
  16. Offline


    I am just confirming, can you please just give me an answer? I don't really get it. Yes / No is fine....
  17. Offline


    It works perfectly fine with Permissions. To know how, read the first post...
  18. Offline


    Loving the iChat, it's simple enough to use, but works well - I was wondering about adding in some sort of text wrapping feature and a scroll to view conversational history - But MOST of all, would you be able to add in a variable system for worlds? so you can nickname your worlds, and have them coloured? (As in for a multiverse, each world could have it's own colour, or the nether's colour could be changed ect.) DAM GOOD WORK MY FRIEND! (LOVING the Permsbukkit support)
  19. Offline


    Ty soo much and luv ur amaterasu plugin im a HUGE HUGE sasuke fan :D like Mega Sasuke fan
  20. Offline


    can u give me a layout of what ichat varible is suppost to look like ?
  21. Offline


    hey i have instlalled iChat and bPermissions and i have this config in iChat
    handle-me: true
    date-format: HH:mm:ss
    message-format: '+iname: +message'
    me-format: '+name +message'
    iname-format: '[+prefix+group&f]+name +message'

    But when a player types a message it doesnt show the message it only shows the name of the player and the group and the prefix but not the message please help me out!
  22. Offline


    I dont get where i put the line for the suffix for the bpermissions permission plugin. Can you please help? This is how its set up for Builder:

    default: Builder
  23. Offline


    You must set it in iChat variables.yml
  24. Offline


    Server log

    @smexhy There is zero need for big red text, I am reporting your post and I refuse to help you until you READ THE FIRST POST ALL THE WAY THROUGH
    Don't just skim it, READ IT

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jul 17, 2016
  25. Offline


    Ok every rank has a custom prefix, my builder rank which is default says [DEAFAULT] and I did not make it that, how do I make it say builder?
  26. Offline


    Read the first post.
    Server log.
    Config files.
  27. Offline


    How do I use the default per-world prefixes I made in PermissionsEx? I want the display to be [world] name: msg, but I don't want to use the actual world name (I want my vanilla and vanilla nether world to both say [vanilla]). Also, am I able to change the view of when players use /list? When I use /list, every name is white.

    Here is my permissionsEx setup for Admins:

            default: false
            build: true
            - '*'
                    prefix: '[Build] &4'
                    prefix: '[Spawn] &4'
                    prefix: '[VanillaLITE] &4'
                    prefix: '[VanillaLITE] &4'
                    prefix: '[Vanilla] &4'
                    prefix: '[Vanilla] &4'
    And here is my iChat config:
    handle-me: true
    date-format: HH:mm:ss
    message-format: '+iname: +message'
    me-format: '* +name +message'
    iname-format: '[+world] +prefix+displayname'
  28. Offline


    Drakia, I've got a small bug. I don't know why haven't seen it before.
    People without ichat.color permissions can just double the &&44 to color text.
    Example: &&55Test -> Test

    Just found how to fix it :
  29. Offline


  30. Offline


    @ZachBora You told me you would use Permissions 2.x, is it compatible with plugins like mcmmo, openinv and admincmd, because I often got a error message.
    Do you have any idea what6 to do if it isn't compatible, because the most plugins using Permissions 2.x/3.x.
  31. Offline


    iChat works with any permission plugin so just use the plugin you need.
Thread Status:
Not open for further replies.

Share This Page