Branded Logs: A Must-Have Mod for Modpack Creators
When you manage a custom modpack, troubleshooting player issues can quickly become a headache. Crash reports and log files often lack crucial context, forcing you to ask the same questions over and over: Which modpack version are you using? How much RAM is allocated? What Java runtime is installed? The Branded Logs mod solves this elegantly by stamping every game log with essential modpack and system information, eliminating guesswork and speeding up support.
What Exactly Does Branded Logs Do?
Branded Logs is a lightweight, server-friendly utility mod that enriches Minecraft’s log output with persistent metadata. Right after the game initializes, it prints the modpack name, its exact version, and a snapshot of the player’s hardware and software environment. This includes the operating system, Java version and architecture, and the amount of RAM allocated to the instance. The data is seamlessly woven into the standard log stream, so any crash report or log file automatically carries these details.
The concept draws heavy inspiration from the Log More Info mod, but Branded Logs focuses specifically on modpack identification and system profiling. It is built for modpack authors who need a reliable, hands-off solution to log enrichment.
Why Every Modpack Author Needs This
Imagine receiving a crash log from a player who says “the game won’t start.” Without Branded Logs, you’d have to manually ask them to check the launcher version, locate the instance settings, and report back. With the mod installed, the log itself tells you that the player is running your pack’s 2.7.1 release on Windows 11 with Java 17.0.8 and only 2 GB of RAM allocated—instantly pointing you toward a memory issue rather than a broken mod. This kind of clarity transforms your support workflow.
Moreover, Branded Logs prevents version confusion. If you maintain multiple alpha, beta, and stable branches, a log will never again be misattributed. The modpack name and version are printed in plain text, making it trivial to filter and categorize incoming reports.
How It Works Under the Hood
The mod scans for modpack metadata in a predefined order. Out of the box, it automatically reads information from several popular launchers without any extra configuration. If a supported launcher file is found, the modpack name and version are extracted and logged. For unsupported launchers or custom setups, you can provide a simple JSON configuration file—the same one used by the Better Compatibility Checker mod—and Branded Logs will prioritize that data.
This dual approach means you get maximum compatibility with minimal effort. The mod never alters gameplay, adds no new blocks or mechanics, and has zero performance impact. It simply observes and reports.
Supported Launchers and Automatic Detection
Branded Logs can automatically fetch modpack details from these launchers:
- CurseForge App – reads minecraftinstance.json
- Prism Launcher – reads instance.cfg
- ATLauncher – reads instance.json
- GDLauncher – reads instance.json
One notable exception is the Modrinth App, which no longer uses a profile.json file and therefore cannot be auto-detected. For any launcher not listed here, including Modrinth, you can still get full functionality by adding a bcc.json configuration file.
For those who prefer a streamlined mod installation experience, grabbing Branded Logs through a modern launcher like the foxygame.net launcher is especially convenient. This flexible platform lets you browse and download mods directly from its built-in menu, so you can add the utility to your pack without leaving the launcher interface. It’s a modern approach that keeps your entire modding workflow tidy and efficient.
Manual Configuration with bcc.json
If your launcher isn’t supported or you want to override automatic detection, you need to place a bcc.json file inside the config folder of your instance. The structure is minimal:
{"modpackName": "My Awesome Pack", "modpackVersion": "1.3.0"}
You can generate this file using the optional Better Compatibility Checker mod, or create it manually with any text editor. Branded Logs will always give priority to bcc.json when it exists, ensuring your custom labels take precedence over whatever the launcher might report.
Dependencies and Compatibility
Branded Logs has no hard dependencies and works on both the client and dedicated server. The only optional companion is Better Compatibility Checker, which can simplify generating the config file. The mod is designed to be dropped into any modpack for Minecraft version 1.16.5 and above (with Forge or Fabric support depending on the build) and will coexist peacefully with any other logging or diagnostic tools.
Real-World Benefits for Support and Development
Beyond immediate troubleshooting, the consistent log format helps with automated issue tracking. You can set up filters that parse logs for the modpack name and version, then sort reports by build number. This is invaluable during beta testing phases where rapid iteration happens. Players no longer need to remember which snapshot they installed, and you no longer need to decipher incomplete descriptions.
Additionally, knowing the exact Java version and RAM allocation in every log allows you to spot environment-specific problems early. If a particular Java update introduces a compatibility quirk, you’ll see it reflected in the logs of affected users without them ever realizing it.
Getting Started with Branded Logs
Adding the mod to your pack is as simple as dropping the JAR into the mods folder. No in-game configuration, no commands to learn. The next time a player launches the pack, the log file will contain a block of information similar to this:
[Branded Logs] Modpack: My Awesome Pack v1.3.0 | OS: Windows 10 (amd64) | Java: 17.0.8 (64-bit) | RAM: 4096 MB
From that moment on, every crash report, latest.log, and debug log will carry the same branding. You can ask players to send their logs with confidence, knowing the answers you need are already there.
Conclusion
Branded Logs is a tiny mod with an outsized impact on modpack maintenance. It removes the friction of collecting system details from players and banishes version ambiguity from your support tickets. By automatically injecting modpack identity and environment data into every log, it turns a chaotic stream of bug reports into a structured, searchable resource. Whether you’re maintaining a small private pack for friends or a public project with thousands of downloads, this mod deserves a permanent spot in your mods folder. Pair it with a flexible launcher and a simple JSON config, and you’ll wonder how you ever managed without it.