PVP Stats 1.4.18

Keep track of your users' PVP Actions - MySQL or SQLite recommended!

  1. SLiPCoR
    Native Minecraft Version:
    1.13
    Tested Minecraft Versions:
    • 1.8
    • 1.9
    • 1.10
    • 1.11
    • 1.12
    • 1.13
    • 1.14
    • 1.15
    Source Code:
    https://github.com/slipcor/PVPStats
    Contributors:
    ChrisLane
    You want to keep track of your users' PVP actions? There you go. Drop the jar into your plugin folder, restart the server, change the config, restart - done!

    >> download for 1.7 and earlier <<

    This plugin features saving of kills, deaths and killstreaks to a configurable database, simple as that:

    Table name: pvpstats
    Colums:
    • name
    • kills
    • deaths
    • streak
    • currentstreak
    • elo
    • time

    Table name: pvpkillstats
    Colums:
    • name
    • kill
    • time
    That's the basic equipment you need to display the PVP experience of your players. PVP Stats will create the databases for you! You just need to setup the database connection/settings in the config

    Commands:
    /pvpstats - show your pvp stats /pvpstats [player] - show player's pvp stats
    /pvpstats [amount] - show the top [amount] players (K-D)
    /pvpstats top [amount] - show the top [amount] players (K-D)
    /pvpstats top [type] - show the top 10 players of the type
    /pvpstats top [type] [amount] - show the top [amount] players of the type
    /pvpstats cleanup - clean the database of multi entries
    /pvpstats debugkill [attacker] [victim] - manually insert a kill for debug purposes
    /pvpstats migrate [from/to] [yml/sqlite/mysql] - migrate from/to a different database implementation
    /pvpstats purge [amount] - purge KILLSTATS entries older than [amount] days
    /pvpstats reload - reload the config
    /pvpstats wipe [player] - wipe the stats [for a player]

    Permission nodes:
    Code (YAML):

     pvpstats.cleanup
    :
         description
    : Ability to cleanup (remove entries with the same player name)
         default
    : op
     pvpstats.count
    :
         description
    : Permission to be counted
         default
    : true
     pvpstats.debug
    :
         description
    : Ability to debug
         default
    : op
     pvpstats.debugkill
    :
         description
    : Ability to add a debug kill
         default
    : op
     pvpstats.migrate
    :
         description
    : Ability to migrate
         default
    : op
     pvpstats.purge
    :
         description
    : Ability to purge entries older than X days
         default
    : op
     pvpstats.reload
    :
         description
    : Ability to reload
         default
    : op
     pvpstats.top
    :
         description
    : Permission to get global stats
         default
    : true
     pvpstats.wipe
    :
         description
    : Ability to wipe the stats
         default
    : op
     pvpstats.newbie
    :
         description
    : Permission to block being killed to be counted
         default
    : false
    Configuration:

    > Commented config since 1.3 < (GitHub)

    config before 1.3:

    Code (YAML):
    MySQL: true
    MySQLhost
    : localhost
    MySQLuser
    : [sql user]
    MySQLpass
    : [sql password]
    MySQLport
    : [sql port]
    MySQLdb
    : [sql database]
    MySQLtable
    : [sql table]
    MySQLkilltable
    : [sql kill table]

    SQLite
    : false
    SQLitefile
    : [sqlite file name]
    SQLitetable
    : [sqlite table]
    SQLitekilltable
    : [sqlite kill table]

    FlatFiletable
    : pvpstats
    FlatFilekilltable
    : pvpkillstats

    PVPArena
    : false
    checkabuse
    : true
    abuseseconds
    : -1
    tracker
    : true
    collectprecise
    : true
    clearonstart
    : true
    kdcalculation
    : '&k/(&d+1)'
    ignoreworlds
    :
    - doNotTrack
    eloscore
    :
      active
    : false
      minimum
    : 18
      default
    : 1500
      maximum
    : 3000
      k-factor
    :
       below
    : 32
       above
    : 16
       threshold
    : 2000
    msg
    :
      main
    :
      - '&cName
    : &7%n'
      - '&cKills
    : &7%k'
      - '&cDeaths
    : &7%d'
      - '&cRatio
    : &7%r'
      - '&cStreak
    : &7%s'
      - '&cMax Streak
    : &7%m'
    update
    :
      mode
    : both
      type
    : beta
    PVPArena: should pvpstats try to hook into PA?
    checkabuse: should pvpstats disallow scoring by killing of the same player in a row?
    abuseseconds: the amount of seconds after which the abuse check gets reset, -1 to never reset
    tracker: may pvpstats phone home to report that your server is using it?
    collectprecise: should pvpstats save each kill with timestamp? < This should be set to false if you don't use SQL - this data is never read internally or offered to any API
    clearonstart: should pvpstats check the database for duplicates on startup?
    kdcalculation: as stated in the config, this defines the calculation for the top X list, the following placeholders are possible:

    • &k - kills
    • &d - deaths
    • &s - current streak value
    • &m - max streak value
    ignoreworlds: a list of worlds that will not make kills count eloscore:

    • active: should we care about previous kills?
    • minimum: minimum score possible
    • default: default ELO score
    • maximum: maximum score possible
    • k-factor below: k-factor below threshold
    • k-factor above: k-factor above threshold
    • k-factor threshold: the border between the two k-factors
    New update config nodes in 1.0!
    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)
    Database options:
    • a MySQL database
      OR
    • SQLite installed
      FALLBACK:
    • YML Files (probably slow)
    Implementation:
    Webstats by Pandapipino (only works with MySQL)

    Placeholder API Player Placeholders:
    • Player based stats:
      • slipcorpvpstats_kills
      • slipcorpvpstats_deaths
      • slipcorpvpstats_streak
      • slipcorpvpstats_maxstreak
      • slipcorpvpstats_elo - the ELO score
      • slipcorpvpstats_ratio - the kill/death ratio
    • Top list stats:
      • 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 list statistics are:
      • kills
      • deaths
      • streak (maximum streak)
      • elo
      • k-d (kill/death ratio as defined in the config)
    Credits:
    • pandapipino for the idea :)
    Source: GitHub
    Phoning home

    To determine popularity and usage of PVP Stats, the server contacts my private server for information purposes. It sends your port, IP (for proper server counting), and the plugin version. That's it! If you want to disable that, set "tracker" to false in the config!
    ku3ntin, Valentina_pro and anemul like this.

