PVP_PROPER
PVP_PROPER version 3, by Kuntz
Created using Bukkit 1.2.4-R1.0 (Build #1425)
Tested on CraftBukkit 1.2.4-R1.0 (Build #2126) (April 3, 2012) using Windows Java 6 update 31
Overview:
A simple and one-of-a-kind PvP mod for CraftBukkit. This should be fully compatible with other PvP mods!
- Tracks all facets of PvP interaction with painfully accurate matrices!
- Extremely fast code and systems. A worst-case scenario of 1,000 players attacking each other in a very small room will only take this mod a few milliseconds per server frame to track!
- No config or setup needed! There are no commands to use either! Just drop it and forget it!
Purpose:
I am sure you've played games like Call of Duty and Halo. These games don't just award kills to the player with the last hit, or assume someone who fell to their death was just committing suicide. These games track thousands of events per second and use the information to calculate who has actually killed who and how they went about doing it. Currently in MineCraft, if I push a player off a cliff to their death, the server simply says they fell to their death, and I would not be rewarded with a kill. What if I hit that player several times and they accidentally fell to their death? Again, the server would not award me with the kill. If I throw a bucket of lava on the ground and it kills someone some time later, again, no reward for the kill. The server really only thinks you kill someone when you get the last hit on them. If they are on fire, or drowning, there is a chance your last hit wont kill them, and the next tick of fire damage or drowning damage will! This is why PVP_PROPER was developed. It accurately tracks player interactions so kills can be rewarded to the players who deserve them!
Future Additions:
I am releasing the mod now in an early-release state that should be bug free. However the mod is far from complete and there are many new things I want to add! I'm doing an early release so server admins and players can give me feedback on what features and ideas they want implemented asap.
Change-log:
Version 3 - April 3rd, 2012 - Updated to latest RB. No other changes as of yet.
Version 2 - March 20, 2012 - 2 bug fixes.
Version 1 - March 19, 2012 - Mod released.
http://pastebin.com/sr293En5
Does it work on 1.3.2-R1.0?
So it currently doesn't do anything except track the data internally?
Can you just have it output the events to a simple text file? Or does it already do that? Even if its ugly (the text file), a super lightweight but still smart kill tracking system would be excellent to start from. :D
Does it work on 1.2.4-R1.0? :)
@kuntz
For now, it would be amazing to have a very functional death message system. Use your own creative ideas, but please do your best to provide a system as functional or more functional than HeroicDeath.
Eg. Randomized death messages and the ability to make your own in an easy-to-setup interface/configuration.
What I mentioned above is what I definitely hope you consider.
I am undoubtedly going to use this on my server :)
Keep up the good work!
@kuntz
This looks very functional and cool.
@xXReVurbXx
It does add death messages, I will post more info and screenshots today or tomorrow. It will allow admins to add as many death messages as possible, and if there are more than 1 for a specific kind of death, they will be round-robin randomly chosen!
It will also log kills & deaths, and could even implement an ELO rating system as well in the future. I'm thinking about supporting databases, at least mySQL ones.
Basically, stage 1 of this plugin is seeing what kind of interest there is in such a thing, all while building a good solid bug-free base. And then stage 2 is adding all the bells & whistles on top of that!
I actually love this idea! Finally something different and unique, hopefully extremely lightweight as well. I'm (slightly) confused of it's functionality, though- Does it add extra death messages? Does it log death/killer information?
That's what I'd like to know, because you mention all of the wonderful things your plugin can do but would only be efficiently used if another plugin were to hook into your plugin's API.
If it doesn't add death messages, you should definitely not hesitate to make it do so :)