This update adds support for bStats. It also eliminates a spurious warning when entering end portals.

Wrong jar (1.1.5.1) was previously posted as 1.1.5.2

Non-functional change to remove annoying debug message that, ironically, is only created when debug messages are not enabled!

added one more useful debug message. Not needed for most usages.

This release supports debug and trace logging without have to put the server into debug mode.

Sometimes entities would not transfer through linked portals properly on paper servers (going to the default portal exit instead). This has been corrected.

If a player holds a compass in their off-hand when they enter a portal, they will be notified of their linked destination or the reason why they could not be redirected to a specific exit portal.

This update is only needed for those that have set the "strictLinking" configuration item to false and wish to link portals in the same world. There is a known issue with linking portals in the same world (that is, the entry portal and linked exit portal are in the same world) that causes entities to be destroyed instead of transported (SPIGOT-6782).

Until this bug is resolved, there will be a workaround that is enabled by default in which the plugin will cancel the portal activation and teleport the entity directly, doing its best to simulate portal mechanics including cooldown. This new workaround appears to be reliable. However, there may yet be differences in behavior in which the simulated behavior does not exactly duplicate what would happen had the entity actually used the built-in server algorithms for portals. This is unlikely to manifest during casual use, but may become an issue when used in high-performance farms that depend on very specific portal mechanics for proper operation.

* added support for Paper servers.
* added optional configuration for controlling the plugin's mechanics.
* should now cooperate better with other plugins that also manage item frame visibility.

WARNING: Due to a Spigot bug (also affects Paper) entities allowed to go through a portal linked to another portal int he same world will be lost. If you disable strictLinking in the config, you will probably want to enable the acls to prevent entities from using "same world" portals.

The plugin is now supported for general use.

• Reload and show commands added
• Supports use of item frames and glow item frames (previously had to choose one or the other.)
• Now supports strict linking by default (only portals naturally in range of each other can be linked). Can be disabled to allow a portal to be linked to any other portal.

If hideItemFrame is true in the plugin's config, then when a valid lodestone-linked compass is placed in an item frame, the item frame will be automatically hidden. When the compass is removed, the item frame will become visible again.

This change in visibility also serves as confirmation that the compass was acceptable for portal linking.