-
Notifications
You must be signed in to change notification settings - Fork 2
Setup
The jar latest jar file can be obtained from here
Older revisions are available from Github
The jar file should be placed in the <server-root>/plugins directory
This will give a warning that the server name has not been set.
This means that it has created the default setup file.
13:09:35 [INFO] [EventLink] EventLink initialized
13:09:35 [INFO] [EventLink-Default Log] [Serverport] Unable to open file: \<server-dir>\plugins\EventLink\eventlink.txt
13:09:35 [INFO] [EventLink] Unable to start server, server name not set
This is not strictly required, but is recommended.
EventLink uses the name of each world on the cluster as a routing target. Plugins which use EventLink can ask for a list of all worlds. However, if there are 2 worlds with the same name, then only one of them will appear in the list.
The Minecraft server calls the default world "world". This means that there would be lots of name collissions.
The name of the default world can be changed with a few simple steps.
- Stop the server
- open server.properties (or server.PROPERTIES in windows)
- Find "level-name=world"
- Replace with "level-name=NewWorldName" (where NewWorldName is the new world name)
- Rename the folder "world" as "NewWorldName" (if it exists)
Note: You must use a different port for players to connect and for the plugin to connect.
Open the file at
<server-root>/plugins/EventLink/eventlink.txt
You should get something like this.
server_name=
server_keys=keysserver
key_size=512
admin_list=
client_keys=keysclient
initial_time_to_live=10
cert_algorithm=SHA512WITHRSA
password=key_password
portnum=25365
algorithm=RSA
You need to give the server a name. This should be unique for all servers in the intended cluster.
If you are running multiple servers on the same machine, you need to give each one a unique port number. This should be different from the main server port number (25365 by default).
This is an updated setup file, with the server called first.server and the port number changed to 25364
server_name=first.server
server_keys=keysserver
key_size=512
admin_list=
client_keys=keysclient
initial_time_to_live=10
cert_algorithm=SHA512WITHRSA
password=key_password
portnum=25364
algorithm=RSA
The plugin should be re-loaded in order to use these changes.
Once you have set up a second server, you can link the two servers.
Log in to one of the servers with a player who has op permission and type
/eventlink add <hostname of other server>:eventlink-portnumber
For example, if the other server is on the same computer and is using port 25364 for the plugin, you would type
/eventlink add localhost:25364
If the process was successful, the reply should be
"Name-Of-Other-Server added to trust store"
You can confirm that the server was added using
/eventlink list
This will give the name and location of the server that was added.
Log on to the second server and use the same command.
If the first server was using 25365, then the command would be
/eventlink add localhost:25365
You can test if the link was successful with
/eventlink list
This should show the server, but with a * beside the name, indicating that the connection is active
You can test another server is connected using
/eventlink ping \<server-name>
In the previous example, you would type
/eventlink ping first.server
This should give a reply of "Reply received from first.server".
If the ping test is successful, it means that the plugin has been correctly setup.
The plugin is set to automatically reconnect when it is restarted. It uses a single SSL connection to the other server for all event transfers
If the servers are on different LANs, you need to forward the ports that the plugin uses on the LAN. The exact method to do this depends on your router.
If you have multiple computers on the LAN, you could just forward the port for one of them and have events for all other servers pass through that computer.