-
Notifications
You must be signed in to change notification settings - Fork 515
Breaking Changes
ljacqu edited this page Jun 1, 2016
·
35 revisions
This page contains a list of breaking changes, i.e. of changes in AuthMe that may require plugin users to make adjustments.
Version | Description |
---|---|
5.2 (2016-05-29) | "Allow all commands if registration is optional" feature dropped |
5.2 (2016-05-03) | Force spawn settings are grouped together (settings should migrate automatically) |
5.2 (2016-02-19) | Command /converter has been moved to /authme converter |
5.2 (2016-02-14) | Some permissions have been moved outside of authme.player . Please see the list below. |
5.2 (2016-02-12) |
Settings.delayJoinLeaveMessages has been split up in more granular configurations. Your config file will update automatically, search for options with "delay" |
5.2 (2015-12-28) | PlainText is automatically change to SHA256 HashAlgorithm |
5.2 (2015-12-26) | Flatfile data source and converters to/from flatfile no longer supported. Use Sqlite. |
5.2 (2015-12-23) | Setting settings.restrictions.enablePasswordVerifier renamed to enablePasswordConfirmation
|
5.2 (2015-12-22) | email.html: Placeholders are like <playername /> , not <playername> or %playername% . (Template) |
5.1 (2015‑12‑05) | Changed permission nodes (up-to-date list) |
5.1 (2015-12-04) | Configurable text sent in email moved from config.yml to email.html |
5.1 (2015-11-27) | Bug fix: Using /authme register no longer changes the password to all lower-case |
A few permissions were moved outside of the authme.player
group. The reason was that assigning authme.player.*
to players also gave them VIP status (authme.player.vip
), for instance, which was undesired.
Old permission -> new permission
authme.player.allow2accounts -> authme.allowmultipleaccounts
authme.player.bypassantibot -> authme.bypassantibot
authme.player.bypassforcesurvival -> authme.bypassforcesurvival
authme.player.seeotheraccounts -> authme.admin.seeotheraccounts
authme.player.vip -> authme.vip