1. Welcome to LilyPad. Download the project, explore the forums, and create your own LilyPad network.


    If you use the software and enjoy it or have a question, or would like to contribute to the future of the software directly or through resources, please sign up and join our little community.

Usage Setting up an AllInOne JLilyPad Server

Discussion in 'Documentation' started by Coelho, Apr 20, 2013.

Thread Status:
Not open for further replies.
  1. Coelho

    Coelho Software Engineer Staff Member Administrator Maintainer

    This tutorial is obsolete. You should no longer be using JLilyPad server, but rather GoLilyPad.

    Concept

    The AllInOne server software can be used when your player count is not yet large enough to load balance, however you still would like to benefit from linking your individual Bukkit servers. It consists of the Proxy, Query, and Connect servers all compiled into one jar to make the process of setting them up and using them easier.

    Download
    You can download the latest build of the AllInOne software by clicking here. Please note that this build may not be stable, and you may want to select from an archive of previous older builds by clicking here.

    Starting it up
    To start the software, you will need to open a Command Prompt (or Terminal) and type in the command:
    Code (text):
    java -XX:+UseParNewGC -Xms512M -Xmx2G -jar Server-Standalone-AllInOne.jar
    You will see a message saying it has been started, however the console will be completely silent from then on. If you would like to stop the server, simply typing "halt" then enter will do so.

    Configuring it
    To use the software properly, you will need to configure it in the file allinone.conf. This configuration file will be shown in JSON contrary to the regularly used YAML, and may be difficult to comprehend at first. If you need assistance, you can learn about JSON more online by clicking here.

    The default configuratrion is:
    Code (text):

    {
      "proxy": {
        "bind": {
          "address": "0.0.0.0",
          "port": 25565
        },
        "outbound": {
          "address": "0.0.0.0"
        },
        "servers": [
          {
            "domain": "*",
            "server": "example"
          }
        ],
        "motd": "A Minecraft Server",
        "playerMaximum": 1,
        "authenticate": true,
        "throttle": 2500,
        "tabEnabled": true,
        "localeFull": "You seem to be already logged in",
        "localeOffline": "The requested server is currently offline. Try again later!",
        "localeLoggedIn": "You have logged in from another location",
        "localeLostConn": "Lost connection... Please try to reconnect",
        "localeShutdown": "The server is restarting. Please try to reconnect"
      },
      "queryTcp": {
        "bind": {
          "address": "0.0.0.0",
          "port": 5555
        }
      },
      "queryUdp": {
        "bind": {
          "address": "0.0.0.0",
          "port": 25565
        }
      },
      "connect": {
        "bind": {
          "address": "0.0.0.0",
          "port": 5091
        },
        "logins": [
          {
            "username": "example",
            "password": "example"
          }
        ]
      }
    }
     
    There are 4 different servers packed into the jar, being the Proxy, QueryTCP (minequery), QueryUDP (minecraftQuery), and Connect. Each have their own separate configurations.

    What they have in common
    • You can specify the bind address with an IP and Port. Please keep in mind that it being blank (in vanilla Minecraft) is equivalent to 0.0.0.0.
    Specific to Proxy
    • The outbound address will be what your proxy will connect from. Please keep in mind that it being blank (in vanilla Minecraft) is equivalent to 0.0.0.0, which will use your default address.
    • Servers will define which domain connects to which server. You are required to have a wildcard (*) which will act as a catch all.
    • Motd will be what shows in the minecraft client's server list. You can use color codes by using the symbol "&"
    • Player maximum defines the maximum amount of players allowed to connect to the proxy. If this is set at 1, it will be unlimited.
    • Authenticate is equivalent to Minecraft's online-mode. If set to false, it will become offline-mode.
    • Throttle is equivalent to Bukkit's connection-throttle within bukkit.yml.
    • Tab enabled will decide whether players can see other players within tab.
    • Locale messages will be shown when a specific error occurs on the proxy.
    Specific to Connect
    • Logins will define a username and password for each Bukkit server. All Bukkit Servers linked to this cloud are required to have a different username. If you are running your Connect server on a private network, it is safe to make the password empty.
    Connecting your Bukkit servers
    For information on connecting your Bukkit servers, you can find a page specific to that here.

    Video
    If you are having trouble understanding, you may want to watch this video which is a brief demonstration on setting up LilyPad. (Apologies for the echo ;o)


    All Done
    Your AllInOne server should be ready to go.
    Code (text):

    [LilyPad] build Unknown of AllInOne
     
    Have fun!
    Last edited: Dec 29, 2013
    • Funny Funny x 1
    • Friendly Friendly x 1
    • Useful Useful x 1
Thread Status:
Not open for further replies.

Share This Page