Bukkit

Version 2.5

New YAML validator validates config.yml before loading.  If a syntax error is
found the details of the error are concisely displayed, indicating the problem,
including the line and column.  Further, checking the validity of config.yml before
loading or reloading allows ShellReact to abort the reload, leaving the existing
configuration in place.  Prior to this, ShellReact was left unconfigured when
trying to load an invalid config.yml until the error was fixed and ShellReact
reloaded.

New auto reload capability, defaults to off.  If turned on, ShellReact will
automatically reload 'config.yml' if it is changed.  This compliments the new
YAML pre-scan above making it safe to use.

Each individual setting has a reasonable default value, and may now be omitted
if not changed or used.  An invalid setting will revert to the default value.

New string directive "_ " that is stripped at runtime.  Makes it possible to
define complex strings starting with a format character "&" without having to
deal with balanced quotes.  It also facilitates the use of multi-line string
definitions.  It serves as a line anchor on multiple lines, preserving white
space formatting.

New directive "_nl" (new-line) in output strings makes multi-line output
possible.

New Platform choice 'Custom' allows choice of shell for shell commands.  Also
makes it possible to vary the OS shell between shell definitions.

'Input_cmd' has been changed to 'Cmd_name' to better reflect the role named commands
now play in ShellReact.  This also makes the yaml file easier to read.  This is
the only setting name that has changed in ShellReact, and hopefully the last.  Named
commands are not just commands entered by the user/player at the keyboard anymore.
They also may be invoked, like subroutines from any other ShellReact section.  This
makes it possible to consolidate routines.  It is fully compatible with the previous
'Input_cmd' usage.  It may simply be renamed in the editor.

'Cmd_name' may now include parameters as part of the command input string
definition.  This makes it possible to have more than one definition for a
single root command.  ie: 'rules 1' and 'rules 2' as 'Cmd_name' definitions
may share the same root command, but are treated as separate command definitions
by ShellReact.  It is now possible to add more parameter options to existing
command families sharing the same root command.  Further, the specific root and
parameter definition, when overridden by ShellReact, applies only to that
particular combination.  Other combinations, used by other plugins will not
be affected.  White spacing variations from user input as well as input command
definitions have been anticipated, and dealt with.  For example, if a player
uses a different number of spaces between parameters than the input definition
it won't matter.

Memory footprint optimized by loading only active triggers and sequences.  All memory
arrays are reduced or expanded, as needed, every time ShellReact is reloaded.

Active items now listed when reloading ShellReact.

New directive for the 'Default_params' setting, '_runtime'.  Use to indicate that
a command definition needs parameters, but you don't want to set a default.

New command type 'Sreact_cmd' to compliment the existing 'Console_cmd', 'Player_cmd'
and 'Shell_cmd'.  Use it to invoke, by name, any command in the 'Commands' section.

New section named 'File_triggers'.  The ShellReact directory is monitored for files
defined with the 'File_name' setting.  If found, the file is deleted and the defined
sequences are invoked.  This makes the event handling bidirectional.  Not only can
ShellReact respond to internal Bukkit events, it can be signaled from the host OS
simply using the file system.

Version 2.0

Multi platform support; Windows and Linux
'Platform' identifier in 'Settings' may be set to 'Windows', 'Linux' or 'Auto'
Defaults to 'Auto'

Platform friendly audio alert ie:
The format is:  beep.[count].[delay_ms]

Fixed bug using 'debug' to monitor shell output.  Output wasn't being shown.

New 'Quiet' setting eliminates all informational messages except 'Message_out'
custom messages, and error messages.

Use standard '&x' formatting for custom messages both console and player.
Variables are expanded for custom messages.

Version 1.85

More work on yaml docs and examples.

Tweaked player and console messages, color and formatting.

Dropped the optional use of single quotes to define yaml values and numbered sets.
Decided that the potential for problems outweighed any clarity benefits such as
punctuating the word 'don't' inside single quotes - will cause a yaml exception.

Character case retained on shell, console and player command definitions.
Variables are now, formally, case sensitive.  Allows retention of character case on
defined, outgoing commands. Often important.  ie: log entry formatting, or case
sensitive switches.

'Message_out' setting already used in the 'Commands' section, added to 'Console_mon'
and the server triggers.

Command override status, as player, checked and invoked independently of player
permissions to insure ShellReact is able to cancel a command that might
unintentionally be processed by the server or other plugins.  I guess that should
be called a bug fixed.

Version 1.8

New command setting 'Default_params' facilitates smart commands that may be
overridden at runtime.

Command interpreter changed to facilitate the use of multiple forward slashes
as an Input_cmd definition.  This makes possible command definitions that start
with two or more forward slashes such as those in WorldEdit.

Player commands always assume the first forward slash.  Any slashes beyond
that are treated as part of the command definition.

New Command setting 'Message_out' used to define a custom message for the command.

General reorganizing of player and console messages emphasizing standard formating
and clarity.

Examples added to the bottom of this document ReadMe.txt'

Version 1.7

ShellReact will determine if any of it's individual sections are not being
used and flag it accordingly to prevent any unnecessary processing.  This is
done at server start up, and any time ShellReact is re-loaded.

%location% variable format changed from 'world,x,y,z' to
'world x y z' (no quotes) to better comply with existing standards and
to prevent confusion with multiple command capability in ShellReact
that uses commas to separate command sequences.

Location variable is further broken down into details:
%world% %X% %Y% %Z%

New variable %player_ip%

Commands, search strings, and variable names are not case sensitive.
The only case sensitivity in ShellReact are the yaml names or identifiers
in config.yml

Improved deployment of available variables.  While it is true that console and shell
commands are not associated with a player or location, ShellReact makes it possible
for live players to invoke these server type commands.  When any type of a command
can be associated with a player, the the player and location variables will reconcile to the
player associated with the ShellReact, defined setting.  Commands entered from the console
will have a %player% = 'Console' and %location% = 'world 0 0 0' without the quotes.

General code clean up emphasizing variable management.

Shortened the docs - too much commentary :-)

No existing settings changed or added to config.yml in documentation only.
Fully compatible with version 1.6, aside from new %locaton% variable format (see above)

Version 1.6

Fixed bugs:
    Runtime parameters duplicated, forgot to remove old parameter handler.

Added Player_cmd to support interactive commands.

Improved config.yml documentation.

Version 1.5

Fixed bugs:
    Active flag not being honored for console commands.
    Runtime parameters added even when directed not to.

Include_params replaced with %parameters% variable.  This
adds flexibility and eliminates the need for the boolean
flag.

Command /shellreact added.  Used to reload config.yml without
restarting the server.  ShellReact never modifies config.yml
The file is always the master.

Permission node shellreact.admin added.

Console_cmd now accepts multiple commands separated by commas.

New Console monitor section.  Define specific strings to look
for in consol output and specify response.

This is a pretty big update so it might be best to rename your old 'config.yml' and let ShellReact build a new one.  Then cut and paste back into the new one.  There are many new features, all documented in the new 'config.yml

If you don't feel like doing that your existing 'config.yml' should be fine with one exception.  'Input_cmd' has been renamed to  'Cmd_name' Just rename them and you should be good to go.  I hated to change a setting name, but it was necessary. see above.

Cheers!