Correct commit to use in plugins that add support for PlaceholderAPI about placeholderapi HOT 3 CLOSED

Tags exist for 3.12, 4.0 and 4.1. Any future versions will also have tags attached to them.

from placeholderapi.

Nope, that commit is not version 4.0. Version 3.12 is likely what you are looking for if you don't want to work with the breaking changes. 4.0 is the complete rewrite to support more than player, annotation based object-method registration and more nifty stuff. Version 3.12 will be kept on the branch legacy-(3.12) for some time, for documentation and legacy support purposes.

To clarify: version 4.0 was SUPPOSED to be the update adding relational placeholders and forcing a breaking method change. However, a suggestion by dualspiral got me thinking about a more effective system to have more dynamic replacement. As such, I moved the then-existing 4.0 into 3.12 and undid it's breaking change, then completely rewrote the plugin, and called the new version 4.0. (Sorry for the confusion about this).

I will look into release tags for jitpack for both 3.12 and 4.0, and all future versions. Shouldn't be too hard to do so I will likely do it by the release of 4.0.

from placeholderapi.

Ok, thanks. Creating a tag/release is very easy: releases -> new -> pick right commit on right branch -> name the thing(v3.12) -> done!

from placeholderapi.