Commits on Aug 8, 2014
Commits on Jul 9, 2014
Commits on Jun 25, 2014
Commits on Jun 22, 2014
  1. Add damage modifier API in EntityDamageEvent. Adds BUKKIT-347, BUKKIT…

    Wolvereness committed Jun 2, 2014
    This commit adds API for the enchantment, armor, potion and other
    modifications to damage done to an entity. These damage modifiers are each
    editable editable via a getter and a setter. This addition allows for more
    accurate modification and monitoring of damage done to/by an entity, as it
    displays the final damage done as well.
Commits on Jun 3, 2014
  1. Rewrite BukkitMirrorTest

    Wolvereness committed Jun 3, 2014
Commits on May 14, 2014
  1. Change YamlConfiguration encoding styles.

    Wolvereness committed Mar 25, 2014
    On JVMs with UTF-8 default encoding, this commit has no change in behavior.
    On JVMs with ascii default encoding (like some minimal linux installa-
    tions), this commit now uses UTF-8 for YamlConfiguration operations.
    Because all ascii is valid UTF-8, there is no feature degradation or data
    loss during the transition.
    On JVMs with any non-unicode but ascii-compliant encoding, this commit now
    forces YamlConfiguration to escape special characters when writing to
    files, effectively rendering the encoding to be plain ascii. Any affected
    file will now be able to migrate to UTF-8 in the future without data-loss
    or explicit conversion. When reading files, YamlConfiguration will use the
    system default encoding to handle any incoming non-utf8 data, with the
    expectation that any newly written file is still compliant with the
    system's default encoding.
    On JVMs with any non-unicode, but ascii-incompliant encoding (this may be
    the case for some Eastern character sets on Windows systems), this change
    is breaking, but is justified in claim that these systems would otherwise
    be unable to read YamlConfiguration for implementation dependent settings
    or from plugins themselves. For these systems, all uses of the encoding
    will be forced to use UTF-8 in all cases, and is effectively treated as if
    it was configured to be UTF-8 by default.
    On JVMs with unicode encoding of UTF-16 or UTF-32, the ability to load any
    configurations from almost any source prior to this change would have been
    unfeasible, if not impossible. As of this change, however, these systems
    now behave as expected when writing or reading files. However, when
    reading from any plugin jar, UTF-8 will be used, matching a super-majority
    of plugin developer base and requirements for the plugin.yml.
    Plugin developers may now mark their plugin as UTF-8 compliant, as
    documented in the PluginDescriptionFile class. This change will cause the
    appropriate APIs in JavaPlugin to ignore any system default encoding,
    instead using a Reader with the UTF-8 encoding, effectively rendering the
    jar system independent. This does not affect the aformentioned JVM
    settings for reading and writing files.
    To coincide with these changes, YamlConfiguration methods that utilize a
    stream are now deprecated to encourage use of a more strict denotation.
    File methods carry system-specific behaviors to prevent unncessary data
    loss during the transitional phase, while Reader methods are now provided
    that have a very well-defined encoder behavior. For the transition from
    InputStream methods to Reader methods, an API has been added to JavaPlugin
    to provide a Reader that matches the previous behavior as well as
    compliance to the UTF-8 flag in the PluginDescriptionFile.
    Addresses BUKKIT-314, BUKKIT-1466, BUKKIT-3377
Commits on Apr 2, 2014
Commits on Mar 24, 2014
Commits on Feb 15, 2014
  1. Update data folder migration for spaces in plugin names. Fixes BUKKIT…

    Wolvereness committed Feb 15, 2014
    This change drops the previous plugin data folder migration based on the
    plugin's file name, and adapts the migration to now instead consider
    plugins that have spaces in their original name.
  2. Fix loadbefore, soft, and normal dependencies with spaces. Fixes BUKK…

    Wolvereness committed Feb 15, 2014
    This change makes the lists of loadbefore, softdependency, and dependency
    replace the spaces in the names with underscored to reflect the behavior
    used with names.
