PlayerConditions v1.2.1

Details

  • Filename
    PlayerConditions.jar
  • Uploaded by
  • Uploaded
    May 22, 2015
  • Size
    52.90 KB
  • Downloads
    115
  • MD5
    0fdbaeb2261e83e1c028223327e89c59

Supported Bukkit Versions

  • 1.8.3

Changelog

Version 1.2.1

  • Changed timing of Vertigo sickness, so it's not a 100% chance as soon as you get over the specified y coordinate
  • Added a new condition, Thalassophobia. If submerged in water for too long, you slowly start to move slower and slower as exhaustion increases
  • The less air you have, the slower you will become and the harder it will be to swim (no config options as it's passive and will not kill players)
  • To recover from thalassophobia, just un-submerge from the water, and your slowness will clear over time
  • Added a zombified groan when players are infected

Version 1.2.0

  • Added a version sub-command (/conditions version)
  • Changed the zombie spawn upon death if infected. The zombie will now wear the armour you had equipped, and the item you were wielding
  • Added a new condition, Vertigo, which can be disabled in the configuration file
  • If a player is above the specifed Y coordinate, they are susceptible to Vertigo (nausea)
  • This new condition is not fatal, however will be very disorienting to the player and may cause them to move around in strange ways
  • Added a new condition, Food Poisoning, which can also be disabled in the configuration file
  • If a player eats a raw food, there is a 20% chance that they can become food poisoned
  • This condition is also not fatal, however low doses of poison, confusion, and slowness will occur

(There are no cures for Vertigo or Food Poisoning. They will subside over time)

Added 3 new configuration options for the new conditions. Please backup your configuration options, delete it, and let the plugin generate a new one

Version 1.1.2

  • Set the events in individual classes and packages. Should be faster response to crafting recipes / right clicking items
  • Added varying death messages for falling to the infected, and bleeding out
  • Separated many loops into different classes to further precise the accuracy of periodical damage, and lessen the memory usage on servers
  • General bug fixes, stability improvements, and decrease in memory usage

Version 1.1.1

  • Separated the commands in a commandExecutor class
  • Changed all "Bleeding>" messages to display "Condition" or "Conditions" instead
  • Conditions is now the main command instead of "/bleed" to easily individualize all future
  • Changed the structure of all the commands (view main page for information)
  • Fixed a few grammatical errors, and argument errors in the commands

Version 1.1.0

  • Separated many randomizations into separate classes. Will only be called when necessary
  • Added a zombie infection! If hit by a zombie, there is a 1% chance that you can become infected
  • If you are infected, over time you will take damage (much like bleeding). This can be disabled in the config
  • While infected, there is a 40% chance that every time you are injured you will become briefly nauseated. This can also be disabled in the config
  • Added custom death messages for bleeding to death, and for dying while infected
  • If infected upon death, a zombie will spawn on your death location
  • Added "Infection Cure" item. If right clicked, you will be cured from the infection
  • Added a new crafting recipe. "Infection Cure". Check main page for recipe
  • Added temporary placeholder blood particle effects when you are hit by a zombie (will change in the future)
  • Changed trajectory of blood particle effects to disperse more
  • Revamped the look of the configuration file
  • Added 4 new configuration options. InfectionsInflictDamage, InfectionPeriodicalConfusion, InfectionDamageDelay, and InfectionDamage

PLEASE NOTE THAT THE CONFIGURATION FOR THIS VERSION HAS BEEN COMPLETELY REVAMPED!!! PLEASE DELETE YOUR CONFIGURATION FILE AND LET THE PLUGIN GENERATE A NEW ONE! BACKUP CURRENT OPTIONS BEFORE DELETION

* This version was not tested before release, so bugs are possible. Please report them in the built-in ticket repository rather than the comment section. Bugs are much easier to track this way