EmoTracker v2.0 Release Notes

August 24, 2018

One year after it’s initial closed alpha releases, EmoTracker has reached version 2.0! As always, your tracker will automatically prompt you to install it the next time you start it, or you can find “Check For Updates” in the gear menu!

Read on for the details on what’s included!

For Users

Brand New Package Manager

The highlight of v2.0 has to be the upgraded package manager. The first thing you’re likely to notice is that packages are now sorted and grouped by game, with attractive new banner art!

package manager screenshot

More Helpful Than Ever

Pretty art is certainly not all you have to look forward to though! This new package manager has a few new features you might be interested in…

See that search bar at the top? Start typing, and your package list will be filtered in real time by game, pack name, author and more!

Badges

Packs can now be accompanied by badges that help you to identify which packs offer what you’re looking for. Pack developers can now mark their packs with the following badges.

Indicates that this pack includes maps
Indicates that this pack includes support for pinned locations
Indicates that this pack has been optimized for ChatHUD


You will also occasionally see these special badges!

This is an Official EmoTracker Pack, developed or distributed by the developers
This is a Featured Pack - the developers and/or the community have decided that this pack is worth highlighting!


Reorganized Gear Menu

Your installed packages are now grouped by game, so it’s easier than ever to find the package you’re looking for.

Some existing options have been reorganized into new folders. You’ll also find some brand new options hiding in there…

Always On Top
Gear Menu > Layout > Always On Top

Open the Broadcast View
Gear Menu > Applcation > Broadcast View

Custom Image Support For !hud rain

For ChatHUD users, you can now add your own custom images for the !hud rain command. Images must be square, and must be save in PNG format with the .png extension.

To use them, simply place them in Documents\EmoTracker\extensions\twitch_chat_hud\images. You will use the filename (without extension) as the parameter to !hud rain.

Example

If I add the file Documents\EmoTracker\extensions\twitch_chat_hud\images\emos.png, then I can trigger it as a rain effect with !hud rain emos.

There is no limit to the number of images that can be added.


For Developers/Customizers

A number of requested features have been added for developers. As always, the developer forum is the place for detailed questions/discussions.

Argument Support For Lua Code Providers

You can now pass parameters to Lua code providers. All parameters are parsed/passed as strings, and must be separated by | characters.

Example

Lua Code
function testExpression(a, b)
  ...
end
In Access Rules
"access_rules": [ "$testExpression|22|This is a test" ],

Argument Support For Image Filters

You can now pass parameters to image filters. Parameters must be separated by | characters.

Two new image filters have been added which accept parameters.

Brightness

Brightness can be used as a more flexible replacement to the dim set of filters. It takes one parameter, which is a floating point brightness factor. 1.0 means brightness is left unchanged.

Example

Darken By 50%

brightness|0.5

Brighten By 25%

brightness|1.25

Overlay

Overlay can be used to composite multiple images into a single image. It takes one parameter, which is a pack-relative image path.

Example

overlay|images/overlay.png

Lua Console

You can now view debug output from Lua, including the output of print(...) by using the Lua Console.

Open it via Gear Menu > Advanced > Developer > Lua Console.

Lua Code Providers Can Now Gate Accessibility

Lua code providers can now return an additional value in order to gate the maximum accessibility allowed for the location/section being processed.

In order to enable this, simply return the maximum accessibility as the second return value, after your provided count. This value is only used to restrict the maximum possible accessibility - it does not specifically set the accessibility to that level.

Example

return count, AccessibilityLevel.SequenceBreak

Valid accessibility levels include None, Partial, Inspect, SequenceBreak, and Normal (the default).

Sections Now Support visibility_rules

Sections can now optionally specify visibility rules. If at least one of those rules are not satisfied, the section will not be displayed in e.g. pinned views of that location.

Example

"sections": [
  {
    "name": "By The Door",
    "visibility_rules": [ "sword" ],
    "item_count": 1
  }
]