Get 0.05 TON 💎Earlier Versions
| Name | Size | Uploaded | Game Version | Downloads | |
| LnXChat 0.1.1 release | 33.23 KB | Feb 13, 2014 | CB 1.7.2-R0.3 | 392 |  Download |
| LnXChat 0.1.0 release | 33.05 KB | Aug 16, 2012 | CB 1.3.1-R1.0 | 1,033 | Download |
Description
LineXChat
Features
- Chat formatting including permission-based color codes
- Easy to use private message system
- Playerlist formatting including /list and tab
- Join-, leave- and kick-message formatting
- Broadcast formatting including /say
- Fakequit and namechanging
- Autocomplete of players and groups
- Highly configurable
Those are all basic features – what makes this plugin special is the pm-system that allows for multiple targets with additional arguments. It was made because normal users almost never use channels so they are quite pointless. However, a big server should have the possibility for private messaging with more than one other user, so why not let the user create his own channels with a very simple command?
Commands & Permissions
| Command | Aliases | Permission | Description |
|---|---|---|---|
| All | lnxchat.command.all | ||
| /tell <Targets> [Message] | /pm, @ | lnxchat.command.tell | Creates a conversation with all targets and sends an optional message |
| /r [Message] | /reply, @ | Focuses on the last active conversation or sends an optional message | |
| /say <Message> | /br, /broadcast | lnxchat.command.broadcast | Broadcasts a message to all online players |
| /list | /who, /players | lnxchat.command.who | Lists all online players sorted by group |
| /list | /who, /players | lnxchat.command.adminwho | Lists all online players with their true name sorted by group |
| /ch | Lists all available channel commands | ||
| /ch list | lnxchat.command.list | Lists all own conversations | |
| /ch listall | lnxchat.command.listall | Lists all conversations | |
| /ch <ID> add <Player> | lnxchat.command.add | Adds a user to an own conversation | |
| /ch <ID> add <Player> | lnxchat.command.addall | Adds a user to a conversation | |
| /ch <ID> remove <Player> | /ch <ID> rem | lnxchat.command.remove | Removes a user from an own conversation |
| /ch <ID> remove <Player> | /ch <ID> rem | lnxchat.command.removeall | Removes a user from a conversation |
| /ch <ID> close | lnxchat.command.close | Closes a conversation | |
| /ch arguments | /ch args | lnxchat.command.arguments | Lists all available arguments |
| /ch reload | lnxchat.command.reload | Reloads the plugin | |
| Fake | lnxchat.fake.all | ||
| /fake | Lists all available fake commands | ||
| /fake quit | lnxchat.fake.quit | Sends a quit- or join-message | |
| /fake name [Name] | lnxchat.fake.name | Changes or resets the name for the next login | |
| Color | lnxchat.color.all | ||
| lnxchat.color.global | Allows using color codes in global chat | ||
| lnxchat.color.channel | Allows using color codes in conversations | ||
| lnxchat.color.name | Allows using color codes in fake names |
Arguments
| Argument | Permission | Description |
|---|---|---|
| All | lnxchat.argument.all | |
| -g | lnxchat.argument.group | Targets a group |
| -f | lnxchat.argument.force | Focuses the user or group on the channel |
| -s | lnxchat.argument.silent | Suppresses all info messages |
| -a | lnxchat.argument.anonym | Deactivates console logging |
Examples
The whole thing sounds very complicated but is very easy to use. Here are some examples.
| Message | Alternatives | Description |
|---|---|---|
| @ | /r | Toggles between global chat and the last active conversation |
| @Horst-f | /pm Horst-f | Opens a conversation with Horst and focuses him on it |
| @admin-g,Horst-s-f Hi | /tell admin-g,Horst-s-f Hi | Opens a conversation with the admin group and Horst, focuses him on it without telling him and sends them "Hi" |
| @ Hi | /r Hi | Sends "Hi" to the last active conversation without changing focus |
| /ch list | Lists conversations and their id | |
| @2-a Hi | /pm 2-a Hi | Sends "Hi" to conversation 2 and deactivates logging of it |
Configuration
The configuration is self-updating, color codes can be with all formats. They can also be set to false to leave the messages unchanged. If you need other variables than the given ones just tell me.
| Node | Description | Variables |
|---|---|---|
| chatformat | Format for global chat | {PREFIX}, {SUFFIX}, {NAME}, {MSG} |
| channelformat | Format for conversations with more than two users | All of the above and {ID} |
| pmformat | Format for conversations with two users | {SENDER}, {TARGET}, {MSG} |
| listformat | Format for tablist | {PREFIX}, {SUFFIX}, {NAME} |
| broadcastformat | Format for broadcasted messages | {NAME}, {MSG} |
| joinformat | Format for join messages | {PLAYERS}, {NAME} |
| leaveformat | Format for leave messages | All of the above |
| kickformat | Format for kick messages | All of the above |
| groupformat | Group format for /list | {LIST}, {GROUP}, {GROUPFLU}, {FLU}, {PREFIX}, {SUFFIX} |
| consolename | The name of the console when sending a private message | |
| saytobroadcast | Should the console say be displayed in broadcast-format? | |
| usetagapi | Should TagAPI be used for fake names? | |
| timeout | Minutes until removal of dead conversations after leave |
| Variables | Description |
|---|---|
| {NAME} (or {SENDER} for pms) | Name of the sender |
| {MSG} | Message to send |
| {PREFIX} | Group prefix and player prefix |
| {SUFFIX} | Group suffix and player suffix |
| {ID} | Conversation id or group name (if only that group is targeted) |
| {TARGET} | Name of the target |
| {PLAYERS} | Amount of online players |
| {LIST} | List of all players in that group |
| {GROUP} | Name of the group |
| {GROUPFLU} | Name of the group, first letter uppercase |
| {FLU} | First letter of the group name uppercase |
Upcoming
Ordered by priority. Suggestions are appreciated.
- Configurable messages for everything including languages (will need some guys to translate)
- -r Argument for regions (Residence, WorldGuard, Regios, LineXRegions)
- -gu Argument for guilds (Uhm… good guild plugins?)
- -t Argument for pvp (PvPArena, others?)
More documentationNope, deal with it
Changelog
16.08.2012
- Initial release
Add a comment