Releases: Dans-Plugins/Medieval-Factions
Medieval Factions 5.0.4
Medieval Factions 5.0.3
What's changed
- #1608 Fix faction chat incompatibility with EssentialsX chat
Medieval Factions 5.0.2
Medieval Factions 5.0.1
What's changed
- #1596 Don't re-create boss bars after accepting duels
- #1597 Use chat previews for formatting
- #1598 Fix wars displaying twice in some scenarios
- #1599 Add missing translations for flag list/set aliases
- #1602 Add missing translations for peace made notifications
- #1603 Fixed faction chat causing unverified chat kick issues
- #1604 Speed up dynmap updates on larger servers with name caching and building faction info less frequently
Medieval Factions 5.0.0
Medieval Factions 5 reimagines and reworks everything about Medieval Factions.
What's changed
- This build is functionally identical to 5.0.0-rc.7
- This is a complete rewrite of Medieval Factions so everything has received a fresh coat of paint since 4.6.x/4.7.x.
- Commands, permissions, placeholders, etc should mostly be compatible, though some things have changed, such as locks, roles, and force commands.
Upgrading from Medieval Factions 4
If you have a Medieval Factions 4 install, replace the Medieval Factions 4 jar with Medieval Factions 5.
On the next start, Medieval Factions 5 will detect the Medieval Factions 4 config and make a backup of all of the data in mf4_backup in the data folder.
It will then proceed to generate the new config file, and shut down the server.
At this point, you should configure your database, if you have one.
If you have MySQL or MariaDB database, this should look something like:
database:
url: 'jdbc:mysql://127.0.0.1/database'
dialect: 'MYSQL'
username: 'username'
password: 'password'If you do not have a MySQL database, you can ignore this, as the plugin will create an h2 file-based database in your server's working directory.
Start the server one more time, and the configuration and data from the Medieval Factions 4 backup will be migrated to your new Medieval Factions 5 install.
Medieval Factions 5.0.0 Release Candidate 7
What's changed
- #1593 Added mf.members permission default
- #1594 Fixed importing from Medieval Factions 4 sometimes failing when Multiverse hasn't yet loaded
What's a release candidate?
This build is feature-complete and has had some feature-testing by developers, but has not been fully battle-tested by servers.
It is likely there will be no changes and this build will be promoted to the full release, but we want servers to do a final pass to see if there are any critical bugs that we have missed. Therefore, we recommend this build for testing environments (unless you have already performed your own testing and are satisfied that everything works as you expect & the experience is better than Medieval Factions 4).
Upgrading from Medieval Factions 4
If you have a Medieval Factions 4 install, replace the Medieval Factions 4 jar with Medieval Factions 5.
On the next start, Medieval Factions 5 will detect the Medieval Factions 4 config and make a backup of all of the data in mf4_backup in the data folder.
It will then proceed to generate the new config file, and shut down the server.
At this point, you should configure your database, if you have one.
If you have MySQL or MariaDB database, this should look something like:
database:
url: 'jdbc:mysql://127.0.0.1/database'
dialect: 'MYSQL'
username: 'username'
password: 'password'If you do not have a MySQL database, you can ignore this, as the plugin will create an h2 file-based database in your server's working directory.
Start the server one more time, and the configuration and data from the Medieval Factions 4 backup will be migrated to your new Medieval Factions 5 install.
Medieval Factions 5.0.0 Release Candidate 6
What's changed
- #1592 Fixed gates preventing factions from being deleted
What's a release candidate?
This build is feature-complete and has had some feature-testing by developers, but has not been fully battle-tested by servers.
It is likely there will be no changes and this build will be promoted to the full release, but we want servers to do a final pass to see if there are any critical bugs that we have missed. Therefore, we recommend this build for testing environments (unless you have already performed your own testing and are satisfied that everything works as you expect & the experience is better than Medieval Factions 4).
Upgrading from Medieval Factions 4
If you have a Medieval Factions 4 install, replace the Medieval Factions 4 jar with Medieval Factions 5.
On the next start, Medieval Factions 5 will detect the Medieval Factions 4 config and make a backup of all of the data in mf4_backup in the data folder.
It will then proceed to generate the new config file, and shut down the server.
At this point, you should configure your database, if you have one.
If you have MySQL or MariaDB database, this should look something like:
database:
url: 'jdbc:mysql://127.0.0.1/database'
dialect: 'MYSQL'
username: 'username'
password: 'password'If you do not have a MySQL database, you can ignore this, as the plugin will create an h2 file-based database in your server's working directory.
Start the server one more time, and the configuration and data from the Medieval Factions 4 backup will be migrated to your new Medieval Factions 5 install.
Medieval Factions 5.0.0 Release Candidate 5
What's changed
- #1589 Log errors on power updates
- #1591 Make power decay slowly from power on logout rather than from max
What's a release candidate?
This build is feature-complete and has had some feature-testing by developers, but has not been fully battle-tested by servers.
It is likely there will be no changes and this build will be promoted to the full release, but we want servers to do a final pass to see if there are any critical bugs that we have missed. Therefore, we recommend this build for testing environments (unless you have already performed your own testing and are satisfied that everything works as you expect & the experience is better than Medieval Factions 4).
Upgrading from Medieval Factions 4
If you have a Medieval Factions 4 install, replace the Medieval Factions 4 jar with Medieval Factions 5.
On the next start, Medieval Factions 5 will detect the Medieval Factions 4 config and make a backup of all of the data in mf4_backup in the data folder.
It will then proceed to generate the new config file, and shut down the server.
At this point, you should configure your database, if you have one.
If you have MySQL or MariaDB database, this should look something like:
database:
url: 'jdbc:mysql://127.0.0.1/database'
dialect: 'MYSQL'
username: 'username'
password: 'password'If you do not have a MySQL database, you can ignore this, as the plugin will create an h2 file-based database in your server's working directory.
Start the server one more time, and the configuration and data from the Medieval Factions 4 backup will be migrated to your new Medieval Factions 5 install.
Medieval Factions 5.0.0 Release Candidate 4
What's changed
H2 database users
If you use the h2 (file-based) database and ran RC 2 or 3 on your server, you may have experienced a migration failure which prevented the plugin from starting up.
If this happened, I recommend restoring your database from a backup before you attempted to upgrade to RC 2 or 3.
If you do not have backups, deleting your database (by default medieval_factions_db.trace.db and medieval_factions_db.mv.db in your server root) will fix the issue but you will lose data.
If you do not have backups, experienced this issue, AND want to keep your data, if you have the technical know-how you can remove the "Duel participant locations" row from mf_schema_history.
If this is too complex for you to do, please seek support on the Dan's Plugins Community discord.
What's a release candidate?
This build is feature-complete and has had some feature-testing by developers, but has not been fully battle-tested by servers.
It is likely there will be no changes and this build will be promoted to the full release, but we want servers to do a final pass to see if there are any critical bugs that we have missed. Therefore, we recommend this build for testing environments (unless you have already performed your own testing and are satisfied that everything works as you expect & the experience is better than Medieval Factions 4).
Upgrading from Medieval Factions 4
If you have a Medieval Factions 4 install, replace the Medieval Factions 4 jar with Medieval Factions 5.
On the next start, Medieval Factions 5 will detect the Medieval Factions 4 config and make a backup of all of the data in mf4_backup in the data folder.
It will then proceed to generate the new config file, and shut down the server.
At this point, you should configure your database, if you have one.
If you have MySQL or MariaDB database, this should look something like:
database:
url: 'jdbc:mysql://127.0.0.1/database'
dialect: 'MYSQL'
username: 'username'
password: 'password'If you do not have a MySQL database, you can ignore this, as the plugin will create an h2 file-based database in your server's working directory.
Start the server one more time, and the configuration and data from the Medieval Factions 4 backup will be migrated to your new Medieval Factions 5 install.
Medieval Factions 5.0.0 Release Candidate 3
What's changed
- #1586 Make locks only apply to a single block
What's a release candidate?
This build is feature-complete and has had some feature-testing by developers, but has not been fully battle-tested by servers.
It is likely there will be no changes and this build will be promoted to the full release, but we want servers to do a final pass to see if there are any critical bugs that we have missed. Therefore, we recommend this build for testing environments (unless you have already performed your own testing and are satisfied that everything works as you expect & the experience is better than Medieval Factions 4).
Upgrading from Medieval Factions 4
If you have a Medieval Factions 4 install, replace the Medieval Factions 4 jar with Medieval Factions 5.
On the next start, Medieval Factions 5 will detect the Medieval Factions 4 config and make a backup of all of the data in mf4_backup in the data folder.
It will then proceed to generate the new config file, and shut down the server.
At this point, you should configure your database, if you have one.
If you have MySQL or MariaDB database, this should look something like:
database:
url: 'jdbc:mysql://127.0.0.1/database'
dialect: 'MYSQL'
username: 'username'
password: 'password'If you do not have a MySQL database, you can ignore this, as the plugin will create an h2 file-based database in your server's working directory.
Start the server one more time, and the configuration and data from the Medieval Factions 4 backup will be migrated to your new Medieval Factions 5 install.