🔍Log Lookup

Log Lookup indexes the logs your FiveM resources post into Discord, so staff can search months of history from a slash command instead of scrolling a channel. Staff can search by typing an exact term, or by describing what they need in plain English and letting the AI Assistant work out the search.

#How it works

You tell FiveUnity which channels carry your gameplay logs. From then on it reads every message posted there (including webhook and bot messages from any resource) and stores the embed title, author, description, footer and fields, plus the player's server ID when the log contains one.

When staff run a lookup, FiveUnity searches those stored entries and rebuilds each match as an embed that mirrors the original, with a Jump to message button back to the source.

Saving a channel for the first time also indexes that channel's recent history, so lookups work straight away rather than only covering messages posted from then on.

#Set it up

1. Turn on Log Lookup enabled.
2. Choose your Death log channels, Vehicle log channels, Inventory log channels, Other log channels, Tebex / gems log channels and Admin log channels. Each picker lists text channels from every server you can manage, not just this one, and each one also lists that server's channel categories: pick a category to add every log channel inside it at once. Other is for everything that does not fit the first three: money, banking, jobs and chat. Tebex / gems is for store and gem-shop webhook channels (Sheisty Tebex gems/cash, and similar). Admin is for admin-menu and staff-tool webhooks (kicks, bans, item grants, noclip, godmode, spectate, teleports) so you can find admin actions or track possible abuse. The FiveM bridge's own log channels (FiveM page) and Log Builder destinations join automatically; the bridge Admin log lands in Admin Logs. Official Tebex purchase channels from Core → Tebex are indexed too. The Tebex / gems and Admin pickers are on the dashboard only: /logs setup in Discord is already full.
3. Set Keep logs for (days), Plain-English search window (days) and Timezone under Storage and dates.
4. Press Save Log Lookup. The confirmation tells you how many past entries were indexed from any newly added channels.

Up to 50 channels can be selected per category. A category is expanded into its channels as you pick it, so what is saved is always a list of channels: a channel added to that Discord category later is not picked up on its own, and removing one channel does not remove the rest.

The /logs setup panel in Discord does the same job with select menus, and can pick up to 25 channels or categories per log type at a time. When a category takes a log type past 25 channels, the menu shows the first 25 as chosen and keeps the rest; the panel says how many there are in total.

#Searching in plain English

/logs find takes a sentence instead of a search term, and searches every category at once. It is the fastest way to answer "who killed Jimmy last night" or "where did the golden deagle come from", and the only way to search your Other log channels. When Log Lookup is on, it also indexes your Tebex purchase log channels (from Core → Tebex); searching those needs the tebex permission, the same node that gates /tebex itself. The FiveM log channels on the FiveM page (money, transaction, death, job, crime, inventory) land in Other Logs, and the bridge Admin log lands in Admin Logs, with no extra setup. Every Log Builder destination (including sheisty_tebex_gems and other gem/cash shop webhooks) is indexed too. Searches read Discord embed titles, authors, descriptions, footers and fields, not just the message text: that is where shop logs put the package, item and gem cost, and where admin menus put the staff member, action and target.

For abuse investigations (chargebacks, refunds, "bought then got the item twice", admin-menu abuse), Money trace, Tebex / gems trace and Admin action trace, /logs find widens automatically: it searches every category you are allowed to see, softens event-type words so they are not AND-matched onto one line, and reads up to 90 days (still never longer than retention). Asking "what did Bob purchase with gems" or "did the admin noclip" widens the same way even in Direct answer mode. Senior Admins hold logs.find and tebex on the default ladder so they can run those searches without Management.

#Modes

The mode option shapes the written answer:

Use Money trace for "where did Bob make his money", "who paid Jimmy", or any question about earnings, transfers, salaries and payouts. Use Tebex / gems trace for "what did Bob purchase with gems", "what has Jimmy bought in the shop", or any question about store packages and gem/cash-shop items. Use Admin action trace for "did Bob noclip", "what did the admin give Jimmy", or any question about staff-tool use and possible admin abuse. All three search every permitted category so the trail is not cut off at a category boundary.

An admin can pick a different default mode under Default answer mode on this page.

#Thinking

/logs find has a thinking switch. On, it runs that one search on the server's thinking model (AI Assistant → Thinking model) instead of the standard one: slower, but better at long multi-row trails. It only has an effect when thinking mode is enabled for the AI Assistant; when it is not, the reply says so and the standard model answers. The dashboard's Ask the logs panel has the same switch, greyed out while thinking mode is off.

/logs find question:who gave Bob the golden deagle

What happens:

1. The AI Assistant reads your sentence and works out what to look for, including the spellings your resources actually write. It knows that a "golden deagle" may be logged as WEAPON_GOLDEN_DEAGLE, so you do not have to.
2. FiveUnity searches your indexed logs for entries matching all of those things at once. That is what the other commands cannot do: they match any one term, so searching a player and an item returns everything about either.
3. The AI writes a short answer and points at the entries it used. Those entries are shown underneath exactly as they were logged, with Jump to message links, so you can always check the answer against the real log.

The same search is on the dashboard under Ask the logs.

#If the AI Assistant is not set up

/logs find still works. It falls back to a plain keyword search across every configured category and says so in the reply. You get the entries, just not the written answer.

Written answers need the Pro plan, a Gemini API key, and the data-use terms accepted on the AI Assistant page. Log entries are sent to Google to produce the answer, which is why the consent is required. See AI Assistant and Privacy and data.

#Searching for an exact term

When you already know the exact word to search for, the category commands are more direct:

All three take the same optional filters:

Your text is matched against the embed title, author line, description, footer, fields and the raw message content. A plain number of up to six digits also matches the player's in-game server ID.

Results are private to whoever ran the command, and are shown one at a time with ◀ Prev / Next ▶ buttons and a link back to the original message. The reply repeats the exact window it searched, so there is never any doubt about which day was used.

#Storage and dates

Housekeeping runs daily: entries belonging to channels you have de-selected everywhere are cleared out, so removing a channel actually frees the space.

The /logs setup panel shows the live picture: status, retention, timezone, the channel count per category, and the number of stored events with their approximate size and the oldest one kept. Its buttons let you enable or disable tracking, change Retention and Timezone, re-run Index History, or Delete Stored Logs. The Retention button sets the search window too, on the same form.

#How cross-Discord lookup works

Many communities post gameplay logs into a separate Discord log server and keep the main server clean. Log Lookup is built for that.

1. Select the channels where the bot receives the log messages; they may belong to another Discord server.
2. Save from the server where staff will run /logs find, /logs death, /logs vehicle or /logs inventory.
3. FiveUnity stores those channel IDs on this server for searching, and switches on collection in each source server.
4. FiveUnity must be present in every source server, and you must have Manage Server or Administrator there. Keeping a channel selected here is what controls which stored logs this server can search.

For example: while configuring your Main Server, choose #death-logs from your dedicated Log Server. Staff then run the lookup commands in Main Server, and FiveUnity searches the entries collected from that Log Server channel.

#Tips

#Related

• FiveM
• Install the bridge resource
• Moderation
• Permissions