Last updated
It's plug and play — add the jar to the server plugins folder and start the server.
By default the plugin stores data in an embedded H2 database, so no extra setup is required. To use a remote MariaDB database, set storage-method: mariadb and fill in the data section of config.yml.
Drop the PlayerDataHistory jar into plugins/ and start the server.
Set a unique server-name in config.yml so server-switch logs identify this server correctly.
A separate Velocity build is available for proxy networks (command /dhv). Install it on the proxy to record cross-server switches and sessions for the whole network.
Point every server/proxy at the same MariaDB database so all of them read and write the same history. H2 is per-instance and cannot be shared across a network.
Last updated