> For the complete documentation index, see [llms.txt](https://invomagic.gitbook.io/ticketsdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://invomagic.gitbook.io/ticketsdocs/drops/giveaways.md). # Drop Giveaways Drop giveaways are a special type of giveaway, instead of playing pick a number, this type of giveaway is first click takes all, this is awesome so jumpstart a chat or get people's attention fast! ## Create a Drop Giveaway To create a drop giveaways you need run the `/drops giveaway` command this will open up a plethora of options to select from, lets go over them now ### Options **Host:** this is the user that is hosting the giveaway, they will be notified when the giveaway is claimed\ **Channel:** This is the channel where the giveaway will be sent!\ **Blacklist:** Users with this role cannot claim the giveaway\ **Requirement:** Users must have this role to claim the giveaway\ **Wait:** The amount of time it takes before the giveaway can be claimed\ **Image:** This is the image that will appear in the embed\ **Winner Role:** This is a role that will be automatically assigned\ **Ping:** Tickets will ping this role for the giveaway\ **Prize:** This prize you are giving away\ **Unb Money:** Giveaway currency instantly to the winner by linking with Unbelivaboat! [Read this](/ticketsdocs/drops/authorization.md)\ **Kiai XP:** Give XP Instantly to the winner by linking with with Kiai! [Read this](/ticketsdocs/drops/authorization.md) ### Form You'll receive a form with 2 inputs, heres what they mean\ \ **Giveaway message:** this will appear under your giveaway with a cool message in a separate embed for you to speak your heart out!\ \ **Winner Message:** This is the message Tickets will send when someone claims the giveaway, you can use `` to refrence the winner and `` to refrence the giveaway prize! (These variables are not functional in the Giveaway message) ### Upon claiming Upon claiming the host will be notify and any Unb money, Kiai XP, and winner role will be granted instantly, the giveaway will edit removing the claim button, and a giveaway winner message will be sent.

Host getting a DM

## Configuration Somethings are setup via a configuration command, this command you will need to run is `/drops configuration` ### Configurations **Staff Role:** This is the role that can create drop giveaways, Administrators can always create drop giveaways\ **Attempt Claim Cooldown:** When someone attempts to claim we put them on a cooldown so they cant just spam the button, be default its 7 seconds, you can however set it to any number of seconds you want\ **Logging Channel:** This is the channel we'll send logs of giveaways to ## View Statistics Wanna see how much you've been giving?\ Run the `/drops stats` command and we'll show the following stats\ \ **Total Drop Giveaways:** This is the total amount of drop giveaways your server has hosted, it will only count ones that have been claimed\ **Total XP Given away:** This is the amount of XP paid out to users via our Kiai XP option\ **Total Server Currency Given out:** This is the amount of "money" given out via our Unb Money option --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://invomagic.gitbook.io/ticketsdocs/drops/giveaways.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.