Releases: Dans-Plugins/Medieval-Factions
Medieval Factions 5.0.0 Release Candidate 2
What's changed
- #1584 Fix unlock cancel checking if the player is unlocking rather than locking
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 1
What's changed
- #1571 Add French translation
- #1572 Add German translation
- #1573 Add missing translations to break alliance command
- #1574 Use ints for power display
- #1575 Fix vassal power counting towards total when vassals have not accepted the request
- #1576 Prevent factions sending multiple vassalization requests to the same faction
- #1577 Remove locks from memory when the claim is removed
- #1578 Allow chest accessors to bypass land claims for locked blocks where they have access
- #1579 Add crop protection
- #1580 Fix /f info and /f power not suggesting players/factions when names are not typed with the correct case
- #1582 Make duels teleport players back to the start position when the duel ends
- #1583 Fix upserting a locked block not updating the version in memory correctly
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 Beta 8
What's changed
- #1570 Fix fresh installs of MF 5 failing to save missing language
What's missing
This beta does not have built-in translations for other languages yet. You can translate it yourself by creating a file in the lang folder and setting the language in your config.yml to the language tag. The full release is planned to have translations for French and German.
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 Beta 7
What's new
- Fix missing translations in British translation
- #1567 Allow the faction to be modified in the FactionCreateEvent
What's missing
This beta does not have built-in translations for other languages yet. You can translate it yourself by creating a file in the lang folder and setting the language in your config.yml to the language tag. The full release is planned to have translations for French and German.
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 Beta 6
What's new
- #1566 Supply faction ID to faction permission types when generating permissions for them
This update is mostly to support development for Currencies and other expansions.
What's missing
This beta does not have built-in translations for other languages yet. You can translate it yourself by creating a file in the lang folder and setting the language in your config.yml to the language tag. The full release is planned to have translations for French and German.
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 Beta 5
What's new
- #1556 Add a config option for allowing neutrality
- #1557 Make vassal chat include lieges
- #1558 Allow admins to configure the "Factionless" name returned by placeholders
- #1559 Add a delay on teleportation that is cancelled by taking damage
- #1560 Allow /f info to be used on other players and factions
- #1561 Allow /f power to be used on other players and factions
- #1562 Fix power decay
- #1564 Fix ally request not correctly replacing placeholder with faction name
- #1565 Fixed relationship conflict handling
What's missing
This beta does not have built-in translations for other languages yet. You can translate it yourself by creating a file in the lang folder and setting the language in your config.yml to the language tag. The full release is planned to have translations for French and German.
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 Beta 4
What's new
- #1554 Make permissions more extendable
- #1555 Legacy data import fails when chests have null accessors
What's missing
This beta does not have built-in translations for other languages yet. You can translate it yourself by creating a file in the lang folder and setting the language in your config.yml to the language tag. The full release is planned to have translations for French and German.
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 Beta 3
What's changed
What's missing
This beta does not have built-in translations for other languages yet. You can translate it yourself by creating a file in the lang folder and setting the language in your config.yml to the language tag. The full release is planned to have translations for French and German.
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 Beta 2
What's changed
- #1548 Fix permissions nodes for /f flag set and /f flag list in plugin.yml
- #1549 Add autoclaim permissions node to plugin.yml
- #1550 Set JvmName on data classes
- #1551 Set JvmName on events
What's missing
This beta does not have built-in translations for other languages yet. You can translate it yourself by creating a file in the lang folder and setting the language in your config.yml to the language tag. The full release is planned to have translations for French and German.
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 Beta 1
What's changed
This is a full re-write of Medieval Factions from the ground up. Everything has a fresh coat of paint, but everything you're familiar with should still be there.
There are a number of new features and systems that have been redone.
What's missing
This beta does not have built-in translations for other languages yet. You can translate it yourself by creating a file in the lang folder and setting the language in your config.yml to the language tag. The full release is planned to have translations for French and German.
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.