v1.11.33 - move to HTTPS for Updater [core update]

• v1.11.28 - allow to change default command behavior to show player's stats instead of a list of available commands - general.showCommands
• v1.11.27 - reload the plugin when changing the config via command, so that all settings actually take effect
• v1.11.26 - allow to set up streaks and commands "every X streak levels" - there can be only one logic so it will override the former version if activated
• v1.11.25 - add spacer line breaks before comments for readability [core update]
• v1.11.24 - someone pushed the wrong button [Documentation commit]

Quick addendum here;

the setting general.showCommands will stay as " true" for a while to account for backwards compatibility, as it has been the default for a while now. But I think that it would be much more handy and a more sturdy design to have a dedicated /pvpstats help command to show available sub commands, and have the old way of "falling back" to "telling players all the commands" only in niche cases.

Most end users probably just want to get their stats [no argument, or "show"] or another player's stats [as the argument, or "show player"] or the top players, easily doable with /pvpstats 10 for example.

I think this solution will be the preferred way of using the plugin.

prefixed messages used to be sent to players AND to console - oups!

v1.10.2 - improve world column check and support late loading of worlds, this should no longer throw around warnings and errors

A player statistic caching function I recently added was prone to spamming the console a lot - sorry for that!

Wow! For some reason I accidentally removed the hook - that was not supposed to happen!

There is some documentation about the API, I added an event to hook in and to cancel.

https://github.com/slipcor/PVPStats/blob/master/doc/api.md

this version includes a proper plugin.yml version. oups

This fixes a small but annoying bug only present in mySQL and only affecting the duplicate check. No player data should be affected.

v1.6.32 - Make some entries write-only for safety reasons

Sorry for all the latest updates, this is the first one properly fixing the newbie issue we had for a while now. Ffaen and I will be working on a proper warning system which will try to inform admins setting up the plugin why it is not working.

This is a short term attempt to deal with Permissions plugins handing out permissions too widely, breaking my backwards compatibility, and breaking the plugin's functionality for LuckPerm users for example who do not take away undocumented permissions.

Why would they, they do not know them

v1.6.16 - only write asynchronously to mySQL

• v1.6.15 - change the newbie permission to "pvpstats.nonewbie" to actually work like a permission, defaulting to "true"
• v1.6.14 - add async runnables
• v1.6.13 - move some database interaction to async thread

In the future, the newbie status is handled differently. Before, it was handled with a "restricting permission" pvpstats.newbie - some permissions plugins or setups caused issues because admins got ALL permissions. This is fixed now in a way that is backwards compatible:

pvpstats.newbie will continue to work for the time being, but you should change your permissions setup if needed, to give the people who are NOT newbies a permission pvpstats.nonewbie, which is given by default!

In the newbie group, you have to "take away" that permission. How you do this, depends on your permission plugin, I have seen "-" and "^" markings to remove a permission. Or set it to false via command

• v1.6.12 - add config setting to enable the newbie feature. for backwards compatibility this will stay "true" for a while
• v1.6.11 - add "flop_*" placeholders to display things like "most killed people" - "flop_deaths_..."
• v1.6.10 - format placeholder information and other list output by using existing language nodes
• v1.6.9 - add scoreboards - needs testing check the docs for info on how to set them up

In the future, the newbie protection will be safeguarded against greedy permission plugins. For backwards compatibility, this change is coming in two updates:

1) everyone already using the plugin will receive an update so eventual fixes they did still work
2) in the future the setting will default to "false" so you need to activate the newbie setting AND give newbie players their permission

The "flop" update adds a second way of adding placeholders. Next to "top_deaths_1" you can use "flop_deaths_1" - the former will show the player with the LEAST deaths on top, whereas the latter will show the MOST deaths on top.

I created a discord for my MC plugins, join it: click

These are the fixes of this build:

• v1.5.5 - Fix Updater throwing an error sometimes
  
• v1.5.4 - Prevent NPE when a player damages themselves

I have sent this to some people to test, and sadly have not had much feedback, so I will upload this but not have it auto update. Use with caution. It should not cause harm, it will work the same way it did before and it is backwards compatible AND old versions will be able to work again if this version fails. Good luck!

• v1.5.3 - Set specific values asynchronously
• v1.5.2 - Start preparing the assisting logic by adding last damage history
• v1.5.1 - Remove Cleanup Command
• v1.5.0 - Move all internal logic to UUIDs

