A feature-by-feature comparison for tribes coming from LogBot+ (Recca's AutoHotkey tool), with the honest differences.
LogBot+ was the tool for ARK: Survival Evolved tribes who wanted the tribe log in Discord. It was an AutoHotkey script that matched pixel colours on screen, paired with a NodeJS Discord bot and a Tempo music bot for sirens. Many tribes still search for it for ASA — so here is what carries over, what doesn't, and what ASA Tribe Log Bot does differently.
Feature map
| LogBot+ feature | ASA Tribe Log Bot |
|---|---|
| Tribe log → Discord with cropped picture | ✓ plus text embeds per event, colour-coded, raid-spam collapsed into ×N |
| Event filter: kill / death / sensor / tame / demolish / cryo / parasaur | ✓ 11 event types, each routable to an alert channel |
| Global chat pictures, tribe excluded | ✓ |
| Online members picture every N minutes | ✓ plus reads the x/y count |
| Screen check every N minutes | ✓ plus on parasaur |
| Sound alert via Tempo bot | ✓ native: the bot joins voice and plays a siren, no third-party music bot |
| @mention on N events within M minutes | ✓ same rule, plus always-on routing |
| Battlemetrics population | ✓ |
| Discord commands: mute, soundon/off, global/tribe chat | ✓ plus status, screenshot, siren test, timers (/baby, /tekgen, /forcefield) |
| Auto-reconnect with FindText per resolution | ✓ you capture the buttons once; works at any resolution |
| Pixel colour detection (breaks when blurred) | OCR + frame alignment — reads the actual text |
| Must be visible on screen | Reads the game window even when covered by other windows |
| License per device, register/deregister | ✓ 1 PC per license, release from the app or your account page |
The honest differences
- Setup. LogBot+ needed an AHK install, a NodeJS bot folder, Tempo in a voice channel, colour/shade tuning and a resolution profile. ASA Tribe Log Bot is one installer and four guided steps; the Discord bot and reconnect are optional extras.
- Reading the text. Pixel colours break with blur, HUD scale, or the ASA UI; OCR reads the words, so "was destroyed" is recognised as such even if a colour changes.
- Working on the same PC. Window capture means the game can sit behind your browser. LogBot+ needed the game in front.
- What's the same: you still need a client logged in with the Tribe Log open. No tool escapes that on official servers.
Switching
- Stop the AutoHotkey script and the NodeJS bot; you can delete Tempo from the voice channel.
- Keep your existing webhooks — paste the tribe log one into step 2 of the app, and the chat / online / screen ones in Extras.
- Re-select the regions once (drag boxes). There are no colour shades to tune.
- For the siren, create a Discord bot (free) following the guide; it replaces Tempo.
Questions
▸Does ASA Tribe Log Bot work on ARK: Survival Evolved too?
It is built and tested for ASA. ASE's Tribe Log panel is similar, and the region selection is manual, so it generally reads it — but ASE isn't officially supported.
▸Can I import my LogBot+ settings?
Webhook URLs and role IDs paste straight over. Regions and colour settings don't carry across — regions take 30 seconds to redo.