Compatibility
Minecraft: Java Edition
Platforms
Supported environments
Links
Tags
Creators
Details
Chat History Tracker
This mod lets you keep your chat history in a format which keeps the original formatting and style, and keeps some extra actions.
Usage
Install the mod to have the chat activity tracked in a format which contains style information.
After installing the mod, run /chattracker update, to download the latest web ui.
To see the logs, you can run /chattracker web. Open the web page that has been linked in the chat to see your logs. The web page is only accessible to you, the page is hosted locally on your computer, no data about the log leaves your computer. To stop the server, run /chattracker stop.
On the webpage, you will see a file picker, and the log view.
In the file picker, you can open:
- any
.chatlogfile (the format that this mod creates). - also
.logfiles which are the files created naturally by the game (those files are less rich in data, but might be useful if you want to look at the chat history when you didn't have the mod installed).
There are also some options:
Show Info Category- Shows data like Minecraft version, profile info, disconnects, singleplayer/multiplayer joins.Show HUD Category- Shows the messages that the client sees and sends.Show System Category- Shows the messages that the client actually receives and sends to the server. This is going to be mostly the same as theHUDcategory, so this is disabled by default.Show Raw Log- If this is enabled, you will see the content of the.logfile without any processing on it. The default is disabled, where the entries will be filtered and slightly reformatted to be more consumable.
Note: In case of any mismatch of the latest README with what you see, it is most likely because you're running an outdated version of the UI. So this is another reminder to run /chattracker update every once in a while, for QoL features.
Data
The activity and chat logs are stored in a chat_history folder in your Minecraft instance folder. A new file gets made whenever you start your game, and no files get overwritten.
The following data is stored locally in those files:
- Game boot time
- Player username and uuid
- Minecraft version info
- Joining a singleplayer world
- Joining a multiplayer world (including ip)
- Disconnecting from a singleplayer or multiplayer world
- Any message you see in the chat
- Any message you receive from the server which might've been hid by the client
- This is typically the same as what you see in the chat, but might be different if the client applies styling to the message you see in chat.
- Whenever you send a chat message or command
- Both of what you type in chat, and then what actually gets sent to the server (which again, might be different if a mod on the client does extra processing)
How it works
When you run /chattracker update, the mod downloads the entire webpage to serve from https://cht.mods.epicpix.dev/static/serve.zip and stores it into config/chat-history-tracker-serve.zip.
When you run /chattracker web, the client starts a webserver on any port that is available. The mod serves the webpage from config/chat-history-tracker-serve.zip.
The zip additionally has a special /signature file, which contains the signatures for all files in the archive. The public key is directly embedded inside the mod. This makes it difficult to modify the archive manually without modifying the mod as well.
The page contains a /api/* route which handles all the requests in the mod itself, and any other request will look at a file inside the zip file and serve that instead.
The webserver additionally puts restrictions on what the page can actually do via a Content-Security-Policy. The value of this header will depend on the version of the mod, but currently this is default-src 'self' 'wasm-unsafe-eval' 'unsafe-inline'; sandbox allow-downloads allow-same-origin allow-scripts.
Those restrictions mean that the log viewer cannot send data to anywhere except its own page. Which means even if the serve.zip file was compromised and ended up trying to send logs to some bad actor, it would not be able to.
If you want to read .chatlog files, see https://gitlab.epicpix.dev/EpicPix/chat-history-tracker-tool