Recent Reviews

  1. Narcox5
    Narcox5
    5/5,
    Version: 1.4.19
    Yes, we would get xpt for death and lose it, and if we had eg 10 xp we would lvl up, but if you look at the pvplevels plugins I mean something like this.
  2. FireSky1
    FireSky1
    4/5,
    Version: 1.4.19
    Hello! I have this plugin on my server, and the commands work. When i die or kill someone, the kills or deaths dosen't apear in my account. Please help!
    1. SLiPCoR
      Author's Response
      Please use the discussion, github issues or PM to get to me. There is no way that this review system brings proper bug discussion --- check the server log for errors and double check your config if the settings are proper. Please contact me in PM and pastebin your config
  3. anemul
    anemul
    5/5,
    Version: 1.4.19
    Thanks SLiPCoR. Only PVP Stats plugin I have ever used. Always been top notch. +++++++
  4. bulvar
    bulvar
    3/5,
    Version: 1.3.12
    /pvpstats = Player not found: Playername... what im doing wrong? …………………………………………….
    1. SLiPCoR
      Author's Response
      You probably did not kill anyone yet?
  5. Nrc0611
    Nrc0611
    5/5,
    Version: 1.3.11
    This plugin works perfectly for me on 1.8.8. Do not try to use the older version if u are below 1.13 just use the latest because the older version is broken. The plugin does not use any methods that don't exist in version 1.8.
    1. SLiPCoR
      Author's Response
      oh thank you for that heads up, I could not test this server version but I will update my pages to reflect that all MC versions should download the latest most updated version :)
  6. fabricio9898
    fabricio9898
    1/5,
    Version: 1.3.11
    [16:19:45] [Server thread/INFO]: [pvpstats] Enabling pvpstats v0.8.36
    [16:19:45] [Server thread/ERROR]: [pvpstats] MySQL disabled, plugin DISABLED!
    [16:19:45] [Server thread/INFO]: [pvpstats] Disabling pvpstats v0.8.36
    [16:19:45] [Server thread/INFO]: [pvpstats] disabled. (version 0.8.36)
    1. SLiPCoR
      Author's Response
      1) check the config for SQL settings
      2) you are not using the latest version
  7. shotcraft3x
    shotcraft3x
    5/5,
    Version: 1.3.11
    good plugin, good help from the creator, 100% recommended!---------------------------
  8. tdubz
    tdubz
    4/5,
    Version: 1.3.7
    Good plugin however PlaceholderAPI doesn't seem to be workng. Also a top kill page would be appreciated!
    1. SLiPCoR
      Author's Response
      For the top page see the command /pvpstats top

      For the placeholders please use the valid ones, they changed due to the dev telling me to use

      slipcorpvpstats_*
  9. Meekville
    Meekville
    5/5,
    Version: 1.3.7
    Great Plugin! Is there away you could add a top kill status page? also with a way to include placeholders for Holographic Displays, or to have it shown in signs, or even a GUI?
    1. SLiPCoR
      Author's Response
      Hey there :) there is a top kill command:
      /pvpstats top kills
      /pvpstats top deaths

      Not sure how to do the integration though --- there are placeholders with placeholder-API - maybe I will add some for the tops?
  10. kenairock
    kenairock
    4/5,
    Version: 1.3.6
    Amazing plugin thank you ♥
    just a question out of all of this!! I'll private message you.