# Troubleshooting the tracker

> What to check when Entropia Central Tracker records nothing, misses trade messages, or shows numbers that look wrong.

Source: https://www.entropiacentral.com/documentation/tracker/troubleshooting
Last updated: 2026-07-30

---

Almost every "the tracker is not working" report comes down to the chat log not containing what the tracker needs to read. Entropia Central Tracker does not talk to the game; it reads the log file Entropia Universe writes. If a line is not in that file, or is not in the expected shape, nothing downstream can recover it.

Work through these in order. See [getting started](https://www.entropiacentral.com/documentation/tracker/getting-started) for first-time setup.

## Nothing is being tracked at all

**Check chat logging is on in Entropia Universe.** If the game is not writing to disk there is nothing to read. This is the single most common cause, and it looks identical to the app being broken.

**Check timestamps are enabled in your chat settings.** This is the one that catches people out. Every line the tracker recognises has to start with a date and time, like `2026-07-28 14:32:05 [Globals] ...`. With timestamps switched off, the log still fills up and looks completely normal to you, but not a single line matches, so the tracker records nothing and reports no error. If logging is clearly on and you are still getting nothing, this is almost certainly why.

**Check the log folder you selected.** The path is stored once during setup. If you picked the wrong folder, or moved your Entropia Universe installation afterwards, the tracker is watching a file that never changes. Re-select the folder.

**Check the game is actually writing while you play.** Open the log file and confirm new lines appear as you play. If the file is not growing, the problem is in the game's settings, not in the tracker.

## Globals are recorded but nothing appears on the website

Check **Privacy Mode**. With it on, everything stays on your machine by design and nothing is sent to our servers. That is the feature working, not a fault. Turn it off if you want your globals to reach the site.

If Privacy Mode is off and globals still are not syncing, check that you are signed in to the tracker.

## Trade radar is empty

Trade messages are only read from the in-game trade channels the tracker recognises:

`#calytrade`, `#arktrade`, `#cyrenetrade`, `#nitrade`, `#rocktrading`, `#toulan_trade`

**You have to be joined to a channel in game for its messages to appear in your log at all.** If you have never joined `#calytrade`, nothing from it will ever be written to your log, so the tracker cannot show it. Join the channels you care about and the radar fills up.

Messages posted in other channels are not tracked, including society chat and private messages.

## Return percentage looks wrong

Return is calculated from what the log reports, and the log does not report everything.

**Markup is not in the log.** The game reports TT values. If you have not told the tracker what your gear and consumables actually cost, your spend is understated and your return will read higher than it really is. Set markup on your loadout.

**Check the session boundaries.** A session that was left running across a break, or started midway through a hunt, will not line up with what you think you are measuring. Return over a partial run is not meaningful.

**Enhancer breaks are deducted automatically** from the log, so those do not need entering by hand. Gear decay and ammo are read from the log too. What the tracker cannot know is what you paid above TT.

## Some events are tracked and others are not

Different event types come from different parts of the log:

| What | Comes from |
| --- | --- |
| Globals, HOFs, ATHs, discoveries, tiering, PvP sprees | The globals channel |
| PvP kills, damage, heals, loot | System messages |
| Trade messages | The trade channels listed above |

If one whole category is missing while others work, the corresponding message type is switched off in your in-game chat settings. Enable system and loot messages, and join the trade channels.

## A global was missed

Check whether it landed while the tracker was closed. It only reads the log while running, and does not backfill history from before it started.

Globals are also deduplicated on the server. If the same event is submitted more than once, whether by you or by several people who saw the same message, it is recorded once. Multiple submissions increase confidence in the record rather than creating duplicates, so seeing your global attributed correctly after someone else also reported it is expected.

## Still stuck

Note which of these you have already checked before reporting a problem, especially whether timestamps are enabled and which channels you are joined to. A log line that fails to parse and a log line that was never written look the same from the outside, and those two questions separate them faster than anything else.