Let your server support multiple Yggdrasil verification routes!
Please note that the current plug-in is still in the beta version, and the English translation is incomplete
Description:
Code (Text):
Realize the coexistence of multiple Yggdrasil
Let your server support multiple authentication methods to log in to the game
Features:
- Support bungeecord server
- Repair skin problems under different validation
- Set the player's UUID in the game
- A white list system compatible with multiple verification login methods
- Block accounts with the same name
- Prevent malicious preemption of ID with the same name
- The account is limited to one login mode
Support:
Code (Text):
https://github.com/CaaMoe/MultiLogin/issues
Commands and permissions:
Code (Text):
Command Permission Description
/Whitelist add multilogin.whitelist.add Add target to whitelist
/Whitelist remove multilogin.whitelist.remove Remove target's whitelist
/Whitelist on multilogin.whitelist.on Open global white list
/Whitelist off multilogin.whitelist.off Close global white list
/Multilogin query [target] multilogin.multilogin.query Query how target (which can be an offline player) logs in to the game
/Multilogin reload multilogin.multilogin.reload Reload configuration file
multilogin.update Receive new version notification
multilogin.whitelist.tab Permissions required to automatically complete whitelist command parameters
multilogin.multilogin.tab Permissions required to automatically complete multilogin command parameters
papi:
- %multilogin_currentname% Player's current ID
- %multilogin_onlineuuid% UUID of player online
- %multilogin_redirecteduuid% Player's UUID in the game
- %multilogin_whitelist% Does the player have a white list
- %multilogin_yggdrasilname% The name of the Yggdrasil server where the player is located
- %multilogin_yggdrasilpath% Path of Yggdrasil server where the player is located
using:
Add a Yggdrasil server
Code (Text):
# The node name is the plug-in tag name. Once it is set, please do not modify it.
# The tag is used as the basis for the system to identify the user authentication server. Random changes will cause the system to be unable to verify the user's identity and be denied the login request.
# You can copy this node to add a new Yggdrasil authentication server.
demo:
# Enable the authentication server
# Closing will deny all players who log in using this verification to log in to the game
enable: false
# Basic attribute setting of yggsrasil server
body:
# Server type, can only be the following values:
# BLESSING_SKIN // Represents blending skin validation
# MINECRAFT // Represents mojang validation(only once)
# CUSTOM // Custom validation
serverType: MINECRAFT
# Verify the nickname of the server.
# Empty string is not allowed.
name: "Deom Yggdrasil"
# Yggdrasil authentication request url
# When the serverType is ‘MINECRAFT’,this node does not need to be set
# When the serverType is ‘BLESSING_SKIN’,just specify the Yggdrasil API address (for example, the URL of littleskin is:‘ https://littleskin.cn/api/yggdrasil ’)
# When the serverType is ‘CUSTOM’, You must specify a complete request url (for example:‘ https://example.com/yggdrasil/session/hasJoined?username=%s&serverId=%s ’, if it is a post request, complete the request url)
# The url request does not contain an IP address, please do not add it.
url: ""
# Verify account identity by post request
# This node is valid only if the value of the serverType node is'CUSTOM'
postMode: false
# Set the request content of post
# This node is valid only if the postMode node value is true
# The content does not contain an IP address, please do not add it.
postContent: '{"username":"{0}", "serverId":"{1}"}'
# Please set to false
checkUrl: false
# Set the player's UUID in the game, can only be the following values:
# DEFAULT -Use Yggdrasil to verify the online UUID provided by the server
# OFFLINE -Use offline UUID
# Please set and modify the node carefully to avoid increasing the mental burden of future maintenance.
# Invalid value is not allowed.
# recommended 'DEFAULT'
convUuid: DEFAULT
# Whether to set a separate whitelist for the current authentication server.
# This node is invalid when the global whitelist is true.
whitelist: true
# Sets whether skin repair is enabled on the current verification server
# This node is valid only if the value of the servertype node is not 'MINECRAFT'
skinRepair: false
# Sets the number of skin repair errors retries for the current validation server
# This node is valid only if the skinRepair node value is true
skinRepairRetry: 3
# Number of account verification error retries
authRetry: 1