S.VII. — Player & Lore Etiquette

General Lore & Magic Tickets

In-game Encounters & Lore Encounters

A. General Lore & Magic Tickets

Expected behavior from players in Lore tickets. Stick to this etiquette, and you will be treated with respect and your ticket will be handled efficiently!

1. Keep It Clean

Avoid spamming GIFs, emojis, or excessive images in your ticket. These clutter the ticket and make it difficult for the Lore Team to follow or respond effectively.

2. Be Prepared Before Opening

Please have your goal, emotes, and required items ready when you open a ticket. If you’re not prepared to begin, the ticket will be closed to make room for others who are ready.

3. Stay On Topic

Keep discussion relevant to the purpose of your ticket. Side chatter, unrelated questions, or long off-topic conversations about other lore related topics, make a general lore ticket for!

4. Respect the Lore Team’s Time and Decisions

Lore Team members handle many tickets daily. Please be patient, avoid pinging repeatedly, and respect their final calls on outcomes or otherwise.

5. Keep It short

Try to keep your responses or emotes to 2–3 paragraphs maximum unless otherwise requested. This helps the Lore Team read through and respond efficiently without missing key details.

6. Ticket Reuse

If your ticket goal changes entirely, please make a new ticket rather than reusing an old one. This keeps transcripts clean and prevents confusion.

7. Keep It Organized

Use clear messages, format your rolls and emotes neatly, and avoid clutter. A tidy ticket helps everyone understand what’s happening and keeps responses flowing smoothly.

8. Avoid Daily Dots

Avoid trying to “bump” your ticket with daily dots! Tickets are sorted from oldest to newest, so placing a dot in them does not help bump the ticket. A ticket will not close unless it is inactive for over 5 days. If you do have to place dots to avoid a ticket closing, you may delete the dots afterwards. Placing dots in a ticket daily can hide or move relevant information, causing the ticket to take longer to look over.

B - In-game Encounters & Lore Encounters

Random Encounter Benefits

If you gain a random encounter, you do not have to use the character you are currently playing! If you would prefer to use a different character, simply ask the lore member in LOOC upon accepting the random encounter
You may make a request for a certain type of lore encounter/event before a Random Encounter starts.

1. Listen to Moderation and Lore Members' callouts

Sometimes during a lore encounter, you may be asked to halt movement, halt Roleplay, or keep certain channels clean & quiet, such as text channels and VC. Lore Members will make these callouts so that they can log all relevant participants’ progress as quickly and seamlessly as possible!

2. Respect Lore Members’ time and passion for the server

The Lore team will do their best to run progression encounters for as many time zones as we can reasonably offer. Please do not try to coerce or ask lore members who are engaging in free time and casual player Roleplay to run lore duties such as ruptures and forge openings.

A lore member has the right to forgo and not continue an encounter or discussion with a player if they are feeling uncomfortable. Lore members are volunteers, and are not trained to handle player confrontation.

3. Make sure that you and your friends maintain TTRP rules

Public progression encounters such as mana ruptures and forge openings will start by waiting and gathering players in Primshire until they reach a reasonable or desired number of players to ensure equal and fair opportunity for people to join the event.

Lore members may choose to close events at a certain number of players.

If you or someone you have given OOC information to is caught metagaming the location of a Lore Event that is already in progress, moderation punishments will apply.

4. Pre-Write and Pre-Plan your turn during CRP or Large Scale events

If you are participating in a CRP event or encounter, use your time while you wait for your turn to plan and prepare your next turn's action, bonus action and reactions! This saves a lot of time for everybody participating, ensuring that CRP does not take too long.

In order for your roll to count, you must emote and then ask if anybody wishes to make a reaction before making any rolls. Attempting to skip others reactions may result in the lore member discounting your roll.

5. Do not OOCly observe roleplay encounters without Permission

At times a lore encounter may be a ticket containing IC only information or be a combat encounter with a rare creature that should not be known about without experiencing it firsthand. To observe a Lore run event you require permission from the presenting lore member first!

Note: This applies to player lore too! You should have permission from all parties in a roleplay to OOCly observe that roleplay. Acting on OOCly observed RP in character is metagaming.

6. Utilize appropriate forms of communication when inquiring to staff

Unless the lore member has given you permission to, please do not DM staff members through Discord or in-game for staff inquiries or staff duty purposes. A lot of people doing this can quickly flood someone's Discord account and impinge on their private life!

If you have a question for the lore team, please use the Lore Questions forum, open a General Lore ticket, or use the Help channel.

7. Lore Content & Mature Themes

TallTalesRP's official storyline is curated by the Lore Team under the creative direction of RiskBunny’s original writings, ConstructorLeo & AliferousLux. The setting draws inspiration from Taoist-inspired fantasy and other works such as Avatar: The Last Airbender and Star Wars, while exploring these themes through an exaggerated lens.

TalltaleRP's contains a range of storytelling styles, from high and light fantasy to grimdark and horror fantasy, to represent conflicting forces. By participating in Lore-run events, players acknowledge that they may encounter mature, disturbing, or emotionally intense fictional themes.

This rule is intended to inform players of the types of content that may appear in Lore-run events. It does not constitute consent to unwanted interaction between players, nor does participation in an event override any TallTalesRP rules, Minecraft's Community Standards, or applicable laws.

Potential Mature Themes

Lore-run events may contain but are not limited to:

Serious themes involving abuse, familial violence, oppression, and psychological distress.
Intense fictional violence and combat, including occasional depictions of blood, gore, injury, death, and stylized body horror.
Psychological and existential horror.
Depictions of fear, phobias, trauma, grief, and loss.
Themes involving moral corruption, manipulation, betrayal, and the consequences of characters' actions.
Loss of identity, autonomy, or control over one's character within the fictional narrative.
Institutional corruption, authoritarianism, extremism, and other forms of fictional oppression.
Fictional depictions of drug or substance use, where such material is not presented as an endorsement of illegal or harmful behavior.
Strong or offensive language where appropriate to the setting and narrative.
Permanent or significant consequences for characters, including injury, death, loss of possessions, changes to relationships, or other lasting narrative consequences.

These themes are presented for fictional storytelling purposes. Players are encouraged to review event-specific warnings where provided. If an event contains particularly sensitive material, additional warnings may be provided before or during the event.

By participating in Lore-run events, you acknowledge that TallTalesRP's storytelling may contain the themes described above and that individual events may involve content that is disturbing or emotionally intense.

If you are uncomfortable with a lore event’s subject matter, you may request to leave the event at any time.

8. Supplementary Lore

Sometimes, in order to help guide a player's roleplay experience during an eventline, the Lore team may offer OOC information about lore. This should occur via a lore ticket. Lore explained through OOC means is always expected to be private, unless explicitly stated otherwise by the presenting lore member. If you are unsure, ask the presenting lore member whether a piece of OOCly distributed lore can be shared or not.

9. Logged Lore

If you would like something logged and progressed within Lore events (e.g. horse magic stage progression) you must inform the DM out of character at the beginning of the roleplay encounter. If you are to be progressing something, it must be your own (e.g. your own horse.)