REVAMPED | [1.8-1.17] GlobalExecute | Execute Commands On All Servers!

REVAMPED | [1.8-1.17] GlobalExecute | Execute Commands On All Servers! -----

A plugin which will allow you to execute a command on all servers connected to the BungeeCord.

Global Execute

Description

GlobalExecute will allow you to execute a command on a specific or all of the servers which MAY OR MAY NOT be connected to the BungeeCord (Proxy).

How does it work?

The resource consists of two parts.

1) Daemon - It creates a WebSocket server which listens on a port of your choice. The Daemon runs on your BungeeCord server. Soon, I will also make a Standalone Daemon available so you won't need BungeeCord compulsorily at all!

2) Client - Clients connect to the Daemon. This creates a network of Spigot Servers which can securely interact (execute commands) with each other. Client runs on your Spigot server.

The communication between clients and daemon makes the command execution possible on all clients.

Everything happens real-time! That means, the command is executed instantly, even if no player is online, unlike before.

Screenshots

Installation

The resource comes in the '.zip' format. The reason being, the plugin is divided into two jars:

1] GlobalExecute [Daemon-BungeeCord].jar :- You must put this jar inside your plugins folder of the BungeeCord Server.

2] GlobalExecute [Client].jar :- You must put this jar inside your plugins folder of the Spigot Server.

Then start all of your servers (BungeeCord and all Spigot servers) to generate all default configuration files. Then shut down the servers and start configuring as follows.

Configuration

The first thing you must do is to get a PORT that can be accessed publicly. On your Server Hosting Panel of BungeeCord, you need to assign an additional PORT. If you have hosted your server on a VPS, you may or may not need to do this step. You need to check that for yourself.

Once you do that, keep that PORT handy.

Configuring Daemon:

Instructions are mentioned as the comment inside the file itself.

Code (YAML):

# DO NOT SHARE THE VALUES OF THESE FIELDS WITH ANYONE

# PORT on which GE Daemon should listen
# It must be publicly accessible
# You may have to manually assign this port on your server hosting panel
# Make sure that this port is not already in use
PORT : 25560

# PASSWORD required for letting GE clients connect to this Daemon
PASSWORD : 'PASSWORD1234'

Configuring Client:

Instructions are mentioned inside the file too. But one thing specifically important is that you must configure the Client name such that every Spigot GE Client has a unique name. Otherwise, only one of all clients having same name will be able to connect to the Daemon.

Code (YAML):

# DO NOT SHARE THE VALUES OF THESE FIELDS WITH ANYONE

# IP Address of the server on which GE Daemon is running
# It is a string, so it MUST BE enclosed within single quotes ('')
# By default (127.0.0.1), it is a localhost address. So if both daemon and client are running on the same machine,
# you may not need to change it. Otherwise, set the same ip that you use to connect to the BungeeCord.
IP : '127.0.0.1'

# PORT on which GE Daemon is listening
PORT : 25560

# PASSWORD required for letting this GE client connect to the GE Daemon
PASSWORD : 'PASSWORD1234'

# Name of this GE client
# DO NOT have any spaces or you may run into problems
# It will be used as an argument to run a command specifically on this Spigot Server
# It must be unique over all other clients
# It is a string, so it MUST BE enclosed within single quotes ('')
NAME : 'server1'

# By enabling this setting, if there is no connection between client and daemon,
# the client will automatically attempt to establish a connection in every interval.
# Interval value is in seconds.
# You can limit the number of attempts.
# If you do not want any limit on attempts, set its value to -1.
auto-reconnect:
enabled : true
interval : 60
attempts : 5

Starting Servers

Make sure that your Daemon (BungeeCord) is up and running before your Client starts and attempts to connect to the Daemon. This can be achieved by making sure that you start your Spigot servers only after your BungeeCord server has started.

You can check the logs on console to see the status of connections. See the screenshots section.

Commands & Permission

These commands can be executed via both BungeeCord and Spigot. But Spigot commands can only be executed from the console.

/ge execute <server>|all <command without slash>

Executes a command on a specified client server or all client servers

/ge list

Gives a list of all client servers connected to the daemon on which commands can be executed

Permission (BungeeCord): gexecute.admin

Feel free to message me if you face any issue!

View on SpigotMC

Resource Information

Author:

----------

Total Downloads: 2,392

First Release: Dec 16, 2015

Last Update: Oct 2, 2021

Category: ---------------

All-Time Rating:

23 ratings

Version -----

Released: --------------------

Downloads: ------

Version Rating:

----------------------

-- ratings