• v1.4.19 - update the preloaded RAM player values when changing the database not by killing
• v1.4.18 - add placeholders for TOP lists, use with caution!
  
  Examples:

slipcorpvpstats_top_kills_head_5 - heading ("Top 5 Kills")
slipcorpvpstats_top_kills_1 - Top player entry ("1. SLiPCoR: 100")
slipcorpvpstats_top_kills_2 - Second player entry ("2. garbagemule: 70")
slipcorpvpstats_top_kills_3 - ...
slipcorpvpstats_top_kills_4
slipcorpvpstats_top_kills_5

valid things to put up there:

• kills
• deaths
• streak (maximum streak)
• elo
• k-d (kill/death ratio as defined in the config)

v1.4.17 - add new config for statistics, 'createOnJoin', defaulting to true

This affects non-SQL-servers. People can turn this off if they have a big server with many players and yet do not work with a proper database

Well this is unexpected but it was really easy to implement tab completion, and it works all the way down to bukkit 1.8

no other changes

the ratio placeholder is analog to the rest:

slipcorpvpstats_ratio

It seems that SQL stats databases never got the initial database entry - sorry for that - everything should work from now on

I think some SQL servers might have trouble updating the database if there are not kill stats present- this build should fix this!

I have not heard back from a tester, so let's just roll with it....

This stops an error where the database tries to recreate the world column on every server start. Thanks to VoxSolus for notifying me

In order to separate kills per world, I added a world column.

This does not affect the flatfile implementation. Changing this to include worlds would exponentially increase the file size.

If anyone really wants this please give me a shout.

Thanks to Drc-DEV for the pull and the almost complete second fixing pull. I took the liberty of fixing the remaining errors

What this update basically does is allow for player placeholders to show even if they are offline.

v1.3.3 - add warning if precise kill stat collection is activated, as these stats show up nowhere in the plugin or API

Yeah this was totally not an update that I pushed early because I messed up the plugin.yml version. No no no.

• v1.3.2 - address #15 and update kills and death for other plugins to get the current stats (e.g. placeholders)
• v1.3.1 - fix various weird issues with the config, causing all sorts of errors
• v1.3.0 - this will be the last rewrite for a while, a lot of classes have been renamed and a lot of JavaDocs have been added
• v1.2.1 - new command /pvp set [player] [type] [amount] to set specific player statistics

Sorry this has taken me so long but I really had issues while testing. Things worked on my end for whatever weird reason and testers had problems..

Also I am lacking testers. Spigot needs to add a DEV branch so I can have people test dev builds before I release broken builds.

OH yeah the config has been rewritten big time. I hope the comments make sense and everyone gets used to order

There are some more config nodes you will notice, for flatfile settings, so in case you do not have a database and no SQLite installed, the plugin will create YML files with the set file names.

I have been rewriting some of the internal workings obviously to support multiple database systems, I have been testing YML and SQLite as much as I can, literally every command - but as I do not have a proper SQL server I can not test THAT part. So plase be careful using this version.

It should be fine though

I fixed some more bugs about the updater and other things throwing errors.

Check your config for some new nodes to activate SQLite.

I am in the process of adding flat file support, for folks that don't want to even use SQLite but will have to deal with some hot YML action then.

This update silently fixes an Updater messup where it would never return valid updates and throw errors like crazy.

Use SQLite with caution. There is no migration to SQLite if you use mySQL!

The plugin will catch but display all errors, I can not test this myself very much because I am on my own, so good luck and happy hunting

This version bump looks like much but it just is there to qualify the move from legacy to 1.13 API. There has been a big change:

The updater works like in my other plugins now, you now have a config block like this:

update:
mode: both
type: beta

Mode case insensitively supports:

• off (fallback default)
• announce - announce updates to OP players when they join the server
  
• download - download updates automatically for the next reboot
  
• both - do both and simply inform players rather that the update will happen on reboot, rather than asking them to download

Type case insensitively supports:

• alpha - bleeding edge
  
• beta - fairly tested things
  
• release (fallback default)

I used the wrong identifier, now it should work!

This version updates the Placeholder API hook to a non deprecated version.

I am not running a setup where I can test this, so please give it a try. I have at least had verified that it no longer throws warnings or errors so it SHOULD work.

Fingers crossed!

thanks to Ken for pointing out a flaw in the code