Auth Actions

How to use the Auth Actions

Where to put the settings?

Open the file AuthSettings.yml, there you'll find the sections Before and After, those are executed before and after the authentication of the user.

How do I use an action?

The descriptions of the actions here have examples, but basically you add the identifier and the arguments with this format: identifier:arguments

Chat

Actions related to the chat

Chat Message

Description: Send messages to the user!
Identifier: msg
Arguments: Any text you want (Color codes and PlaceholderAPI is supported 😉).
Examples:

• msg:&aWelcome to my Server &b%player_name%
• msg:&aWelcome &b%player_name%&a. Remember to claim your kits with /kit!

Player Command

Description: Need to execute a command in behalf of the players? Such as /kit or /spawn? Use this action!
Identifier: cmd
Arguments: The command to be executed. Make sure to not include the slash "/", i.e. spawn, kit nooby, etc. (PlaceholderAPI is supported 😉).
Examples:

• cmd:kit nooby
• cmd:home

Console Command

Description: Execute commands in behalf of the console!
Identifier: console
Argument: The command to be executed. Make sure to not include the slash "/", i.e. say Hello, World!, sauth reload, etc. (PlaceholderAPI is supported 😉).
Examples:

• console:say Hello %player_name%
• console:broadcast %player_name% has joined our awesome server!

Movement

Actions related to the movement of the players.

Teleport

Description: Move your users around the worlds without extra plugins with commands and events.
Identifier: teleport
Argument: The world name and coordinates ({WORLD};{X};{Y};{Z};{YAW};{PITCH}).
Example:

• teleport:my_world;100.0;50;100.0;0.0;0.0

More info regarding the coordinates can be found at the SpigotMC JavaDocs

Server

Description: Send your users to another servers!
Requirements: BungeeCord Instance Configured
Identifier: server
Argument: The identifier of the server. You can find the identifiers in the config.yml file in your BungeeCord instance.
Examples:

• server:lobby
• server:rules

Last location

Description: Do you need to first send the users to the spawn and then back tho their last location? Use this action!
Identifier: lastlocation
Arguments:

• register: Register the user last location. (MAKE SURE TO RUN BEFORE THE back EVENT)
• back: Sends the user to the registered location if any. (MAKE SURE TO RUN AFTER THE register EVENT)

Example

Before:
  Register: # Before register actions
  - lastlocation:register # Here we register the last location
  # ... Here you can teleport the user
  Login: # Before login actions
  - lastlocation:register # Here we register the last location
  # ... Here you can teleport the user
After:
  Register: # After register actions
  - lastlocation:back # Here we send back the user to their the last location
  # ... Other actions
  Login: # After login actions
  - lastlocation:back # Here we send back the user to their the last location
  # ... Other actionss)

If you have essentials and the setting spawn-on-join enabled, make sure to disable it or the lastlocation action won't work.

Others

Those extensions doesn't have a specific category

Wait a sec!

Description: Wait a certain amount of seconds before executing another action.
Identifier: wait
Argument: The amount in seconds to wait before executing another action.
Example:

• wait:5

External Actions

This actions are provided by external plugins. If you want your action to be added create a ticket in our discord