The metascripts, being a toolbox of various functionalities spread over a handful of different scripts, sometimes don't get the proper announcement of new features or capabilities on any individual basis. Since they are intended to work together (with themselves and with other scripts), I decided to roll all of the updates into a single message. With that said, let's get to what you can do with them, now:

SelectManager Criteria Selection

SelectManager recently got the ability to use wildcards (or even full regular expressions) as a way of identifying sets of tokens. For example,  the following formation would choose all tokens that began with the pattern "GoblinArmy" followed by any number of characters:

{&select GoblinArmy*}

Further examples will use this notation, so if you need a refresher, read this post. 

Available Criteria

With this update, the tokens that are selected by a {&select} formation can be evaluated against a series of user-defined tests. The tests can require a condition (+), or conversely exclude based on that condition (-). The available conditions include:

Using Criteria

To use criteria, include them in a {&select} formation in addition to selectors. The criteria will not work without selectors; the selectors gather the tokens that the criteria will then test.

{&select GoblinArmy*, +bar1>0}

Multiple criteria can be included. To be selected, an object must pass all criteria evaluation (think of them as logical AND operators):

{&select GerbilArmy*, +bar1>0, +layer in [objects, gmlayer]}

Multiple selectors can be included in the formation, and the entire set will be evaluated against all criteria included in the selection.

{&select GerbilArmy*, GuineaPigBrigade*, Ralph, +@hp > 10, -Trapped}

Criteria only affect the selectors in the same {&select} or {&inject} formation. Therefore, to arrive at a logical OR evaluation, you can utilize zero or one {&select} formation, followed by as many {&inject} formations as you wish.

{&select *, +npc, +bar1 > 0} ... {&inject *, +pt, +MindControl}

That would select all npc tokens with a bar1 value over 0, as well as any player token marked with the status marker "MindControl".

Available Comparisons

For those evaluations that are testing the value of the given criteria, the following comparisons are available:

equals                 =     
does not equal         !=
greater than           >
less than              <
greater than or equal  >=
less than or equal     <=
includes               ~
does not include       !~
in                     in [value1, value2, ...valuen]

Fetch gets Deck, Text, and Path Properties

Fetch retrieves properties from game objects (tokens, pages, markers, characters, etc.). With the pending update, it can now retrieve text properties, path properties, and it will now expand the properties it can retrieve for a graphic that is a card. 

Cards

For cards, Fetch can now retrieve any of the following:

cardname
deckid
deckname

These will work with any Fetch formation that returns a card:

@(selected.deckname)
@(-M1234567890abcdef.deckid)

Text Objects

Since text objects do not have a "name" property, the only way to select them is by using "selected" or the id of the object:

@(selected.font_family)
@(-M1234567890abcdef.text)

The available text object properties you can return include:

Path Objects

Similar to text objects, paths do not have a "name" property allowing easy desigation. Therefore, the only way to select them is by using "selected" or the id of the object:

@(selected.left)
@(-M1234567890abcdef.top)

The available path object properties you can return include:

New Script Package in 1-Click: MetaScriptToolbox

As mentioned, the metascripts are various scripts which bring added functionality (or backfill functional gaps) to a Roll20 game. They are developed, built, stored, and delivered as individual scripts since they have discrete functions: Fetch retrieves game items, APILogic provides conditional logic to a command line, MathOps allows for complex math operations, SelectManager allows for "virtual" selection of tokens, etc.

While maintaining the scripts this way gives you the maximum flexibility over what you would install to your game, situations sometimes arise where you might need one of the metascripts that you don't happen to have installed. Many solutions I offer on the forums might require 4 or 5 of the metascripts to make them work as described.

For that reason (and at the suggestion of The Aaron), I have put together a new script package and submitted it to the 1-click installer: MetaScriptToolbox.

The MetaScriptToolbox packages up all of the metascripts as dependencies from the 1-click, meaning that if you get the MetaScriptToolbox, you will automatically get all of the other scripts, too, as well as all of the libraries and scripts that the metascripts might rely on (like libTokenMarkers or libInline). There is no command-line interaction with the Toolbox; it simply exists as a way to easily get all of the metascripts at once.

Getting the MetaScriptToolbox

Game owners can get the MetaScriptToolbox (once it passes through the script merge this week), by going to the script panel for their game and picking it from the dropdown on the Mod Library tab.

What Is Included

Primary dependencies (the metascripts) include:

• APILogic
• Fetch
• MathOps
• Muler
• Plugger
• SelectManager
• ZeroFrame

Future Updates

Since you'd be getting these scripts from the 1-click installer, you will always have the latest updates for any of them. One limitation of the 1-click installer is that dependent scripts are only installed once -- when the reliant script (in this case, the MetaScriptToolbox) is installed. After that, all of the dependent scripts will be updated via any change in the 1-click library. However, if I later added another script to the Toolbox, it would not automatically install. For that reason, I have included a check inside the MetaScriptToolbox that tests whether all of the scripts it would expect to find (that is, all of the metascripts) exist in the game. If it finds any missing, it will prompt you with a message and ask you to install the missing mod script from the 1-click library yourself.

Cool !!! but does that mean that we have to uninstall all the metas nefore installing the Metatoolbox ? shall we uninstall first and then install the toolbox or install the toolbox and then uninstall ??? :)

Ha! Thank goodness, no! You'd only have to uninstall metascripts you had manually installed. If you already had a metascript from the 1-click, that should be fine. The Toolbox will just want to make sure it's installed,, and if it sees the script is present from a manual install, it won't update it to the one click version.

ah ok cool and clever hehe. 

Update (pre-merge, no version increment)

SelectManager now has a new criteria it can test: the currentSide of a token. As an example of how you could use this criteria, you could select all of your Werewolves that are not yet transformed:

{&select Werewolf*, +side=0}

Be aware that the current side property is 0-based, and that standard tokens (not multi-sided) have a currentSide value of 0.

Update

These new features were a part of the merge this week, so they are all now available from the 1-click library.

That needs to be a forum tag for Mods/Scripts.