Dorothy's UltraApp

Short Description:

App for Ticket Show, Single Goal, Progressive Goals (Multi-goal), Goal Counter, Tip Sequence, and Tip Jar

Full Description

Current Version 1.4 (3/25/19). Note: The Change Log of fixes and enhancements in each release is at the bottom of the page.

Summary

The purpose of this "Ultra" App is to provide many of the most commonly used app features on Chaturbate in one place, specifically goal and ticket shows, and give the broadcasters and trusted moderators the ability to change many of the settings being used on-the-fly, without restarting the app. This includes the ability to add and edit goals and change settings. It is recommended to start this at the beginning of each show and not reset it unless truly necessary, as you will lose the data accumulated in the current session.
This app does not contain many common bot-driven features such as leaderboard, chat control, timers, etc, as it is expected you will be using an ultrabot like Dorothy's Ultra Fembot (or Dorothy's Easy Fembot for shorter setup) to perform those functions.
Another reason I started doing my own development was to create apps and bots that do not have developer backdoors giving people you don't know access to your show, in particular hidden cam shows. As you can see, the source for my apps an bots will always be visible, I don't encode it or try to hide the source like many others do, so you can see that no one, including me, is granted access to anything without your permission.

As you use the app, one thing to keep in mind is that the changes you make using the commands within a show are not permanently updated to the start page - you have to make those changes there for them to be saved. This includes things like goal changes, changes to the outstanding ticket list, etc.
I recommend keeping all of these lists in a separate notepad document so you can update them as you go, and copy and paste them into the boxes on the setup page when you start a show, especially in case something happens and the configuaration page gets reset.

The App features are:

1. UltraApp Ticket Show - Sell tickets to a private show, similar to CrazyTicket. With Dorothy's Fembot alongside you can also do pre-sales.


2. Single / Progressive Goals - Similar to the Single Goal or Tip Multi-Goal apps, setup one or more goals for people to tip toward.


3. Goal Counter - Use smaller incremental goals with prizes at intermediate goal counts.


4. Tip Sequence Goals - People tip in an ascending or descending sequence with prizes at intermediate sequence numbers.


5. Tip Jar - Tip to a goal, and once the goal is reached, perform the prize until the tip jar runs out. Multiple goals with ability to recycle each one. Can speed up or slow down the drain rate on the tip jar.

