How to use Tickets: Difference between revisions
m (Thulamin moved page Guide to Tickets to How to use Tickets: They're all guides in this section so the name was redundant) |
(Added Tickets versus Wishes) |
||
| Line 12: | Line 12: | ||
You can use tickets to request assistance or clarification on in-game matters that require staff input. | You can use tickets to request assistance or clarification on in-game matters that require staff input. | ||
==Common Types of Tickets== | ==Tickets versus Wishes== | ||
Wishes are covered in a separate guide, but they would be used when immediate attention is needed to an | |||
issue or when there is a bug that has you stuck - such as a locked door that you can't get out of. | |||
==Common Types of Tickets == | |||
===Animation Requests=== | ===Animation Requests=== | ||
| Line 18: | Line 22: | ||
If you need an animation (e.g., a special emote, object manipulation, or NPC response), especially one that requires staff timing or presence, submit a ticket. | If you need an animation (e.g., a special emote, object manipulation, or NPC response), especially one that requires staff timing or presence, submit a ticket. | ||
'''Examples:''' | '''Examples:''' | ||
*Interacting with key Non Player Characters. | *Interacting with key Non Player Characters. | ||
*Entering a hidden area or triggering a scripted event. | *Entering a hidden area or triggering a scripted event. | ||
| Line 25: | Line 29: | ||
<small>'''Note:''' These usually require scheduling with staff to align with your playtime, so plan ahead.</small> | <small>'''Note:''' These usually require scheduling with staff to align with your playtime, so plan ahead.</small> | ||
===Investigative Queries / Forensics / Object Inspection=== | ===Investigative Queries / Forensics / Object Inspection === | ||
These tickets are used when you're examining something in-game and want to know what your character would find based on their skills or tools. | These tickets are used when you're examining something in-game and want to know what your character would find based on their skills or tools. | ||
| Line 32: | Line 36: | ||
*Checking a bone fragment for explosive residue. | *Checking a bone fragment for explosive residue. | ||
*Determining how a piece of equipment was destroyed. | *Determining how a piece of equipment was destroyed. | ||
*Inspecting blood for signs of poison. | * Inspecting blood for signs of poison. | ||
Once staff responds, you can use the results to guide your RP and push the story forward. | Once staff responds, you can use the results to guide your RP and push the story forward. | ||
===Clarification or Mechanical Rulings=== | ===Clarification or Mechanical Rulings === | ||
Sometimes you may need clarification on how a rule or system works in a specific situation. | Sometimes you may need clarification on how a rule or system works in a specific situation. | ||
'''Examples:''' | '''Examples:''' | ||
*Whether a certain skill applies in a given scenario. | *Whether a certain skill applies in a given scenario. | ||
*How a custom item functions under stress. | *How a custom item functions under stress. | ||
Latest revision as of 05:47, 17 May 2025
In Untold Dawn, the ticket system is a tool for players to interact with staff outside of regular roleplay, especially when certain actions require coordination, confirmation, or behind-the-scenes resolution.
This page explains how and when to use the ticket system.
What Is a Ticket[edit | edit source]
A ticket is a private communication thread between you and the staff team, opened in discord:
You can use tickets to request assistance or clarification on in-game matters that require staff input.
Tickets versus Wishes[edit | edit source]
Wishes are covered in a separate guide, but they would be used when immediate attention is needed to an issue or when there is a bug that has you stuck - such as a locked door that you can't get out of.
Common Types of Tickets[edit | edit source]
Animation Requests[edit | edit source]
If you need an animation (e.g., a special emote, object manipulation, or NPC response), especially one that requires staff timing or presence, submit a ticket.
Examples:
- Interacting with key Non Player Characters.
- Entering a hidden area or triggering a scripted event.
- Coordinating a combat action that needs real-time support.
Note: These usually require scheduling with staff to align with your playtime, so plan ahead.
Investigative Queries / Forensics / Object Inspection[edit | edit source]
These tickets are used when you're examining something in-game and want to know what your character would find based on their skills or tools.
Examples:
- Checking a bone fragment for explosive residue.
- Determining how a piece of equipment was destroyed.
- Inspecting blood for signs of poison.
Once staff responds, you can use the results to guide your RP and push the story forward.
Clarification or Mechanical Rulings[edit | edit source]
Sometimes you may need clarification on how a rule or system works in a specific situation.
Examples:
- Whether a certain skill applies in a given scenario.
- How a custom item functions under stress.
- Determining outcomes for unusual uses of mechanics.
Story or Lore Interactions[edit | edit source]
Tickets can also be used to interact with hidden or staff-controlled lore.
Examples:
- Getting the results of a study you've done on a new species or type of material.
- Asking if your character would recognize a symbol, or notice something during an event.
- Exploring rumors or clues that might not have a clear path forward in-game.
Best Practices[edit | edit source]
- Be concise but clear. Provide enough context that staff can respond effectively, but avoid unnecessary fluff.
- Use in-game references. Include item names, skill levels, or scene details as relevant.
- Be patient. Some tickets (especially animations) take longer to resolve.
Still Not Sure?[edit | edit source]
If you're unsure whether something warrants a ticket, ask in the help channel or message a moderator privately. It's better to ask than to miss out on a chance to deepen your story.