You are able to limit how often a player can perform a command. You can mix these criterias as you please.įor each of these, you are able to specify You are able to check, if the user meets a number of criterias. Is the user allowed to execute the command? In order to actually be executed, a few additional checks will occur. Note, that if no target is used, it will use the player executing, as the target. One for each member of the faction as the target. If multiple targets are specified (such as in the case, where you may use a faction as the target), it will run the command x-times. In your CommandEntry, you should lowercase it aswell. Ie, 'tp' and 'TP' and 'tP' and 'Tp' all resolves to 'tp'.

Key: playfield Note, that all commands are *NOT* case-sensitive (Everything gets lower-cased), to make it easier to use. i: 1 #At 2nd place, expect entityid, playerid, playername, steamid or clientid You can use this later in the command, such as to check what was typed in a certain spot, etc. You are additionally able to specify, what the data is 'temporarily stored as'. In the example, the playfield is not used as a target, so it will not try to execute it on the players on the playfield. Then it looks if there is typed a player, or a playfield (effectively). (In the example, it first looks if there is typed 'tp' or 'tpto'. You may repeat the pattern of (0) as many times as you want. You are additionally able to specify, wether you want to use what was typed as a target (if faction for instance, will run the command on all the online members of that faction) and if there should be a defaultvalue for it, if nothing is specified. You are able to set parameters as optional, to require additional conditions to be met (such as have to share origin with the executing player), that it have to be a 'whitelisted word' or 'not a blacklisted word'. You are able to look for a keyword (Such as 'tp' or 'tpto'), or you can decide to look for a 'thing', for instance items (id/name), a clients ID, the steamID of a person, an entityid (currently only playerIDs are supported, but it is planned when possible), a playerID (the entityid of a player), a playfield, a faction, an integer, a string, a boolean (true/false), a POI (ship or base) or a playername.

After the prefix, the actual command starts. (If optional, you could both type '!tp ' and '!cc tp '.

A command may be required to use the 'namespace' as defined in config.yaml. Immediatly after the prefix, the next position starts.

Icecream Screen Recorder 7.29 instal