Create, fill, run and archive events.

System overview

One board creates one event card and one discussion thread

Administrators publish an Event Board in a dedicated Discord channel. Members use its buttons to create activities; they do not need to memorize an event command. Every published activity receives a live event card for status, schedule and participants plus a Discord thread for coordination.

Board setup

Publish only the boards included in your edition and plan

Run the relevant setup command once per board. Reusing it with another channel moves that board configuration instead of creating a second active configuration. Luminox refreshes the board links and the channel's active counter as events are created, cancelled, completed or removed.

Universal Edition

Create reusable event templates for any game or community

Universal does not assume that a server uses Tibia vocations or even character classes. An administrator opens /events configure to design the event types and team structure for that Discord server. The configuration is stored independently for each server and never changes Community or Founder event rules.

Built-in starting templates

Configuration workflow

1. Run /events configure as a server administrator.
2. Select an existing template, create a new one or reset the server to the two defaults.
3. Edit the template name, emoji and description.
4. Add, edit or remove slot types. Every slot stores its Main, Waitlist and minimum values.
5. Set the template members should see first during event creation.
6. Publish the general Event Board with /events set general.

• Up to twenty templates may be stored per server.
• Each template may contain up to ten slot types.
• A template can hold up to one hundred combined Main and Waitlist places.
• At least one template and one slot must remain, preventing an unusable configuration.
• Published events save a complete template snapshot. Later edits affect future events only.

Discord structure

Active counters and nested threads make every board easy to scan

A configured board channel can show its active-event total in the channel name, such as bosses·1. Discord places the linked activity thread beneath that channel, for example Raid for final boss. Members can therefore identify the active event from the server sidebar before opening any panel.

The counter excludes expired and cancelled activities. When the last active event closes, Luminox returns the channel count to zero without deleting the archived thread history.

Before creating

Identity and timezone checks prevent broken events

• The creator must configure a timezone with /timezone set so natural date inputs are interpreted correctly.
• Community Hunt, Boss, Quest and general Event boards require at least one eligible registered character.
• Universal general events use the member's Discord server identity and do not require a game character.
• Community characters must belong to the configured guild and world when the action requires guild eligibility.
• The server must give Luminox permission to send messages, add reactions and create, manage and archive threads in the selected channel.

Creation suite

Review every important choice before publishing

1. Open the correct board and click Create hunt, Create boss, Create quest or Create event.
2. Universal creators choose one of their server's saved templates and the slot they will occupy. Community and Founder creators use the fixed rules of the selected Tibia board.
3. Choose Set date now, Vote · Leadership decides or Vote · Automatic.
4. Enter the title, complete description and duration. Automatic voting requires an expected duration.
5. Community and Founder select the creator's compatible registered character. Universal resolves the creator's Discord identity automatically.
6. Optionally invite eligible participants from the review screen and assign the intended custom slot or registered character.
7. Check the final summary, remove any mistaken invitation and publish.

Natural inputs such as “tomorrow 20:30”, “Saturday 21:00” or “in 3 hours” are interpreted in the creator's stored timezone and displayed with Discord timestamps, so every viewer sees the same moment in local time.

Event rules

Universal is customizable; Community and Founder remain purpose-built for Tibia

Manual invitations

Reserve the intended place before another member takes it

Universal events invite a Discord member directly into a custom slot. Character-based Community and Founder boards select one of that account's eligible registered guild characters. Invitations never bypass the capacity or eligibility rules of the active event.

1. During creation review, click Invite participant.
2. Universal selects the Discord member and custom slot. Community or Founder selects the Discord member and registered character.
3. Repeat for additional accounts or use Remove invite before publishing if a selection was incorrect.
4. After publication, current Leadership, a server administrator or a configured moderator can use Invite participant on the event card.
5. Luminox adds the participant immediately, marks the entry as Invited, grants thread access and posts an invitation notice in the thread.

Joining and leaving

Every participant keeps one clear identity, slot and status

• Universal events use the member's Discord server identity and ask which custom slot should be joined.
• Each Universal slot manages its own Main and Waitlist capacity from the event's protected template snapshot.
• Community boards ask which compatible registered character should join; members may save “always use my main” or return to “ask every time”.
• Community Hunt and Boss boards use vocation reactions. Quest and general Event boards use one open join reaction.
• The event card marks the organizer as Leadership, manually added participants as Invited, active positions as Main and overflow as Waitlist or Reserve.
• Every active participant is added to the event discussion thread.
• A member may leave from the event card. The departure remains crossed out with its time, while the remaining active order is recalculated.
• Leadership may kick another participant; that removal is recorded and thread access is removed.

Schedule voting

Propose ranges and choose manual or guarded automatic scheduling

• Leadership and every joined or invited participant can submit up to three proposals; one event can hold up to twenty.
• Leave the date blank to mean every day.
• Use a fixed date, a weekday, every Friday or localized equivalents.
• Use one time such as 17:00 or a range such as 17:00-20:00.
• Each participant may vote for multiple proposals, including proposals created by other members.
• Future participants can vote after joining; votes from members who leave or are kicked stop counting.
• Discord timestamps convert exact and next recurring occurrences for every viewer's timezone.

Manual mode: Leadership may select any proposal or publish a different final date.

Automatic mode: Luminox acts only after every active participant has voted, the required team is present, one option wins without a tie and that time range covers the full event. The winning proposal's author must have voted for it and be able to receive Leadership safely.

For Hunts, automatic scheduling recalculates Main and Reserve positions from availability. If any safety condition fails, Luminox changes nothing and current Leadership may conclude the vote manually.

Leadership

One accountable organizer controls the live event

The creator joins immediately as Leadership. Leadership can close or reopen signups, schedule a recruiting event, conclude a manual vote, edit event details, invite or kick participants, transfer Leadership, cancel the event or request permanent deletion.

Server administrators and configured moderators may edit, invite and permanently delete an event when intervention is necessary. Leadership-only actions remain tied to the current organizer. A Community Hunt transfer is blocked if the new Leadership character would invalidate the shared-experience range for active members.

Editing a Universal template through /events configure does not rewrite an event already in progress. Its slot names, capacities and minimums remain attached to that event until it is completed, cancelled or deleted.

Permanent deletion always asks for confirmation because it removes both the event card and its thread immediately.

Thread coordination

Important changes reach the people already involved

Large mention lists are split into safe Discord-sized messages so one crowded event does not lose its notification.

Automatic completion

Objective requirements replace manual success buttons

At the official end, Universal checks the minimum configured in every custom slot and counts Main participants only. A template may therefore require one Tank and one Heal while allowing additional DPS, or use one open Players slot with a simple total minimum.

Community Tibia events use their fixed board minimum or required Hunt Main composition and can also evaluate online attendance from observations already collected by guild systems: participants normally need coverage for 25% of the event, with a five-minute minimum, a thirty-minute cap and at least two observations. If attendance data is unavailable, Luminox falls back safely instead of unfairly failing the event.

Waitlist or Reserve participants only qualify after becoming part of the successful Main team. Cancelled or permanently deleted events do not produce normal completion rewards.

Close and archive

Expire, cancel and delete are intentionally different actions

Normal expired and cancelled histories stay in Discord. Luminox stores only the operational metadata needed for event state, completion and rewards, not the thread conversation or its attachments.