Today we’ve done something unusual.
We’ve temporarily published a preview of our internal item telemetry dashboard — the same data we use as administrators to monitor and balance the server.
You can view it here:
👉 https://mirvengeance.com/item-admin/
Before anything else, let’s be clear:
This level of detail will not remain public once the server is live.
This is a transparency preview — a look behind the curtain — to show how Mir Vengeance is being engineered.
Most Servers Guess. We Measure.
Traditionally, private servers adjust drop files based on perception:
- “That item feels too common.”
- “This monster seems overpowered.”
- “Players say farming X is broken.”
That approach leads to instability.
Small tweaks compound.
Economies drift.
Inflation creeps in quietly.
We decided to do it differently.
Every item drop is logged.
Every pickup is recorded.
Every expiry is tracked.
Nothing is deleted.
Nothing is assumed.
We measure.
What Admin Can See
The internal telemetry dashboard allows us to analyse:
- Total items dropped over any time period
- Pickup rates per item
- Expired (unlooted) items
- Distribution by map
- Distribution by monster
- Circulation efficiency across the server
From this data, we can determine:
- Which items players ignore
- Which items are farmed heavily
- Whether a map is over-generating loot
- Whether items are circulating or stagnating
- Whether balance adjustments are actually working
This is not theoretical balance.
This is measurable balance.
Why We’re Showing It Now
We’re still in pre-launch development.
There’s no competitive advantage at risk.
There’s no live economy to protect yet.
So this is the perfect moment to show players what’s happening under the hood.
Once the server launches:
- Detailed telemetry will be restricted to admin use
- Only high-level public stats will remain visible
Balance integrity matters.
But so does trust.
We want players to understand that when we make adjustments, it won’t be arbitrary.
It will be informed.
Building for Longevity
Mir Vengeance isn’t being built as a short-term project.
We are migrating systems to SQL.
We are preserving full audit history.
We are instrumenting the economy.
We’re building infrastructure.
Because long-term stability doesn’t happen by accident.
It happens by design.