• Now only works on 1.17 and above
• added regex-based permissions system

Permissions:
Example permissions file will be created if absent.
Users in the admins list (old system) bypass all restrictions, so be careful.
How it works:
For each group the user is in, it firstly checks if the command passes any of 'allow' regexes, and if it does - any of 'deny' regexes.
If at least one group the user is in allows the command execution, the command will be executed.

Now by-default the output's color codes are stripped.
You can revert to older behaivor (if you for some magical reason need the color codes) by changing strip-colors config value to false.

Changes:

• made compatible with latest versions
• fixed small bug noone ever reported
• added bot.need-command config entry, which defines if only /exec commands are executed, or if anything bot recieves should be treated like a command
• now plugin doesnt depend on anything, as it automatically downloads missing dependencies

This update was made possible by WhiTe_Yak

Fixed console output not always displaying on linux
Fixed incorrect display of some commands (such as tps)

Changes:

• Now this plugin depends on Telegram Bots API
• Fixed possible crash
  • Added a message to notify user if the command is already being processed
• Some code cleanup

Fixed minor bug + added support for 1.13.* and 1.14.* builds

So, uh, i did a complete rework of the plugin, and removed all those secondary control functions.
Now all it does is passes your commands to the server and returns the result back.
And it supports proxies now.
It also no longer depends on TelegramBotsAPI.

• now you can add your bot to groups, and it should work just fine
  • to let bot send notifications to groups, you need to add group's id to the notifications config. to get it, add bot to the group and use `/getid` command
• now no dependencies, but increased weight
• a lot of bugfixes
  • a lot of new bugs possibly

Here is a chance i forgot to mention something, i hope i didn't

Now you can grant bounded access to your console, for example, you can create mod group and grant it such commands as
mute, kick, ban, unban, etc...

but, specifying the command kick, you also give permission for command kickall and so on;
To avoid possible abuse from possibly incompetent staff member there also is blocked section.
There you put exclusions from section commands. (if you do not want to restrict any acces, you can put there any command which can't be executed via console, such as some world edit commands)

In current version only unic user_ids can be specified in ids section, in upcoming updates it will be expanded to accept @usernames - stay tuned)

A shame, i was unable to edit bStats the way i wanted to without breaking other plugin's stats collection.

So, now you have two options:

• send all data mentioned here https://bstats.org/getting-started
  • and some custom usage data from my plugin, if you enable it in my plugin's configs

• Or, you can completely disable all stats in 'bStats/config.yml'

all the stats are public and anonymous - you can have a look at them
here: https://bstats.org/plugin/bukkit/TGConsole

A lot of minor fixes + menu fix

What data do we collect:
* ServerUUID(unic number to separate servers from each other)
* Bukkit version
* Java version
* OS name
* Plugin version
* Server location (country)
* configurable menu usage (is it enabled or disabled)
* notifications usage (is it enabled or disabled)

You can see those here

Now you can reload this plugin with command /tgconsole reload (permission: tgconsole.reload) (alias: /tgc reload)

Now you can summon menu with commands specified in config files!

to show menu use /show or /showmenu command,
to hide menu use /hide or /hidemenu command.
Also:

• more bugfixes
• more localizations

Here is chance new feachure contain bugs, if you meet them - contact me!

Now you can get notifications from server about selected events
Currently available:

• player send command
• player send chat message
• player died
• player joined the server
• player left the server

Now you can send multiple commands!
You must separate them by lines
Usage:
/multiple
delay_in_seconds:command
another_delay_in_seconds:another command
etc...

The 'delay' part is the time between command execution and bot output.
Current max and min are 30 and 4 seconds
Example:

- More info about errors while in debug mode
- Small config changes: now 'adminids' is 'admins'
- Now you can use both - numeric userids and @usernames to grant acces
for your admins
- Next update: more than one command at time with configurable delay between each command

1. I fixed a lot and cleaned the code
2. Now you can look at source code

Reworked debug and logging

Changed code a bit, so the crash possibility decreased

Now you can set custom messanges! Not very much to change yet, but some may find it useful

Small bugfixes and optimisations.

now command '/start' isn't being passed to server

Now all looks great:

I see some troubles getting output from Essentials and other plugins. working on fixes. The problem is: you see the command output, but it looks like...
I will put the fix to it soon.

The bot still can send messanges, but the way he outputs the result may differ