Admin Guide
Configure and manage your guild's Respawns, Fixed Claims, announcements, and settings.
1 · Add & Edit Respawns
Respawns are the core of the system. Each represents a hunting location that players can reserve.
1
Go to Admin Panel → Respawns tab
Navigate to /admin and select the Respawns tab. You will see all configured Respawns with status, queue length, and code.
2
Click Add Respawn
Fill in: Respawn Code (short, e.g. DEM1), Name (e.g. Demon Respawn), Level Range, and optionally Allowed Ranks.
3
Save
The Respawn is immediately available to players on the Respawns page.
4
Edit or Delete
Use the Edit and Override buttons on each Respawn row. Force-delete cancels any active reservation.
Expected result
The new Respawn appears immediately in the Respawns tab and is available to all eligible players on the /respawns page.
Common mistakes
Using a code with spaces or special characters — codes must be short alphanumeric strings (e.g. DEM1, HYD2).
Setting Allowed Ranks when you mean to allow everyone — leave the ranks list empty to allow all ranks.
💡Choose a code that matches the Respawn name — DEM for Demon, HYD for Hydra. Makes Discord commands intuitive.
Respawn Codes
Every Respawn has a unique short code used by the Discord bot. Players type this in slash commands.
Demon RespawnDEM1
Hydra LakeHYD1
Dragon Lord LairDRG1
Crystal SpiderCRY1
Expected result
Players can use /claim DEM1 in Discord to reserve the Respawn without opening the web app.
Common mistakes
Duplicate codes — each code must be unique across all your Respawns.
Long codes — keep them 3–5 characters for quick bot command use.
💡Codes are case-insensitive: DEM1 and dem1 are the same command.
3 · Allowed Ranks
Restrict which guild ranks can reserve a Respawn. Useful for high-level areas reserved for senior members.
1
Edit a Respawn
Click Edit on a Respawn in the Admin Panel.
2
Select allowed ranks
Check the ranks that should have access. Leave all unchecked to allow every rank.
3
Save
Restriction applies immediately. Players with non-allowed ranks see a 🔒 Rank Restricted badge.
Expected result
Players with non-allowed ranks see 🔒 Rank Restricted on the card and cannot reserve or queue for that Respawn.
Common mistakes
Forgetting to run Sync Ranks after guild rank changes in-game — players will have stale rank data.
Locking every Respawn to senior ranks — leave some open for all ranks.
💡Run Sync Ranks from the Admin Panel header after any rank promotions or demotions in-game.
4 · Fixed Claims
Fixed Claims are recurring scheduled reservations. They block a Respawn for a player or team on set days and times.
1
Go to Admin → Fixed Claims
Navigate to /admin/scheduled to see all Fixed Claims with schedule, assignee, and status.
2
Click New Scheduled Reservation
Fill in: Respawn, assignee, days of week, start/end time, and timezone.
3
Set an optional end date
Add an end date for temporary reservations. Without one, it repeats indefinitely.
4
Manage active claims
You can Disable, Release, or Delete any Fixed Claim. Release makes the current occurrence available.
Expected result
The Fixed Claim appears in the calendar and all member Fixed Claims views immediately. During the window, the Respawn is locked for the assignee.
Common mistakes
Not setting the correct timezone — Fixed Claims display in each member's local time based on the timezone you set.
Creating overlapping Fixed Claims for the same Respawn — only one claim can be active at a time per Respawn.
💡Set an end date for temporary Fixed Claims so they expire automatically without manual cleanup.
5 · Announcements
Post guild-wide announcements for events, rule changes, maintenance, or any news.
1
Go to Admin → Announcements
Navigate to /admin/announcements.
2
Click New Announcement
Fill in title, message, type (Info / Warning / Event / Maintenance / Alert), and optional start/expiry dates.
3
Pin important announcements
Toggle Pinned to keep the announcement at the top of the page.
Expected result
The announcement appears on the /announcements page and, if Discord is configured, is also posted to the guild channel.
Common mistakes
Not pinning urgent announcements — non-pinned items are sorted by date and may be buried under older posts.
Not setting an expiry date for event announcements — they stay visible after the event passes.
💡Use Warning type for urgent notices (rank changes, rule updates). Use Event type for time-limited content.
6 · Configuring Discord
1
Go to Admin → Settings → Discord
Navigate to /admin/settings and select the Integrations tab.
2
Create a Discord webhook
In Discord: Channel Settings → Integrations → Webhooks → New Webhook → Copy URL.
3
Paste the webhook URL
Paste in the Webhook URL field and click Send Test Message.
4
Configure notification types
Enable or disable: reservations, queue events, announcements, and Fixed Claim reminders.
Expected result
A test message appears in your Discord channel. Queue and claim notifications are now delivered automatically.
Common mistakes
Wrong webhook URL — copy it directly from Discord's webhook settings, not the channel invite link.
The bot not having permission to post in the channel — make sure webhook permissions are active.
💡Send a test message before enabling all notification types to confirm the webhook is working.
Plans & Limits
TheGuildHub offers several plans with different feature limits. Your current plan is shown in the sidebar and Admin Settings → Billing.
Expected result
After upgrading, new limits take effect immediately. Extra Respawn slots and Discord integration are available without restarting.
Common mistakes
Tibia Coins transfer to the wrong character — verify the receiver character name before transferring.
Not submitting the payment form after transferring TC — the platform admin cannot verify without the form submission.
💡Screenshot your TC transfer in-game as proof in case of any payment questions.
Guild Branding
Custom branding lets you upload a guild logo and choose an accent color. Requires Guild Elite plan.
Expected result
Your guild logo appears in the sidebar and member profiles. The accent color replaces the default purple in highlights and buttons.
Common mistakes
Logo file too small — minimum 512×512px for sharp display on high-DPI screens.
Choosing an accent color too similar to the background — ensure sufficient contrast for readability.
💡Preview changes in both dark and light modes before saving.
8 · Audit Log
The Audit Log records all significant admin actions: respawn changes, announcement posts, Fixed Claim management, rank syncs, and overrides.
1
Go to Admin → Audit Log
Navigate to /admin/audit-log. Filter by action type or target.
2
Read the log entries
Each entry shows: actor, action, target, and timestamp.
ℹ️The Audit Log is read-only. Entries cannot be deleted. Use it to track who made changes and when.