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 panelStays at the bottom of its channel, shows the active count and links directly to every active event.

Event cardDisplays the current schedule, requirements, Leadership, participant order, Main or Reserve positions and management controls.

Discussion threadKeeps planning, schedule notifications and the final event summary attached to the event instead of mixing them into the board channel.

Discord archivePreserves the finished conversation after the temporary event card is removed; Luminox does not copy thread messages or attachments into its database.

Board setup

Publish only the boards included in your edition and plan

General events · Universal and Community Free/events set general channel:#events

Hunts · Community Free/events set hunts channel:#hunts

Bosses · Community Core/events set bosses channel:#bosses

Quests · Community Core/events set quests channel:#quests

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.

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

Open the correct board and click Create hunt, Create boss, Create quest or Create event.
Choose Set date now, Vote · Leadership decides or Vote · Automatic.
Enter the title, complete description and duration. Automatic voting requires an expected duration.
Select the Hunt composition and Reserve display, or set a minimum of 2–100 participants for Boss, Quest and general Event boards.
Select the creator's compatible registered character. Universal general events resolve the creator's Discord identity automatically.
Optionally invite eligible registered guildmates from the review screen before anyone else takes their intended position.
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

Four boards share one workflow but enforce different teams

Type	Team model	Joining and success rule
Hunt	All vocations; EK + ED duo; any duo; EK + ED + DPS trio; any trio; Team 4; or any five.	Members join through vocation reactions. Luminox validates Tibia shared-experience range and uses the required Main slots for success.
Boss	Tanks, Heals and DPS ordered by arrival, with a configurable minimum of 2–100.	Vocation reactions place characters into role groups. More than one character from the same vocation may participate.
Quest	Any eligible registered character, ordered by arrival, with a configurable minimum of 2–100.	A single join reaction opens character selection. No vocation composition is enforced.
General event	Any eligible participant with a configurable minimum of 2–100.	Community uses registered characters; Universal uses Discord accounts. The format suits meetings, tournaments, social activities or any custom purpose.

Manual invitations

Reserve a place for a registered guildmate you already planned with

Character-based Community and Founder boards can add another member before publication or while an event is active. Invitations do not bypass eligibility: Luminox validates the Discord account, registered character, current guild membership, event composition and Hunt shared-experience range before reserving anything.

During creation review, click Invite participant.
Select the Discord member, then choose one of that account's eligible registered guild characters.
Repeat for additional accounts or use Remove invite before publishing if a selection was incorrect.
After publication, current Leadership, a server administrator or a configured moderator can use Invite participant on the event card.
Luminox adds the selected character immediately, marks the entry as Invited, grants thread access and posts an invitation notice in the thread.

PositionThe invitation uses normal join order. It can reserve a Main position when capacity is available or enter the Reserve queue when Main is full.

ParticipationAn invited character already counts as joined, may propose and vote on schedules, and is included in automatic scheduling checks.

Member controlThe invited member may leave normally. Leadership cannot leave until Leadership is transferred.

SafetyAn account cannot occupy two active places, the creator is already included, and a participant kicked from that event cannot simply be invited back.

Joining and leaving

Every participant keeps one clear identity and status

Universal general events use the member's Discord server identity and do not require a game character.
Community boards ask which compatible registered character should join; members may save “always use my main” or return to “ask every time”.
Hunt and Boss boards use vocation reactions. Quest and general Event boards use one open join reaction.
The event card marks the current organizer as Leadership, manually added characters as Invited, active Hunt positions as Main and overflow as 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 Hunt transfer is blocked if the new Leadership character would invalidate the shared-experience range for active members.

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

InvitationThe invited account is mentioned in the event thread with the selected character and the member who added it.

Final scheduleWhen a vote is concluded or automatic scheduling succeeds, the thread receives the chosen date, duration and decision context.

Time changeEditing an existing start time posts the previous and new schedule and mentions active participants.

CancellationActive participants are mentioned, the cancellation remains visible on the card and the thread is locked and archived.

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, Luminox checks the configured minimum or the Hunt's required Main composition. Community Tibia events 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. Universal general events use the active Discord participant list.

Created event10 Loyalty Points for the creator after the event reaches its official end, even when it is not successful, if Loyalty is unlocked.

Successful participant50 Loyalty Points for every qualifying Main participant when Loyalty is unlocked.

Successful LeadershipAn additional 100 Loyalty Points for the Leadership account when Loyalty is unlocked.

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

Outcome	What members see	What Discord keeps
Expired	At the official end, Luminox records the automatic result and adds `[X]` to the card and thread title. The card remains visible for 24 hours but no longer counts as active.	After 24 hours, the card is removed and the final-summary thread is locked and archived.
Cancelled	The card shows who cancelled it and remains outside the active count during its 24-hour visibility period.	Participants are notified and the thread is locked and archived immediately; cleanup later removes the temporary card.
Deleted	A confirmation step prevents accidental deletion.	The card and thread are removed immediately. Use this only for mistakes, not normal event history.

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.

Create, fill, run and archive events.