Autologin feature for UserLogin 2.12.1+ and NukeLogin 0.0.4+.

Here, the "main plugin" refers to the UserLogin or NukeLogin.

Suppose you have a proxy and three servers: lobby, survival and mini-games. The lobby server has the "main plugin" installed, and here (and only here!) players log in (or register) and teleport through portals to other servers.

Let's imagine that some player, BratishkaErik, joined the server, authorized on lobby, and went to the survival portal. Then, he decided to go to the mini-games server, but he needed to go via the lobby server:

• Without autologin support: BratishkaErik must log in manually as if he were offline on lobby the whole time he was on the survival server. This can be annoying for some players.
• With autologin support: BratishkaErik logged in automatically as if he were online on the lobby the whole time he was on the survival server. Player don't need to do anything and he can go straight to the mini-games portal.

Note that in the second scenario ipCache setting from "main plugin" config is not respected.

How to install

Jar-files

• Download "main plugin" and put it into plugins folder of your auth server.
• Download UserLoginProxy and put it into plugins folder of your Velocity 3 or BungeeCord proxy (not auth server!).

Configuration

• For "main plugin": enable autologin setting in config.yml:

bungeeCord:
  # ...
  autoLogin: true

• For this plugin: add backend server(s) (where "main plugin" is installed) to the auth-servers list in config.yml:

auth-servers:
  - 'lobby'
  - 'another_lobby'

Finally, restart servers. Now players will be logged in automatically when changing server to lobby or another_lobby.

Permissions and Commands

There are no permissions. There is only one command, /userloginproxy (alias /ulp), that re-reads config.

License

This plugin is licensed under "GNU GPL v3 or later" license. Release jars includes relocated DazzleConf 1.2.1, which is licensed under "GNU LGPL v3 or later" license.