You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per the title, please include a micro number in the version information in plugin.yml.
As things currently stand, people end up with bPermissions-2.12-DEV-all.jar on their hard drives and /bukkit:ver will tell them it's 2.12, but there is no way to know whether it is Beta 18 (the latest) or some other version, short of diffing JAR files. It would be preferable to identify the version as "2.12.18".
The lack of distinct identification of different betas is a significant obstacle to configuration management of our servers. If someone else came along and updated the JAR file, I probably would not notice.
The text was updated successfully, but these errors were encountered:
Per the title, please include a micro number in the version information in plugin.yml.
As things currently stand, people end up with bPermissions-2.12-DEV-all.jar on their hard drives and /bukkit:ver will tell them it's 2.12, but there is no way to know whether it is Beta 18 (the latest) or some other version, short of diffing JAR files. It would be preferable to identify the version as "2.12.18".
The lack of distinct identification of different betas is a significant obstacle to configuration management of our servers. If someone else came along and updated the JAR file, I probably would not notice.
The text was updated successfully, but these errors were encountered: