You can use this tool to test how different commands are matched against different chat messages.
Add messages, and change the command, if they'll match will be automatically shown as you change the command.
No command means anything matches!
Put these directly as they appear here into the chat command setting field, including any $ symbols etc.
This will require viewer to put in their Guild Wars 2 account names in the format matching Test.1234 - it handles names with spaces too
Yup, it sure does! For names with spaces in, the last part will match, and the whole message will be shown. For example, Name With Spaces.1234 will match with Spaces.1234 - but the whole message will be shown if selected as a winner.
This will require viewer to put in their 8-digit Steam Friend Code 12345678.
This will match either the $gw2_account$ or $steam_friend$ chat commands above
The Spam Limit only affects Active Chatter giveaways. When doing the giveaway, every user will have how many times they entered counted. If this count exceeds the set spam limit, they will be removed from the draw before choosing winners. The goal of the spam limit is to reduce chat spam and catch bots spamming blindly.
Your Twitch details are only saved locally, in the folder with giveaway-o-tron.exe. They are never sent anywhere, besides to authenticate with the Twitch API. They are never stored anywhere besides locally on your PC.
At the top of the app, one of the buttons has the OBS icon, which will take you to the OBS Settings page.
Here you can copy your specific URL for the two available alert types, which are:
This alert will show the winners name in a brief alert. You can control how long the alert stays visible for with the Duration setting on the OBS Settings page.
This alert will automatically show giveaway status, based on the Chat Command entered on the main screen, and the status of the Timer tool also on the main screen.
When the Timer is started, the alert will change to display a message stating that the giveaway is open, as well as any chat command required (including descriptions of any special commands used).
When the Timer finishes, it will automatically update the alert to say that the giveaway has been closed.
Cancelling the Timer will remove the alert.
At the top of the app, one of the buttons has the Discord icon, which will take you to the Discord Settings page.
In the top right of this page is a button which will take you to invite the bot to an available server.
Once the bot is invited, before it can post anything, it needs to know where you want it to send messages, and so you must enter the Server ID and Channel ID.
To get these:
Once the bot has been invited, and configured with the required IDs, it will post the default messages for winners and giveaways starting and ending.
You can control these on the Discord Settings page, by setting the Title and Body for each type independently. You can also enable/disable each message, by ticking or unticking the checkbox to the right of the other details.
You can use special keywords in the title and body messages to enter things like the winners name - for more details see in the app itself.
Mentions like @role will work in the message body as well and correctly notify Discord members with the specified role.
One useful setting you can also find on the Discord Settings page isGiveaway Alert Min Time. This interacts with the Timer tool on the main page. The Giveaway Start and Giveaway End messages will only be sent if the Timer duration exceeds the Giveaway Alert Min Time. This can be useful for only notifying your Discord for longer entry giveaways, and not the brief 2 minute flash entry giveaways.
First off, open Giveaway-o-tron, and go to the Settings page by clicking on the cog icon.
At the bottom of the Settings page, there are two red buttons.
To begin with, click the Sign Out Token Tool. This will cause new Twitch tokens to be reissued, and available for you to copy.
Then, click on the Reset Channel Info button back in the app. This will take you back to the Setup screen, where you can enter the new tokens.
This should fix most issues.
If it does not, please let me know by opening an issuehere so it can be investigated.