keronholidays.blogg.se - Liquidbounce donator

LIQUIDBOUNCE DONATOR CODE
LIQUIDBOUNCE DONATOR FREE

This includes but is not limited to:įilters have been implemented to deny any type of link that is unrelated to AAMC from being sent through. In the event that one of these rules are broken, a temporary mute will be issued, the length will depend on the severity of the offense. If you need to stop to think if your actions are moral, it is a good idea to not do them at all.įilters have been implemented to deny certain messages from being sent, however not everything is automatically moderated.

LIQUIDBOUNCE DONATOR FREE

This is your guarantee that the server is kept free of players who abuse loopholes in the rules.ĭon't be a jerk. The AutoAuxilium Management team reserves the right to modify any rule, or remove any* player from the network, at any time with no reason. Also note that nobody is more or less protected from getting punished if they are a donator, we value the safety and happiness of our community over their money.

Note that these rules are just guidelines on basic conduct, and staff are free to punish any player based on their own judgement whether the offense is listed here or not. Punishments have also been put in place, and staff will not hesitate to punish any player who decides to go against the rules. command, instance of the command to be unregistered.A set of rules have been put in place on all of our platforms, and they are expected to be followed at all times when interacting with others whether it be in-game, on discord, or on the forums.command, instance of the command to be registered.Registers the given command instance with the CommandManager. If a command with the given name is not found, null is returned. Returns an instance of Command with the given name. command, string containing the command to be executed.Įxample: commandManager.executeCommands(".killaura range 3.4").

Method summary commandManager.executeCommands(command) Again, only the most important methods are listed here, all of them can be viewed here. For this reason, similar methods are also defined on it. Similar to the ModuleManager, the CommandManager takes over the task of managing commands.

module, instance of the module to be unregistered.

module, instance of the module to be registered.

Usually the script API does this automatically. Registers the given module instance with the ModuleManager. Returns a List of all registered modules. ModuleManager.getModule("Scaffold").getValue("AutoBlock").get() Getting the value of a setting defined on another module ModuleManager.getModule("KillAura").getValue("Range").set(3.4) If a module with the given name is not found, null is returned.Įxample: // Changing the value of a setting defined on another module Returns the instance of Module with the given name. Method summary moduleManager.getModule(name)

LIQUIDBOUNCE DONATOR CODE

To view all methods, please refer to the source code of the class on Github. Only the most important methods are listed here. Furthermore it is possible to retrieve instances of modules to be able to perform further actions on them. With it new modules can be registered and already existing ones can be unregistered. The ModuleManager is, as the name suggests, responsible for managing all registered modules. Instead of listing all available methods and fields here, we refer to the Minecraft JavaDocs, which can also be found online here. It can be used to do almost any manipulation desired to the game. Mc contains the Minecraft instance ( Minecraft.getMinecraft()) It is the most important instance in every script.