LibSequence

New · Integrity-check that all placeholders are resolved · Improved command responses (messages) · command responses (messages) now checks for 5-digit and 3-digit locale (e.g. "de_de" and if not found "de") · command responses have a new locale "default" to overwrite the hardcoded english messages · check_world and include_world · Maximal number of currently running sequences is now a config option Notes · If you use player-related placeholders, please take care to limit the initiator to player ("check_sendertype: player") because some PlaceholderAPI plugins throw a java-exception if player is null. · The plugin config loader cannot detect duplicate entries, so the LibSequence Syntax Inspector cannot warn about it. · Please delete your old config.yml to get access to the new configuration options.

New · Directory for publishing sequences and starting sequences from other plugins · ControlAPI is now designed as Exception-free · Command is moving from "/libsequence" to "/sequene" · Sharpened the Inverse-Operator on some include-rules API Changes · callback has changed to respect the new features Please delete your old config.yml to get access to the new configuration options.

New · Using Exceptions instead of proprietary Result-Objects · New SyntaxValidator to warn about unknown and missing attributes · New action: none (do nothing) Changes · New functions in action-interface (needed for syntax check) · Every action gives a list of "optional" and a list for "required" attributes the syntax validator can check for Notes · The plugin config loader cannot detect duplicate entries, so the LibSequence Syntax Validator cannot warn about it.

New · IncludeManager (simple playerlist-generation for "notify" and "title") · Operators ("-" for exclude, "!" for inverse) · ConditionManager for a consistent way to convert a String to boolean (used in includes and checks) Please delete your old config.yml to get access to the new configuration options.

New Features · CheckManager (you can add custom checks) · Private Sequencers are now disposable (please read documentation) · Cascaded Results (to get better error messages)

New Features · New action: check · Localized Messages for "notify" and "title" · Option to enable/disable debug printout in Callback · Actions can now access the plugin where the sequence was started from · Out-of-the-box actions now use the given plugin to call Bukkit functions instead of the LibSequence-plugin · Introducing Orchestrator to get a bit more control about the Managers (internal modules of LibSequence) · Integration manager for links to other plugins (WorldGuard, PlaceholderAPI etc.) Changes · Attribute "permission" was renamed to "include_permission" (actions "notify" and "title") · Config "addSection" and "reloadSction" was renamed to "loadSection "(SequencerAPI) Please delete the plugin.yml so LibSequence can rollout a new default configuration containing an improved demo-sequence.

New The Libsequence can now resolve chained interactions (e.g. Player => Button => CommandBlock => Sequence) to detect the "real" initiator. Changes The %USER% Placeholder was renamed to %NAME%. The Placeholders now contain the "real" initiator if a chained interaction was detected and resolved. API Changed "Integer" => "integer" and "Boolean => boolean" in some functions. Some function marked as "depecated" in the last release are finally removed. Please delete the plugin.yml so LibSequence can rollout a new default configuration containing an improved demo-sequence.

Fix: · Reload command New Features: · Authorization for Actions · Default actions can be used in private sequences (register manually) · New Out-of-the-box Actions · Info (send message to server console) · Notify (send message to a group of players) · Title (send title to players) · Introducing runOptions · Can limit Sequence to only run once at a time (singleton) · Manage authorization keys for actions · Local Placeholders · PlaceholderAPI integration Changes: · Moved initiator (CommandSender) to runOptions · API change for actions to reflect the new authorization feature

In Version 1.0, the "command" action always issued the command as ConsoleSender. Now you have the option to select, that the command should be executed in the context of the initiator (the player or command block who has started the sequence). Attention: The API to start a sequence has changed to add the CommandSender object.