Note that when the UltraApp is started, you'll set the 'current' app to be one of the 5 above. Most commonly, users will start with one of the goals to help drive the show. Goals help keep things moving towards an end goal, which could be done in public or sometimes it may make sense to do a hidden ticket show if there are enough people in the room (recommend at least 1500 total viewers) and tipping has slowed down or there are privacy concerns. If that is the plan, you can then easily switch from the goal show to the ticket show.
If there are errors when attempting to start the current app (usually settings missing or not entered correctly - you'll see an error message in yellow), no feature is started and the draw panel (box below the video window) will show that no app is running. You can either re-launch the bot and update the settings, or manually update using the commands below and then use the /chgapp command to initiate the feature you want to use. It is also possible to turn off the apps and just track total tips if you change the current app to 'none'.
In general, with all of the goal app features, it's important to enter the goals in the slots 1 thru 10 (or 20) in the order they will be performed during the show. You can either specify a final goal in the room description, or set it as the last goal defined in the settings.
I've also added the ability to control your background and text color in the draw panel, if you'd like a personalized background, just contact me, and if you'd like to make it yourself, send me a 270 x 69 pixel image to use as the background.

All Bots and Apps by chelsea
Link for Easy Fembot: Dorothy's Easy Fembot - Simpler ultrabot for newer cammers with minimal config, most features related to chat control.
Link for Ultra Fembot: Dorothy's Ultra Fembot - Messaging for mods and broadcasters, Private Messages to other users, Silence Level and Graphic Level, Leaderboard, Nice List, Tip Count next to name, Silence individual users, Silence individual users without notification (ninja), Tip Menu 1 & 2, Positions Tip Menu, Token Poll, VIP List, External FanClub List, Blocked word list, Additional Notifiers (up to 5 rotating), User Group icons next to name (mods, CB fan club, external fan club, VIP list), Color control of most messaging, Ticket prep function (disable regular tip menu, enable positions menu and token poll), Lush/Nora/Domi Menu, Media Contact List, Ticket show pre-sales, Hidden Ticket Show, Dice Game, Gray Chat Time Lock, Raffle, Price Checker - ensure same price not used across features, All time tippers, Assign nicknames
Link for UltraApp: Dorothy's UltraApp - This app...
Link for Dice game: Dorothy's Dice Game - Roll 2 6-sided dice to win prizes, plus a rare special roll of '13'. Note this same version of the game is also already built in to the Ultra Fembot.
Link for Ticket Show App: Dorothy's Ticket Show - Same as the ticket show portion of this App - Sell tickets and then lock the room for a private show, similar to crazyticket but with more features.
Link for Tip Goals App: Dorothy's Tip Goals - Run a goal show with either a single goal or multiple progressive goals. Same as the goal feature of the Ultra App in its own separate App. Like the UltraApp, the Tip Goals App also has customizable draw panel backgrounds.
Link for Ultra Gamebot: Dorothy's Ultra Gamebot - Includes Dice, Wheelspin, Keno, War! (High Card), Russian Roulette, Press Your Luck, all with a common prize list that can be used across all the games so you don't have to keep setting up prizes in different bots

Please let me know if you find any issues or have recommendations for improvement, you can usually find me on the couples rooms on the site, or on twitter @thechelsea2950.

Commands

Most of these are available for moderators and broadcasters only, with some exceptions. Note that you can also type "/help" within the chat to see the list of commands as well.

A. General commands across most or all App features

The primary command noted below is the /chgapp command, which lets you switch between each of the 5 apps that are built into the UltraApp so far. You can switch at any time, but you if you change in the middle of a goal, you cancel any open goals in that app when you do.
Total tipping and time online stats are also kept and can be accessed anytime. There is also a parameter in the 'General Settings' section to turn on/off the display of the total tips accumulated so far for each app on the draw panel (you can still see them in the /stats info).

1. /chgapp [newapp]: switch from one app to another, or turn off the current app. The values used for [newapp] are 'goals', 'goalcount', 'sequence', 'tipjar', and 'ticket' to go along with the 5 types of shows, or the value of 'none' to turn off the current app feature and not start a new one immediately.


2. /stats : Display a listing of your time online (with the app running), total tips, and tips broken down by app.


3. /skip and /next: These are available in most of the apps, so they are are listed within each section with specifics of what they do for that app. In all of the apps except the ticket show, use the /skip function to bypass the rest of the current goal and start the next goal fresh. Note it can be used with the tip jar, but not while the tip jar is actually draining. With the sequence app, it just advances to the next sequence.


4. /addtips [tokens]: Within the goal apps (Progressive Goal, Goal Count, and Tip Jar), this can be used to simulate users having tipped and advance the token count within a goal. Indicate the number of tokens you are adding as the [tokens] parameter, and note the value can be negative. You can add more than the current goal, but you cannot subtract less than has been tipped in the current goal.


5. /listgoals (also /lg): List the current setup of the goals for the App feature that is active.


6. /chgpanelbg [imagename]: Change the background of the drawpanel to one of the valid images. Images are updated regularly, so you can see the current list by entering this command with no parameter and the error message will show the current valid choices. Note that you can also see the images by going to the 'Source Code' tab for the app and clicking the link for 'App Images'.


7. /chgpaneltext [newcolor]: Change the color of the text in the drawpanel to either a hex code (#0000ff) or the exact text of one of the color choices from the menu ('Dark Green', 'Dark Red', etc). You can lookup hex codes for any color on a site such as Color-hexa: https://www.colorhexa.com/

B. Single / Progressive Goals

For the progressive goal show, you can setup a single goal, or multiple goals that will be progressed through in sequence as users tip. There is a configuration flag that defines if the app automatically moves from one goal to the next, or requires the use of the /next command to advance after the goal is met. If set to automatic advance, tips that exceed the goal will carry over to the next goal. If set to advance by command, the tips do not roll over.
By default, the room subject will show the current goal amount and description, the next goal description and a configurable block of text that you can use to describe what happens at the last goal or after the goals, or even just put searchable hashtags to draw more people into the show. This room subject text can be edited using the "/setgoaltext" command as noted below.
Any changes you make are not stored permanently, they are only stored within the current session. They will be kept if you switch between app features, but not if you deactivate the app.
Also, you must keep the goals in sequence, and cannot add an entry that would leave an empty level. For example, if goal levels 1-3 are filled in, you can't add a level 5, you must add a level 4 first.

1. /restartgoal : If you'd like to repeat a goal (common if you have a single goal you're recycling), you can use this command at any time to reset the tip count on the current goal to 0 (even if already complete)


2. /setgoal1, /setgoal2, /setgoal3...(thru /setgoal20) [goal] [description]: These are the commands that let you edit the goals for your show. Both the [goal] and [description] parameters must be entered every time and will update both values. Note this is also only a temporary change made within the session, it does not permanently update the launch page config.
   The 1-20 designation as part of the command identifies which entry you are modifying.
   The [goal] parameter is the new value you are setting for the goal amount. Even if you are not changing the goal (only changing the description, you must still enter the existing value for the goal.
   The [description] Parameter is the new value you are setting for the goal description. Even if you are not changing the description (only changing the goal amount), you must still enter the existing value for the description.
   An example of the syntax for this command would be "/setgoal4 400 Blow job", which would set goal 4 to be a Blow Job once you reach 400 tokens.
   Note that you can't make updates to the current goal or past goal, only future goals.


3. /rmvgoal [level]: Remove the goal entry for goal level of [level] (amount and description are both removed). Note this is also only a temporary change made within the session, it does not permanently update the launch page config.


4. /setgoaltext [newsubject]: Update the text that is shown in the Room Subject between the current goal and the next goal.


5. /next : Used to advance to the next goal once the current goal is complete, when auto advance is turned off.


6. /skip : Advance to the next goal regardless of the status of the current goal.

C. Goal Counter

For the Goal Counter show, you define the smaller goal amount that will be tipped repeatedly, and then define prizes that will occur at a certain number of goals reached. For example, you may define that each goal will be 99 tokens, and then at 5 goals you take off your shirt, 10 goals take off your pants, etc. If there is a final/end goal, set it up as the highest of the goal level thresholds in the configuration list, the app will stop counting once the highest goal count is met.
By default, the room subject will show the remaining goals levels and their descriptions/prizes, plus a configurable block of text that you can use to describe what happens at the last goal or after the goals, or even just put searchable hashtags to draw more people into the show. This room subject text can be edited using the "/setcounttext" command as noted below.

1. /setcount1, /setcount2, /setcount3...(thru /setcount10) [goal] [description]: These are the commands that let you edit the goal levels for your show. Both the [goal] and [description] parameters must be entered every time and will update both values. Note that you can use these commands to add or edit an entry, however they cannot be used to delete an entry (use the /rmvcount).
   The 1-10 designation as part of the command identifies which Goal Level entry you are adding or modifying.
   The [goal] parameter is the new value you are setting for the goal level (such as '10' for doing a prize at the 10th goal). Even if you are not changing the goal level (only changing the description, you must still enter the existing value for the goal level.
   The [description] Parameter is the new value you are setting for the goal level description. Even if you are not changing the description (only changing the goal level), you must still enter the existing value for the description.
   An example of the syntax for this command would be "/setcount5 20 Blow job", which would set goal level 5 to be a Blow Job, to be done after you've hit the individual goals 20 times.
   Note that you can't make updates to the current goal level or past goal levels, only future goal levels.


2. /rmvcount [level]: Remove the goal from goal counter level of [level] (amount and description are both removed). Note this is also only a temporary change made within the session, it does not permanently update the launch page config.


3. /setcounttext [newsubject]: Update the text that is shown in the Room Subject after the listing of the remaining goal levels.


4. /chgcountgoal [amt] : Change the amount that is being used for the individual goal levels (99 in the above example) to a new value of [amt]. If changing the value after the tipping has already started, it cannot be set to a value that is less than the tips received against the current goal.


5. /skip : Advance to the next individual goal regardless of the status of the current goal. Note this will only do one individual goal at a time, you can use the command /skiplevel described below to skip past the current goal level threshold


6. /skiplevel : Advance to the point the next goal level is complete, regardless of the status of the current goal. If there are no more goal level prizes, this will skip to the end of the show, so check the goal list (/lg) to be sure you know how what levels remaining have goals. As an example, if you are on goal 7, and there are prizes every 5 goals, it will skip ahead to having completed goal 10.

D. Tip Sequence Goals

For the Tip Sequence goal show, you can setup the starting and ending points in a sequence that users will tip through, and there can be intermediate goals defined at certain sequence thresholds. The tip sequence can be ascending or descending. For example, you could define the sequence as ascending from 1 to 50, with a goal threshold at 15, 20, 30, and 40... you could also define a sequence as descending from 60 to 10, with goal thresholds at 50, 40, 30, 20, 10, the direction, the range, and the goal levels are all configurable.
By default, the room subject will show the remaining goals sequence levels and their descriptions/prizes, plus a configurable block of text that you can use to describe what happens at the last goal or after the goals, or even just put searchable hashtags to draw more people into the show. This room subject text can be edited using the "/setsequencetext" command as noted below.
Group tipping is available, which allows smaller tips to be accumulated against the current tip sequence number, and advancing when the accumulation meets or exceeds the next number.
There is also a parameter to turn on/off the display of the total tips that will result for the range.

1. /setseq1, /setseq2, /setseq3...(thru /setseq10) [goal] [description]: These are the commands that let you edit the goal levels for your show. Both the [goal] and [description] parameters must be entered every time and will update both values. Note that you can use these commands to add or edit an entry, however they cannot be used to delete an entry (use the /rmvseq).
   The 1-10 designation as part of the command identifies which Sequence Goal Level entry you are adding or modifying.
   The [goal] parameter is the new value you are setting for the goal level (such as '10' for doing a prize once the count sequence reaches and exceeds the number 10). Even if you are not changing the sequence goal level (only changing the description), you must still enter the existing value for the sequence goal level.
   The [description] Parameter is the new value you are setting for the goal level description. Even if you are not changing the description (only changing the goal level), you must still enter the existing value for the description.
   An example of the syntax for this command would be "/setcount5 20 Blow job", which would set goal level 5 to be a Blow Job, to be done after you've hit the individual goals 20 times.
   Note that you can't make updates to the current sequence goal level or past sequence goal levels, only future sequence goal levels.


2. /rmvseq [level]: Remove the goal from sequence goal level of [level] (amount and description are both removed). Note this is also only a temporary change made within the session, it does not permanently update the launch page config.


3. /setsequencetext [newsubject]: Update the text that is shown in the Room Subject after the listing of the remaining goal sequence levels.


4. /usechatmsg [on/off] : Toggle the flag on and off for whether a message is posted in the chat for each sequence as it is achieved.


5. /usegrouptips [on/off] : Toggle the flag on and off for whether group tipping is allowed.


6. /skip : Advance to the next sequence regardless of the status of the current sequence.


7. /chgendseq [newseq]: Update the value for the end of the sequence. When ascending this is the higher number of the range, and when descending it is the low number of the range. The value cannot be updated to a sequence that has already been passed, or affect the current goal level target.

For reference, here are the total number of tips for several common sequence ranges:
from 1-10=55
1-20=210
1-30=465
1-40=820
1-50=1275
1-60=1830
1-70=2485
1-80=3240
1-90=4095
1-100=5050

E. Tip Jar

For the Tip Jar show, you can setup a single goal, or multiple goals that will be progressed through in sequence as users tip. As each goal is reach, a countdown begins using the number of tokens in the jar (total tips when goal was hit or passed). Tokens begin to 'drain' out of the jar at the specified rate of tokens per second. During this time, the user is performing the prize for that goal, and they would stop performing once the tip jar runs out/empties. While it is draining, users can continue to tip to keep it full and keep the performance going.
One the jar is empty, there is a configuration flag that defines if the app automatically moves from the completed goal to the next, or requires the use of the /next command to advance after the goal is met. If set to automatic advance, user will now be able to tip towards the next goal.
The goals also have a recyle count setting, which lets the broadcaster identify that some goals will be repeated over and over, to the defined threshold. Note that a recycle of '1', means that the goal will be performed twice (two cycles).
By default, the room subject will show the current goal amount and description, and a configurable block of text that you cn use to describe what happens when the tip jar is running, or even just put searchable hashtags to draw more people into the show. This room subject text can be edited using the "/setjartext" command as noted below.

1. /setjar1, /setjar2, /setjar3...(thru /setjar10) [goal] [recyc] [description]: These are the commands that let you edit the goals for your show. All three of the [goal], [recyc], and [description] parameters must be entered every time and it will update all three values. Note that you can use these commands to add or edit an entry, however they cannot be used to delete an entry (use the /rmvjar for that).
   The 1-10 designation as part of the command identifies which entry you are modifying
   The [goal] parameter is the value you are setting for the goal amount. Even if you are not changing the goal (only changing the description), you must still re-enter the existing value for the goal.
   The [recyc] parameter is the value you are setting for the recycle count. Even if you are not changing the recycle count (only changing the goal amount or description), you must still re-enter the existing value for the recycle count. Note that the default for recycle is '0', which means the goal is done once. With a recycle of '1', the goal is done twice, and if the recycle is '2', the goal is done three times, etc.
   The [description] Parameter is the value you are setting for the goal description. Even if you are not changing the description (only changing the goal amount), you must still re-enter the existing value for the description.
   And example of the syntax for this command would be "/setjar2 400 Blow job", which would set goal 2 to begin a Blow Job once you reach 400 tokens and continue that prize as long as the tip jar has tokens in it.
   Note that you can't make updates to the current goal or past goals, only future goals.


2. /rmvjar [level]: Remove the goal for the tip jar goal level of [level] (amount and description are both removed). Note this is also only a temporary change made within the session, it does not permanently update the launch page config.


3. /setjartext [newsubject]: Update the text that is shown in the Room Subject after the current goal.


4. /faster [levels]: Speeds up the drain rate by the specified number of levels. If no level is specified it is assumed to be by one level. If a level is specified beyond the maximum, the maximum is used.


5. /slower [levels]: Slows down up the drain rate by the specified number of levels. If no level is specified it is assumed to be by one level. If a level is specified below the minimum, the minimum is used.


6. /next : Used to advance to the next goal once the current goal is complete, when auto advance is turned off.


7. /skip : Advance to the next goal regardless of the status of the current goal. This will also bypass the prize/draining of the jar for the current goal. Note that for the Tip Jar goals, the /skip and /next work in a similar fashion.

As noted, the drain rate can be increased or decreased, and below are the available rates. You set the default on the launch page, and then you can change it during the show using the /faster and /slower commands:
Level 1: 5 tokens per second (fastest)
Level 2: 4 tokens per second
Level 3: 3 tokens per second
Level 4: 2 tokens per second
Level 5: 1 token per second
Level 6: 1 token every 2 seconds
Level 7: 1 token every 3 seconds
Level 8: 1 token every 4 seconds
Level 9: 1 token every 5 seconds
Level 10: 1 token every 10 seconds (slowest)

F. UltraApp Ticket Show

As noted, the Fembot's built-in ticket show can be used rather than an external stand alone app if you like, however, the app features are usually a better fit for ticket shows, so it is suggested to use the UltraApp Ticket Show rather than the bot if possible. Both have the benefit of not giving anyone you don't know access to your shows. Most of the CrazyTicket features are duplicated into both of them, with some tweaks and improvements.
Since it is not expected to have both the Fembot Ticket Show and the UltraApp Ticket Show (or CrazyTicket) running at the same time, the same commands are used for many of the features to make it easier to manage the show for those familiar with the CrazyTicket commands.
An Outstanding Ticket feature is included, which lets you maintain a list of users that have outstanding tickets that they can use for future shows, in the event they have to leave before the show starts, or there is a problem with a show and you'd like to grant the ticket holders a free ticket to a future show. ** IMPORTANT: The list can be viewed during the show using the "/otlist" command, and the "/otchanges" command can be used to see which users have saved a ticket or used a saved ticket during the show, as these changes need to updated in the outstanding ticket list on the launch page for the next show. The list should also be saved outside of CB.
Also, it is not advisable to put the ticket price in the show description, as those are not automatically updated if the price is changed. The notices that are displayed show the current ticket price and are updated automatically when the price changes.

1. /tickets : (all users) Display the list of users that have bought a ticket. If the parameter of 'alpha' is added, the list is displayed alphabetically. Note that viewers can be added back to the show using the /add or /addticket commands and pasting the list that is shown from the /tickets command.


2. /useot [on/off]: (mods/bc only) Toggle the setting for whether the Outstanding Ticket feature of the Ticket Show is "on" or "off". Overrides the initial setting, and allows you to turn the Outstanding Ticket usage feature on or off during the show. .


3. /otlist : (all users) Display the list of outstanding ticket holders, can be used by anyone if the Outstanding Ticket feature is enabled.


4. /otchanges : (mods/bc only) ** IMPORTANT when using the OT feature ** Displays a list of tickets that have been saved or used during the current session so the permanent list can be updated.


5. /saveticket: (all ticket buyers) If the broadcaster has enabled Outstanding Tickets (and is tracking them) - If you've bought a ticket and will not be able to stay for the show, you can save it for a future show. You will no longer be able to see the current show. IMPORTANT: If in the same session, the ticket will be available automatically. However for future shows or if the broadcaster restarts the bot, the broadcaster must add the saved tickets to the outstanding ticket list to be able to use them with /useticket.


6. /useticket: (all users with an outstanding ticket) If the broadcaster has enabled Outstanding Tickets (and is tracking them) - Redeem an outstanding ticket and use it for access to this show. You can use the command /otlist to view the list of outstanding ticket holders if the broadcaster has enabled this feature.


7. /addot : (mods, bc if granted privileges) If the outstanding ticket feature is in use, the broadcaster can manually give a user an outstanding ticket. Moderators can also add if they have authority. The addition still must be made permanent by updating the launch page outstanding ticket list.


8. /rmvot : (mods/bc only) Remove a user from the outstanding ticket list within the current show. The removal still must be made permanent by updating the launch page outstanding ticket list.


9. /addticket or (/add) [user]: (bc only, moderator when granted privileges) Manually add a user to the ticket show list. Can be a specific user or a list of users separated by a comma. Note that /add is the CrazyTicket command but also works with the Fembot Ticket show.


10. /rmvticket (or /del or /delticket) [user]: (mods/bc only) Manually remove a specific user from the ticket show list, only used for one user at a time.


11. /startshow: (mods/bc only) Start the ticket show when not set to automatic start. Once started, the show will only be visible to ticket holders. Hint: start the show when you're in a good position for the preview pic to be frozen that will attract more ticket buyers. Note that /startshow is the CrazyTicket command but also works with the Fembot Ticket show.


12. /showwarn (or /showover): (mods/bc only) Display a warning that the show will be ending soon and ticket purchases are allowed but not recommended. If configured, this can also end the positions menu, and reduce the ticket price. Note that /showover is the CrazyTicket command but also works with the Fembot Ticket show.


13. /showend (or /stopsales): (mods/bc only) Suspend ticket sales, no more automatic ticket purchases can be made. Recommended to always do this once you are less than a few minutes from the end of the show so people don't buy at the last second and are disappointed by getting a short show. If configured, this can also end the positions menu, and reduce the ticket price. Note that /showend is the CrazyTicket command but also works with the Fembot Ticket show.


14. /stopshow: (mods/bc only) End the hidden show and return to a public broadcast.


15. /newticketshow: (mods/bc only) Completely refresh the ticket show to start a brand new show. This will remove all the ticket holders from the list, and re-initialize all settings using the configuration from the launch page.


16. /restartshow: (mods/bc only) Go back into hidden cam mode if the show was accidentally ended too soon, or the broadcaster wanted to go back to public to sell more tickets. The ticket holder list and all settings are kept intact.


17. /ticketprice (or /ctprice, or /chgticketprice) [newprice]: (mods/bc only) Update the ticket price to the [newprice]. Note that /ctprice is the CrazyTicket command but also works with the Fembot Ticket show.


18. /starttimer (or /ticketstarttimer, or /starttickettimer) [time]: (mods/bc only) Start a [time] minute timer for the raffle drawing when in 'timer' mode with the drawing to be triggered by the /raffledrawing command. The timer will count down but not automatically perform the drawing (unless set to automatic mode but the auto-timer was ended, and this is a restart of that timer)


19. /addtime (or /ticketaddtime, or /addtickettime) [time]: (mods/bc only) Add [time] minutes to the timer for either automatic or manual drawing mode. The [time] value can be a negative number to subtract time, but cannot be greater than the remaining time.


20. /stoptimer (or /ticketstoptimer, or /stoptickettimer): (mods/bc only) Stop the raffle timer for either automatic or manual drawing mode.


21. /tickettimeleft : (mods/bc only) Display the time left on the ticket show countdown for either automatic or manual starting mode.


22. /showtime : (all users) Display a message showing how long the current show has been hidden.


23. /chgticketmode (or /chgtktmode) [manual/timer/ticketgoal/tokengoal]: (mods/bc only) Switch between the modes being used to determine when to start the ticket show. If switching from a timer show to a non-timer show, the timer will be ended. Ticket count and Tip Count are being tracked regardless of mode, so switching to a 'goal' mode should not require starting progress at 0.


24. /chgticketauto (or /chgtktauto) [auto/bc]: (mods/bc only) Switch between the modes being used to define if the show starts automatically when a goal is reached or timer expires, or if the broadcaster or mods still control the start of the show.


25. /giftticket [user]: (all users, once you have extra tickets) If the 'gifting' feature is enabled, when you tip enough to buy extra tickets, you can gift those tickets to other users using this command. Each time you gift, it removes one of your 'extra' tickets. You can only gift extra tickets with this command, to give away your own ticket, you can use /givemyticketto as noted below. Be sure to type the user name correctly for the person you are gifting to, extra tickets cannot be recovered once they are gifted. This can be done before and during the show.


26. /givemyticketto [user]: (all ticket buyers) If you can't stay for a show, and outstanding ticket feature is no used to allow saving your ticket, you can give your ticket to another user. This can only be done before the show starts, and you will be removed from the ticket show list!


27. /ticketsubject (or /ctsubject) [newsubject]: (mods/bc only) Change the room description/subject/title to a new value. Also supports the CrazyTicket command of /ctsubject.


28. /ctn: (bc/mods) Post a one-time notice in the chat. The syntax for using this type of notice is "/cn [X]", where [X] is the message you want to send. This is the plain notification without any separators or highlighting.


29. /ctnd: (bc/mods) Post a one-time notice in the chat. The syntax for using this type of notice is "/cnd [X]", where [X] is the message you want to send. This notification includes a dash separator before and after the message, but no highlighting.


30. /ctnh: (bc/mods) Post a one-time notice in the chat. The syntax for using this type of notice is "/cnh [X]", where [X] is the message you want to send. This notification includes highlighting, but no separators.


31. /ctndh: (bc/mods) Post a one-time notice in the chat. The syntax for using this type of notice is "/cndh [X]", where [X] is the message you want to send. This notification includes both separators and highlighting.


32. /addefc [user]: (bc only) From within the show, adds a user to the External Fan Club list where [user] is the person you want to add. Normally these users are entered in the Fan Club List field on the launch page, but the command can be used if there is a new fan during the show.


33. /rmvefc [user]: (bc only) Removes a user from the External Fan Club List where [user] is the person you want to remove.


34. /listefc : (mods/bc only) Displays the list of users currently in the External Fan Club list.


35. /addvipuser [user]: (bc only) From within the show, adds a user to the VIP list where [user] is the person you want to add. Normally these users are entered in the VIP List field on the launch page, but the command can be used if there is a new VIP during the show.


36. /rmvvipuser [user]: (bc only) Removes a user from the VIP List where [user] is the person you want to remove.


37. /listvip : (mods/bc only) Displays the list of users currently in the VIP list.

Latest enhancements and fixes:

3/25/2019 Version 1.5 (current version):
- Add ability for all users to see the ticket show ticket buyer list

3/25/2019 Version 1.4 :
- Add Support for Dorothy's Gamebot commands

3/14/2019 Version 1.3 :
- Display the OT list changes upon stop show.

2/20/2019 Version 1.2 :
- Add external fan club and VIP list management within the App to allow for adding them to the show without command entry. If you're already using Dorothy's Ultra Fembot, you'll need to duplicate the EFC and VIP lists from there here into the App as well.

2/14/2019 Version 1.1:
- Added ability to customize background and text color in the panel
- Added ability to change the background panel and text color on the fly using commands /chgpanelbg and /chgpaneltext

2/9/2019 Version 1.0:
- Original release with Ticket Show, Single / Progressive Goals, Goal Counter, Tip Sequence Goals, and Tip Jar features
- Includes Token Stats