Repository navigation
Viewer values, chat games, your values and channel points rewards - #77
Merged
Merged
Conversation
…l points rewards
What a chat economy needs, as general steps:
- Viewer value step: a number per viewer (give, take, spend, set), read as
{viewer.x}, {target.x}, .rank and {top.x}; can pay recent chatters or a
named viewer. Kept in the data file.
- Maths step, a "% chance" check, Wait for chat, and blocks (a trigger
other triggers run by name, which may run itself).
- Remember a value can keep text between runs ({saved.x}); Stop can leave
a run out of the history.
- Chat commands can answer a viewer who is too early ({cooldown_left});
cooldowns of 10 minutes or more survive a restart.
- Your values: named settings read as {my.x} anywhere, edited on one
screen with what viewers hold, and carried by recipes. Counting words
take them as $my.x.
- Channel points: make, edit, switch and delete rewards from a redeem
trigger, tick which rewards start it, and a step that switches one.
Logins now ask for channel:manage:redemptions as well.
- Chat message triggers can match whole words, with live examples and a
"Try a message" box.
- Test runs start from given counter and viewer values and save nothing.
- Twitch events carry user_login; chat commands carry target_login.
Counters are now read live during a run, not as an earlier step left
them. The builder ignores a click on a step still fading out after a
switch of trigger.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
Everything a chat economy needs, as general steps anyone can build with. No recipe or game is bundled with the app.
{viewer.x},{target.x},.rankand{top.x}. It can pay everyone who chatted lately, or a viewer the step names.{saved.x}); Stop can leave a run out of the history.{cooldown_left}), and cooldowns of 10 minutes or more survive a restart.{my.x}anywhere, edited on one screen (sliders for chances, one-per-line lists), with a tab for what viewers hold. Recipes carry the values they use.Behaviour changes
{counter.name}is read as it is at that moment, not as an earlier step of the same run left it.channel:manage:redemptions. Existing logins keep hearing redemptions; managing rewards asks for a new login.Testing