Core

• Bump version to 2.16.0
• Compile against Bukkit 1.13 1.13.1 1.13.2
• Materials support - #2153, #2204
  • Abstract ItemDb for items.csv backwards-compatibility
  • Remove IDs from /itemdb
  • Remove item ID fallbacks in permission checks and config files
  • New spawn egg materials
  • Ensure item spawn blacklist and kits work - #2170
  • Ensure all item names are available - #2172
  • Fix applying meta strings to items - #2204 (comment 1) (comment 2)
  • Add enum convenience methods
  • Improve item alias coverage
    • Automatically download the latest items.json during build with maven-download-plugin no
  • Convert signs from item IDs to item names automatically
• Update to Java 8 - #1922
  • Support Java 9 - #1896
• Evaluate command selectors support - #2102 not in 2.16.0
• Fix cross-world teleport safety - #2121 not until 2.16.1
  • Async teleportation/teleport safety (requires Paper API) not until 2.16.1
• Support new mobs

Modules

• Update AntiBuild/Protect to use item names - #2238

Command selectors will not be in 2.16.0.

Hi @md678685 - could you add Permission Node updates to this list? There will be some that need to be deprecated for 1.13.x servers based on the list I took from https://essinfo.xeya.me/permissions.php

essentials.build.break.[:datavalue]
essentials.build.craft.[:datavalue]
essentials.build.drop.[:datavalue]
essentials.build.interact.[:datavalue]
essentials.build.pickup.[:datavalue]
essentials.build.place.[:datavalue]
essentials.itemspawn.item-[itemid]
essentials.unlimited.item-[itemid]

Not sure which are still valid or will/should be invalid as the list hasn't been updated in a while. I did check each of the EssentialsX*.jar files for each of the plugin.yml and we're not listing them there for me to compare what's supported or not. Would be much easier on users if they were self-contained in the jars. I'm seeing many developers starting to do this with other plugins.

Full Permissions: https://pastebin.com/zUpxqbTf I've set the paste to never expire.
Thanks -Steve

@smmmadden I don't have any control over the unofficial permissions list page - that's run by @Xeyame.

Many plugins traditionally list permissions in the plugin.yml, but EssentialsX doesn't as registering them causes undesirable side-effects that interfere with EssentialsX permission handling, as well as creating an unnecessary maintenance headache.

@md678685 okay, so where is the official permissions list page and has it been updated? I just wanted to make sure that we cover perms as well as block changes that are in flight. :-)

@smmmadden There is the Essentials permissions reference and the list provided by Xeyame as a convenience to the EssentialsX community. EssentialsX does not currently provide an official permissions reference.

@md678685 - thanks, no sense in recreating another document then if its pretty current. So it comes down to what we're doing about these for the 1.13+ releases?
essentials.build.break.[:datavalue]
essentials.build.craft.[:datavalue]
essentials.build.drop.[:datavalue]
essentials.build.interact.[:datavalue]
essentials.build.pickup.[:datavalue]
essentials.build.place.[:datavalue]
essentials.itemspawn.item-[itemid]
essentials.unlimited.item-[itemid]
These are the only ones referring to data value and itemid's that are not valid for new releases (for everything anyway).

I found on my server that /spawner seems to be saying "Target block must be a spawner." when im looking at a spawner. maybe add that to the list.

@Warp8 Please open a separate issue for your bug report.