Storage and networks
FastWorldLoader keeps templates either in this server's own folder or in a database shared by a whole network.
FILE (default)
storage:
type: FILETemplates are plugins/FastWorldLoader/templates/<name>.fwl, this server's own. Nothing to set up.
MYSQL — shared across a network
storage:
type: MYSQL
mysql:
host: 127.0.0.1
port: 3306
database: fastworldloader # the database must exist; the plugin makes its tables
username: root
password: ""
table-prefix: fwl_ # one database can hold several plugins or networks
poll-seconds: 5 # how often other servers' changes are picked up
properties:
allowPublicKeyRetrieval: trueWith MYSQL, every server using the database has the same templates:
- A template imported, saved or deleted on one server is on the others within
poll-seconds. Worlds already open keep the old template until they close; the next ones open from the new one. - Each server keeps the templates it read in
plugins/FastWorldLoader/cache/and downloads one again only when it changed, so opening stays as fast asFILE. - On the first start with
MYSQL, the templates intemplates/the database doesn't have yet are uploaded, and the files move totemplates/uploaded/.
Tested on MySQL 8.4 and MariaDB 11.4.
Mixed Minecraft versions
Servers of different versions can share one database. An upgraded template (old maps) is kept beside the original, per version, so a 26.x server's upgraded chunks never reach a 1.8 server. Only one server of a version upgrades a given template; the others use its result.
A template saved by a newer Minecraft than a server's can't be opened on that server (its chunks are too new) — edit maps on the oldest server of the network.
If the database is down
If the database can't be reached at startup, an error is logged and worlds open read-only from the templates this server downloaded last. Templates can't be changed until the next start that reaches the database; the server never fails to start over it.