MCdigr
MCdigr will be permanently shutting down its services on May 3 due to unforeseen circumstances. We greatly appreciate all of our users, and wish we could continue providing Minecraft stats for all. Keep on digging!
We dig your craft!
Notice
Since the plugin is still in it's beta phase, you MUST stay current to use our service!
About MCdigr.com
MCdigr.com tracks and stores a growing set of Minecraft statistics across servers. Server owners install our plugin, and any players that play on these servers will have their stats tracked. Server stats are tracked too!
By logging in to MCdigr.com, server owners can monitor and see their system's operation in many viewports that are synchronized and dynamically updating.
Our backend system is designed to scale with the incoming data. Our interface is sleek, simple, and well tested.
About MCdigr Plugin
The plugin collects statistics and sends the results every 1, 5 or 15 minutes to MCdigr.com. As a fail-safe for network congestion, the plugin implements a fault tolerance policy - it retains a server's stats locally for up to 24 hours.
Engineering the MCdigr plugin so that it does the heavy lifting without interfering with gameplay was a real challenge. Before our public release, we had relentlessly tested the plugin on a server that constantly had 150+ active players at any given time.
Configuration
Statistics collection can be controlled from config.yml. The default set is good enough for most people! You must download it after you add a server to mcdigr.com, and then add it the MCdigr directory in bukkit's plugin directory.
Each server has a unique code that is automatically inserted into your config.yml file when you download it. The plugin disables itself if the code is not there. To disable a statistic from being collected, simply remove it from the enabled list in config.yml.
Port 37996
Please have port 37996 open or the plugin will not be able to communicate with the MCdigr servers. While most Minecraft hosts allow all outbound connections, a few large hosts do block outbound ports by default. Contacting your host should quickly resolve this.
Tracked Statistics
- Active players Tracks the players seen in the last interval
- Block breaks Tracks who broke what (the type of the block destroyed)
- Block placement Tracks who placed what (the type of the block placed)
- Chat Tracks the number of chats, player and systemwise. This DOES NOT track WHAT is said!
- Death Tracks who/what dies
- Economy balances Tracks player balances, if you have Vault installed.
- Entities Tracks the total number of entities in all worlds.
- Entity explosions Tracks creeper, TNT, fireball and wither skull explosions!
- Kick Tracks who was kicked and when
- Login Tracks all login attempts (successful and not)
- Player experience level Reports a player's last known experience level
- Player time Tracks how much time a player spends on your server
- ServerInfo Records some environment info at start
- Tick rate Reports the average tick rate from the last interval
We value your suggestions and feedback!
@SirArky
currently using on 1.4.6 without any issues.
@codedonut
This problem is fixed in our upcoming release.
@SirArky
The current 20121127 build should be compatible with 1.4.6. We'll have a new release coming up soon, but are still testing it to ensure there are no compatibility problems going forward.
Hello,
When will this be ready for 1.4.6 CraftBukkit build?
Thanks, SirArkimedes.
@mcdigr
i keep getting this message
http://pastebin.com/ZRnXNjd3
running on the latest version of 1.4.5 R.0.3 since anything passed that has the new buggy api.
@spazmonkey777
@Ozelo
I found the problem. The fix will be in the next release.
Sorry to bother, but what could it be:
I recently signed up, and added the plugin and config to my server. Upon restart and lots of players logging in, I am getting this error when creepers blow up:
http://pastebin.com/kjWUX6T3
To be specific, it was happening when players jumped into our worldguarded mob arena and creepers were blowing up. But it seems to be involved with Essentials Protect.
@mcdigr
Ah, okay. Thanks.
I also sporadically get:
Which I understand just means it cannot read the server on that attempt. More pointing it out in-case it should not have this trouble occasionally.
Thanks for getting back to me so speedily :)
@zedadiaswick
Sender is what sends data, so that time is spent serializing and sending the data to mcdigr.com. Consider network latency, this doesn't look unreasonable.
@mcdigr
You are fast. Added some details to my post.
@zedadiaswick
Thanks for posting. A fix is in for the next release.
I am getting a lot of the following error in my logs:
Also, it seems MCdigr is doing more than I had expected. Using NoLagg's examine function, I get the following data back.
Total duration: 438.352 ms / 500 ticks Average duration: 0.877 ms/tick Event count: 4 Task count: 4 Plugin: MCdigr
and lists 'Task #27' as using the following within MCdigr:
Total duration: 436.894 ms / 500 ticks Average duration: 0.874 ms/tick Selected task: Task #27 Plugin: MCdigr Location: com.mcdigr.MCdigr.util.FeatureManager$Sender
Most other plugins are on less than 100ms, bar a few more resource intensive tasks such as LogBlock and the loading of chunks, making MCdigr third on my list. Is this normal?
@MrMime22
Would you mind including a bit of your logs surrounding the exception so that we could get some context to determine what's causing the conflict? If large, feel free to use our contact form or mail it as an attachment to the support address found on our site.
[SEVERE] Could not pass event EntityExplodeEvent to MCdigr v20121106-1615
@harryjamesuk
http://dev.bukkit.org/server-mods/mcdigr/files.rss
If possible, I'd recommend that you use easier version names (E.G: 0.1 or 0.01 etc...) as 20121106-1615 makes it a bit difficult for me to check if there's an update xD
@mcdigr
would rather you were busy than not doing anything!
Will keep an eye out for it.
thanks for the great work so far!
@TorgusAmorgus
The next release with major new features is forthcoming (together with the fix for the bug that you had reported). Can't make promises, but aiming at next Monday or Tuesday.
Next week will be a very busy week for us. Happy Digging!
@mcdigr
Do you have any idea when the next update will be?
@TorgusAmorgus
Thank you for bringing this bug to my attention. The next update will include a fix for this.