Commits on Feb 8, 2014
Commits on Jan 19, 2014
Commits on Jan 15, 2014
  1. Modify give command to support 1.7 features. Fixes BUKKIT-5286

    Wolvereness committed Jan 15, 2014
    Necessary additions include an interface to add internal value conversions
    that are inappropriate for proper API design. This acts as a substitute
    for properly formed, user-friendly commands in an effort to maintain
    relatively vanilla behavior.
Commits on Jan 6, 2014
  1. Fix some messages

    Wolvereness committed Jan 6, 2014
    Addresses BUKKIT-5272, BUKKIT-5282, and BUKKIT-5283
Commits on Jan 4, 2014
Commits on Dec 25, 2013
  1. Add method to get plugin by its class. Adds BUKKIT-5240

    Wolvereness committed Dec 25, 2013
    Currently, the only way to get a plugin is by name or using a static
    variable. This adds two methods to get a plugin based on its classes,
    utilizing the plugin classloader.
  2. [BREAKING] Shift plugin initialization; Addresses BUKKIT-1788

    Wolvereness committed Dec 11, 2013
    This reverts commit ae4f1c0, restoring
    commit 27cb5e7 (mostly).
    Shared class loading was removed as an explicit feature in the plugin.yml,
    as all plugins implicitly share class loaders already.
    Some deprecated, internal functionality is now (package) private, namely
    some sections pointed out in 203de41.
Commits on Dec 15, 2013
  1. Pulling all pending Bukkit-JavaDoc changes

    Wolvereness committed Dec 15, 2013
    A special thanks goes to @aerouk for almost all of the changes found here.
Commits on Dec 11, 2013
  1. Add Location.setDirection(Vector). Adds BUKKIT-4862

    Wolvereness committed Dec 11, 2013
    This commit adds an additional method to Location to set the direction of
    facing. Included are a set of unit tests that ensure the consistency of
    getDirection and setDirection using a set of cardinal directions and
    arbituary data points.
    Javadocs were also added to pitch and yaw methods that explain the unit
    and points of origin.
Commits on Dec 1, 2013
Commits on Oct 15, 2013
  1. Fix format of 9cba5ff

    Wolvereness committed Oct 15, 2013
  2. Update maven compiler to 2.3.2

    Wolvereness committed Oct 15, 2013
    This change removes a redundant addition of source encoding and makes our
    compiler match the current maven default. This amends the commit
    Upstream issue
Commits on Oct 9, 2013
  1. Use simple multiplication for squaring. Fixes BUKKIT-4836

    Wolvereness committed Oct 9, 2013
    This change adds a method to NumberConversions for squaring and
    replaces uses of Math.pow(..., 2) with the new method for efficiency
Commits on Sep 11, 2013
Commits on Aug 28, 2013
  1. Deprecate magic values

    Wolvereness committed Aug 19, 2013
  2. Add source encoding to the maven compiler plugin.

    Wolvereness committed Aug 28, 2013
    This change adds the source encoding to the maven compiler plugin, which
    will strictly enforce build consistency on multiple platforms and address
    possible compilation issues on some of the source files. The source
    encoding unintuitively is system-specified by default.
Commits on Aug 6, 2013
  1. Add ConfigurationSerializable-Serializable compatibility. Adds BUKKIT…

    Wolvereness committed Apr 25, 2013
    This commit adds a comaptibility layer for use between
    ConfigurationSerializable and Java Serializable, such that when using the
    Bukkit object streams, any ConfigurationSerializable acts as if it
    implements Serializable for purposes of that wrapped stream.
    Included are a set of unit tests for the stream with a check for backward
    compatibility across versions.
  2. Relax generic types for ConfigurationSerialization

    Wolvereness committed Apr 25, 2013
    The method signatures are unnecessarily strict for the generic signatures.
    This change may cause a compile-time error for extending classes overriding
    methods, but no byte signature or compile time call signatures change.
Commits on Aug 3, 2013
  1. Use player as point of reference for min volume. Fixes BUKKIT-4640

    Wolvereness committed Aug 3, 2013
    When the minimum volume is being used because the distance is over a
    threshold, the unit vector delta should be added to the player's
    location, instead of where the command specified location.
    This change makes the player's location the point of reference for
    playing sounds when distance to volume scale is lower than minimum
    specified volume.