Discord Server Ticket Systems Design
Budget: $750 – $1,500 USD
I need a ticket systems for our Discord server. Here’s exactly what I’m looking for:
---
1. CROWN SALES TICKET SYSTEM
This system is for managing crown store sales between buyers and our verified sellers (called @Vendors). The system should handle tracking, calculations, and logging.
What We Need:
Ticket Access & Visibility
Anyone in the server can open a Crown Sales ticket.
Once opened, only the buyer, @Vendor role, and Admins can view the ticket.
Tickets can be claimed by a vendor and then closed once the sale is complete.
Ticket Form Should Ask For:
Buyer’s In Game name
Amount of crowns purchased
Total gold paid
Crown-to-gold rate used (dropdown: 300:1, 400:1, 500:1, 600:1, 700:1)
Automations When Ticket Closes:
1. Post a summary of the sale in a public channel like #crown-logs.
2. Post raffle entry data to #crown-raffle-tickets, based on the following logic:
300:1 = 1 ticket per 500 crowns
400:1 = 1 ticket per 400 crowns
500:1 = 1 ticket per 300 crowns
600:1 = 1 ticket per 200 crowns
3. Log ticket details in a private channels for each @vendor who claimed the ticket only the vendor and admins can see (e.g., #vendor-history-[name])
Gold Split Calculation (Dynamic Guild Cut)
Guild cut increases based on the rate:
300:1 → Guild gets 50:1, Seller gets 250:1
400:1 → Guild gets 75:1, Seller gets 325:1
500:1 → Guild gets 100:1, Seller gets 400:1
600:1 → Guild gets 100:1, Seller gets 500:1
700:1 → Guild gets 100:1, Seller gets 600:1
The Second Ticket system is for GUOLD EVENTS AND VERIFICATION
2. EVENT SUBMISSION TICKET SYSTEM
This ticket system is for members of certain ranks (@Mentor) to submit in-game events they’ve hosted and list participants.
What I Need:
Ticket Access
Only certain ranks (e.g. @Mentor) can open these tickets.
Ticket Form Should Ask For:
Host’s In-Game Name
Date of event
Name of event
List of all participants (multi-line input)
Optional: screenshots
Automations When Ticket Closes:
1. Post a message in a channel like #event-participation-log with:
Event name & host
List of participants
Bundle duplicate names so each participant only appears once per weekly summary
2. This list should auto-compile across all event tickets that week, so admins have a clean list of all players who participated for event credit.
---
1. CROWN SALES TICKET SYSTEM
This system is for managing crown store sales between buyers and our verified sellers (called @Vendors). The system should handle tracking, calculations, and logging.
What We Need:
Ticket Access & Visibility
Anyone in the server can open a Crown Sales ticket.
Once opened, only the buyer, @Vendor role, and Admins can view the ticket.
Tickets can be claimed by a vendor and then closed once the sale is complete.
Ticket Form Should Ask For:
Buyer’s In Game name
Amount of crowns purchased
Total gold paid
Crown-to-gold rate used (dropdown: 300:1, 400:1, 500:1, 600:1, 700:1)
Automations When Ticket Closes:
1. Post a summary of the sale in a public channel like #crown-logs.
2. Post raffle entry data to #crown-raffle-tickets, based on the following logic:
300:1 = 1 ticket per 500 crowns
400:1 = 1 ticket per 400 crowns
500:1 = 1 ticket per 300 crowns
600:1 = 1 ticket per 200 crowns
3. Log ticket details in a private channels for each @vendor who claimed the ticket only the vendor and admins can see (e.g., #vendor-history-[name])
Gold Split Calculation (Dynamic Guild Cut)
Guild cut increases based on the rate:
300:1 → Guild gets 50:1, Seller gets 250:1
400:1 → Guild gets 75:1, Seller gets 325:1
500:1 → Guild gets 100:1, Seller gets 400:1
600:1 → Guild gets 100:1, Seller gets 500:1
700:1 → Guild gets 100:1, Seller gets 600:1
The Second Ticket system is for GUOLD EVENTS AND VERIFICATION
2. EVENT SUBMISSION TICKET SYSTEM
This ticket system is for members of certain ranks (@Mentor) to submit in-game events they’ve hosted and list participants.
What I Need:
Ticket Access
Only certain ranks (e.g. @Mentor) can open these tickets.
Ticket Form Should Ask For:
Host’s In-Game Name
Date of event
Name of event
List of all participants (multi-line input)
Optional: screenshots
Automations When Ticket Closes:
1. Post a message in a channel like #event-participation-log with:
Event name & host
List of participants
Bundle duplicate names so each participant only appears once per weekly summary
2. This list should auto-compile across all event tickets that week, so admins have a clean list of all players who participated for event credit.