currently, send-on-login only has 3 modes:
TO_FIRSTTO_EMPTIEST_SERVERRANDOM
I suggest adding a 4th mode, that is VIA_DOMAIN_NAME to send players to the server depending on which domain name they used to connect to the Velocity proxy, e.g.:
-
Player A connects to the Velocity proxy via the following domain name: survival-1.mc.abc.xyz and gets sent to the auth-1 server for authorization. Upon successful authorization, they will be sent to the survival-1 server as defined by forced-hosts in Velocity config or AuthMeVelocity's separate config file.
-
Player B connects to the Velocity proxy via the following domain name: creative-1.mc.abc.xyz and gets sent to the auth-1 server for authorization. Upon successful authorization, they will be sent to the creative-1 server as defined by forced-hosts in Velocity config or AuthMeVelocity's separate config file.
-
Player C connects to the Velocity proxy via the following domain name: lobby.mc.abc.xyz and gets sent to the auth-1 server for authorization. Upon successful authorization, they will be sent to the lobby server as defined by forced-hosts in Velocity config or AuthMeVelocity's separate config file.
-
Player D connects directly to the Velocity proxy by the IP address and gets sent to the auth-1 server for authorization. Upon successful authorization, they will be sent to the default server, e.g. lobby, or the last server that they played on previously (this could be done via LuckPerm's meta fields, also perhaps adding a command like /remember would be great to let people toggle this behavior).
currently,
send-on-loginonly has 3 modes:TO_FIRSTTO_EMPTIEST_SERVERRANDOMI suggest adding a 4th mode, that is
VIA_DOMAIN_NAMEto send players to the server depending on which domain name they used to connect to the Velocity proxy, e.g.:Player A connects to the Velocity proxy via the following domain name:
survival-1.mc.abc.xyzand gets sent to theauth-1server for authorization. Upon successful authorization, they will be sent to thesurvival-1server as defined byforced-hostsin Velocity config or AuthMeVelocity's separate config file.Player B connects to the Velocity proxy via the following domain name:
creative-1.mc.abc.xyzand gets sent to theauth-1server for authorization. Upon successful authorization, they will be sent to thecreative-1server as defined byforced-hostsin Velocity config or AuthMeVelocity's separate config file.Player C connects to the Velocity proxy via the following domain name:
lobby.mc.abc.xyzand gets sent to theauth-1server for authorization. Upon successful authorization, they will be sent to thelobbyserver as defined byforced-hostsin Velocity config or AuthMeVelocity's separate config file.Player D connects directly to the Velocity proxy by the IP address and gets sent to the
auth-1server for authorization. Upon successful authorization, they will be sent to the default server, e.g.lobby, or the last server that they played on previously (this could be done via LuckPerm's meta fields, also perhaps adding a command like/rememberwould be great to let people toggle this behavior).