Live watched-server cards
Each watched server gets a clean Discord status card with population, server state, labels, and alert context.
Obelisk Sentinel
Powered by Tribe Drop
Premium ASA PvP intelligence
Watch servers, track player IDs, route raid alerts, and give your tribe a clean Discord command layer before pressure turns into panic.
What it does
Obelisk Sentinel turns watched servers, player labels, and base events into readable Discord output. It is built for ASA PvP teams that need fast context, shared notes, and clean channels instead of scattered screenshots and guesswork.
Modules
Each watched server gets a clean Discord status card with population, server state, labels, and alert context.
Mark IDs, keep comments, search player history, and make server cards easier to read during pressure.
Highlight suspicious same-source movement, watched players, and customer-selected raid signals in the right channel.
Route important tribe-log and base-security events to Discord so the team can respond without staring at logs all day.
Premium tracking helps surface repeated shared-server and shared-timing patterns for better scouting decisions.
Use the customer panel to update watched servers, labels, alert roles, channel routing, and notification behavior.
Access
For tribes that want watched-server cards, player labels, raid signals, Discord routing, and setup support.
For teams that need deeper player history, more watched servers, advanced alert routing, and priority setup.
Setup
Purchase a license and bind it to the customer Discord.
Add the Discord app and activate the license.
Save watched servers, player labels, alert role, and channel routing.
Send a test alert and go live.
Obelisk Sentinel uses normal Discord app permissions and customer-approved setup. We do not ask for Discord tokens, Discord passwords, Steam passwords, or anti-cheat bypasses.
Customer panel
Enter your license key and Discord server ID to manage modules, watched servers, player labels, alert routing, and customer tests.
Paid customer controls
Validate a key and save settings to generate a customer-ready preview.
Choose what should surface in Discord.
Match named parasaurs and route detections into the server log channel with a trigger screenshot.
Track EOS, Steam, or short IDs and label them for customer Discord lookups.
Use this for a visible, customer-approved log source.
Normal delivery uses the Discord app and saved channels. Use this only as an optional fallback route.
For staff use. Keep admin token private.