

Connect multiple Rust servers together and have your players travel between them in fun ways using events!
This plugin allows you to synchronize player inventories and stats, event containers, and much more to come!
Please use the Discussions tab to recommend suggestions, as I am very open to implementing your great ideas for everyone to enjoy!
NOTICE: This plugin does not automatically reconnect you to other servers as Rust's Nexus system is not released yet.
You'll be notified that you must type in the connect command leading the IP and port of the server you've been transferred to.
Try before you buy it!
connect germany.mikehawke.co.uk:29015
[ ! ] PLEASE KEEP IN MIND THAT CERTAIN SERVER HOSTS DO NOT ALLOW YOU [ ! ]
[ ! ] TO IMPORT FILES/DLLS, WHICH THIS PLUGIN REQUIRES YOU TO [ ! ]
INCLUDED DLL EXTENSIONS REQUIRED
EVENTS
CH47 Transition Event
FRIENDLY & HOSTILE MODES
THIS EVENT REQUIRES BOTH INITIAL AND DESTINATION SERVERS TO HAVE AIRFIELD FOR IT TO WORK
The Chinook event carries you and another 12 participants over the seas. You'll be greeted by Jackie Chan and Jamie Lee, your border patrol officers which will assist you to have a save welcoming onto the server. Make sure you're not wearing any illegal items on you or you'll be marked hostile and will be immediately attacked.
The storage on the right in the picture can be used as luggage which can carry items that are coming with the Chinook onto the other server. On screen you'll find the directions on how to get yourself seated. Press [RELOAD] to open up the seating panel, and assign yourself onto whichever you're liking.
Cargo Ship Transition Event
FRIENDLY & HOSTILE MODES
The Cargo Ship event you're willing to infiltrate and use for transport is driven by scientists or has a peaceful visit in the server you're in, broadcasting its next travelling spot.
You got a luggage storage which can contain items you wanna carry from the other server in mass.
HOW TO INSTALL
srvs 1/3 is the connected and total amount of servers that are connected with eachother.
evnts 0 are the currently locally running events on the server.
arriv 0 are the currently local locally running arrival events, events that come from other servers.
hnshk valid this must be valid at all times, if the master server goes offline, the handshake becomes invalidated.
NOTE: The handshake between the master server and all the sub-connected servers must be synchronized. If the Master server goes offline, the sub-servers will be locked until the Master server is up so it can dictate where the players should go and the their activity being communicated.
To set your events up and running, so it all comes to life, follow these instructions:
NOTE #1: Scheduled events only get triggered if both the server an event is starting from and the server an event is going towards are valid and online / connected.
NOTE #2: Scheduled events are executed in random order.
CONFIGURATION
The entire plugin can be managed from one configuration file, which can be found in the config folder of the Master server when you've initially added the MultiverseMaster.cs script in the plugins folder (alongside the MultiverseCore.cs file). There can be defined only one server as being the master server. Highly advise to keep the ID of it to "master".
The MultiverseSlave.cs and MultiverseCore.cs both go in all the other servers' oxide/plugins folder.
This is a rundown on all the current settings you can have for the Master server:
"Sync": { "Interval": 120.0, "Time": true, "Weather": true }
The sync property is used by the Master server to synchronize the time and weather across all the servers. The interval is set to 120 seconds by default, which is what it is recommended.
"ScheduleTickRate (in seconds)": 60.0
Scheduled events ticking rate in seconds. It basically checks every 60 seconds if there's anything available to be triggered onto the server based on the cooldowns of existent scheduled events.
"Legend": { "EventTypes": { "0": "CH47 Friendly", "1": "CH47 Hostile", "2": "CargoShip Friendly", "3": "CargoShip Hostile" } }
The legend is read-only, is to help you to choose what events you'd like to use in your schedule list.
"Shared": { "FirstSpawnServerId": "master", "WipeDeadBody": true, "UI": { "ShowLogo": true, "ShowShadows": true, "Colors": { "ValueColor": "eee16f", "PassengersColor": "6faaee", "StatusColor": "ee6fbe" } }, "BorderPatrol": { "IllegalItems": [ { "ShortName": "bleach", "SkinId": 0, "MinAmount": -1 } ] }, "Schedules": [ { "SourceServerId": "myserver1", "DestinationServerId": "myserver2", "EventType": 0, "Cooldown": 30.0 }, { "SourceServerId": "master", "DestinationServerId": "myserver1", "EventType": 2, "Cooldown": 30.0 } ], "Servers": [ { "IsMaster": true, "Id": "master", "DisplayName": "Master", "Ip": "myip", "Port": 12345, "RconPort": 12346, "RconPassword": "legitpassword", "Settings": {}, "IsConnected": true }, { "IsMaster": false, "Id": "slave01", "DisplayName": "Slave #01", "Ip": "myip", "Port": 23456, "RconPort": 23457, "RconPassword": "legitpassword", "Settings": {}, "IsConnected": false }, { "IsMaster": false, "Id": "slave02", "DisplayName": "Slave #02", "Ip": "myip", "Port": 23456, "RconPort": 23457, "RconPassword": "legitpassword", "Settings": {}, "IsConnected": false }, { "IsMaster": false, "Id": "slave03", "DisplayName": "Slave #03", "Ip": "myip", "Port": 34567, "RconPort": 34568, "RconPassword": "legitpassword", "Settings": {}, "IsConnected": false } ] }
This portion of the config is being shared across all servers, just to stay up to date so you don't have to manually do anything onto the other servers.
COMMANDS
PERMISSIONS
UPCOMING
(c) Raul-Sorin Sorban — 2022
All rights reserved
Total number of downloads.
Total customers served.
Total number of files sold.
Total payments processed.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.