Introducing Mercurius! Stats and Analytics for Forge

16 posts in this topic

Mercurius has been around for a few months now, while we've been collecting data, testing, and in general doing our best to handle the immense amount of data that this community generates.

Today, we're announcing that Mercurius will be merged into the Forge installer and will be included by default with Forge from 1.11 forward.

What is Mercurius?

Mercurius collects data about your current client/player/server sessions and reports this back to our central stats server for processing.

Is there any personally identifiable data?

Absolutely not. Access logs have been disabled for the API ingest and your IP address is not stored with stats data. We have no way of knowing who a row of data belongs to.

What data do you transmit?

SessionID - Several versions of this exist, including a Client Session and a "Play Session". Generated when you start your client, and a unique ID generated when you start a world or join a server. Generated with random unidentifiable information.

InstallID - This is a unique ID given to a modpack installation, constant through the life of that installation.

Modpack - Name of the modpack you're playing (as indicated by the modpack developer)

Forge Version - The version of Forge you are running.

Java Version - The version of Java you are running.

Minecraft Version - The version of Minecraft you are running.

Start Time - Sent with Client start and Play Session start.

End Time - Sent with Play Session (not currently sent with Client exit)

Installed Mods/Versions - A one time packet sent with the information of all mods installed and their status (enabled/disabled) and their versions.

How often do you transmit data?

When starting the client, the initial packet is sent to stage the statistics data for your session. Upon starting a world, a similar packet is sent (you may make changes while in the client before starting a world). The client pings every 5 minutes to let us know that you're still connected and sending data. When you stop a world, a small STOP packet is sent to let us know you've exited your world.

The largest packet is the initial packets sent that include the modpack information. This should have little impact on your bandwidth, even after long and frequent play sessions.

Can I opt out?

Absolutely. You can opt out globally by turning the snooper settings off in Minecraft which sends information back to Mojang. Out of courtesy and respect, we've decided that this is something we will absolutely respect as well. Additionally, if there is certain information listed above that you would prefer not send us, you can opt out invididually. Because we value the reliability of our statistics, some options aren't available for you to opt out of indvidually, and do require you to opt out globally.

I have more questions!

Ask here! I'll be adding questions to this post as we go and I look forward to the feedback (good and bad).

Can we see the data?

The current front end for Mercurius is a bit bare, as we process stats and we roll up what we have, crank out new SQL statements, caching systems, etc, but you can see the current public iteration here: https://mercurius.minecraftforge.net/

We have a few more features that we're currently working on but until those are a bit more polished, we're holding off on making promises or announcing anything.

Also, the main page is in EARLY alpha, and some of the stats may not match up, as I'm pushing updates fairly regularly to make things more accurate. Also, taking into account opt-outs, etc, not all counts will be consistent across all fields.

Currently we're tracking specific modpacks that have included Mercurius, so these numbers will vary wildly as we roll out further.

Share this post

Link to post

Share on other sites

One of the main goals of this is to determine what Java versions are used by players. This will allow us to better determine what versions we should care about supporting.

If, for example, after we get a bit of data and we see like <1% is using Java 6, Forge will probably drop support for Java 6 reguardless of what Mojang does. Gracefully with a 'update your java here, or downgrade Forge' message but none the less. It will help us figure out what is best to move forward with.

Right now, the stats are extremely biased, as Mercurius is only in some FTB packs, and a couple personal packs. Most of which have other mods that force Java 8. We are working twards getting this packaged/installed with the normal Forge installer so that we can get the best dataset we can.

And I just want to reiterate that user privacy is of UPMOST importance to us in this project and we have taken great care to make sure no personally identifiable information is sent anywhere. As well as giving you all of the options we can to allow you to control either you even report things or not.

Share this post

Link to post

Share on other sites

Besides Java version and PC specs, what other data are you collecting?

*puts on tin foil hat*

PC specs are not collected. The only thing that's captured is the OS itself. Beyond that RAM allocation, mods and their versions. Unique session ID's are generated via PRNG and hashed. These are per game install and per game launch and never directly attributed to a user.

Recently Browsing

Posts

Currently, when I play on the forge profile, it doesn't save the world which I am playing on. I tried reinstalling Minecraft entirely, however that didn't work. I tried again on a superflat world (flew to a village and exited there) and it didn't save my position or my inventory. It worked perfectly on the unmodded profiles (or worlds).
What is happening?

Oh. I see your example.
Well, the problem I get when doing that is I get a run time error saying there is a conflict between my mod's config and itself.
It's as though it sees each of them as my mod, and doesn't allow duplicates of the same mod to have config.

Yeah I did.
Im asking for a solution to this in just a quick way. When I open the gui i have no rendered cursor, it only shows up when i move my mouse outside of the minecraft window and move it back in. Fix for this @diesieben07 problem.

Difficult to describe without screenshots, but I have too many options to put easily on one screen, so in all of my previous versions I split them up into 3 screens.
So when you click on Config the first thing you see is the choice of 3: "Coordinates Options" "Timer Options" or "Infopanel Options".
Clicking on "Coordinates Options" brings up a page of just those options, etc.
I implemented all this in 1.12 using the @config annotation system, which allowed this kind of structure (outer-level config, 3x inner-level configs)
I just don't see whether the new ForgeConfigSpec system permits you to do this.