TinyCommands adds a handful of small slash commands, much as the name would suggest. These commands can be used from the chatbox directly, or from macros, or with other plugins, but the ""intended"" usage is primarily from within macros.
TinyCommands uses a custom argument parser for its commands, allowing GNU-style boolean flags to be specified in the form -flags, where each individual letter is another flag being turned on. All commands support the -h flag to display their extended help message, including usage and a description. Other flags depend on the command in question.
TinyCommands also uses a custom command registration framework as an interface between itself and Dalamud, which the above-mentioned argument parser is actually a part of. Commands registered with this framework are often given aliases, which are hidden commands (not listed in Dalamud's /xlhelp or the plugin installer window) that are the same command as the "main" one, simply offering different names to use.
/ptinyhelp/thelppthelp
This command provides basic, general help when used alone, or can be given the name of a TinyCommands plugin command to display the extended help message for that command. The -h flag that all plugin commands accept is redirected to the same functionality as this command provides, so the two are exactly equivalent. You can also use /tinyhelp -h (or /tinyhelp tinyhelp to get extended help details about this command.
-a: display aliases for the given command(s) along with their help text
/ptinycmds/tcmds/ptcmds
This command lists all TinyCommands plugin commands, optionally with their aliases and help text. Each command listed is given with an approximate usage guide describing the arguments it expects to be given.
-a: include aliases for each command listed-v: include the extended (TinyCommands-specific) help description for each command (not recommended, long!)
/ifthen
The first conditional chat command implemented, takes a set of conditions to test in the flags and a command to execute if the conditions all pass. Technically, the "command" needn't be an actual command, since whatever text you provide AFTER the condition flags is simply treated as if you had entered it in the chatbox yourself. As a side effect of this, macro-only commands cannot be used, but manual-only commands can, so you can't use /wait but you can use /macrocancel.
If you do not provide any text to execute on success, a message will be printed to your local chatlog with the results of the test; if it fails, the first condition tested that failed will be reported, which is not related to the order of the flags you pass. If it succeeds, a message will be printed saying so.
-t: you have a normal target-T: you do not have a normal target-f: you have a focus target-F: you do not have a focus target-o: you have a mouseover "target" (see the<mo>chat placeholder)-O: you do not have a mouseover "target"-c: you are in combat-C: you are not in combat-p: you have a normal target and it is a player-P: you do not have a normal target OR it is not a player-n: you have a normal target and it is an NPC-N: you do not have a normal target OR it is not an NPC-m: you have a normal target and it is a minion-M: you do not have a normal target OR it is not a minion
/ifclass/whenjob/whenclass
The third conditional command implemented, takes as a first argument a comma-separated (NOT whitespace-separated) list of class/job abbreviations, which your current class/job will be checked against. If your current class/job is found in the list, the match succeeds. When not inverted, the test passes when the match succeeds; otherwise, it passes when the match fails instead. All remaining text after the first argument will be treated the same as with /ifcmd and effectively sent from your chatbox.
If you don't provide any text to execute, a message will be printed with your current class/job abbreviation. The colour will differ depending on whether the test was conisdered passed (green) or failed (orange), accounting for the -n ("not one of") flag.
-n: invert the test ("not one of the given jobs")
None at present.
The second conditional command implemented (can you tell the readme was written late?), works similar to both /ifcmd and /ifjob to test your GP. The particular comparison is specified by flag, and the GP threshold (if applicable) is given as the first argument. All remaining text is then sent from your chatbox.
As with both of the others, a status message reporting the result of the test is printed to your local chatlog ONLY if you don't pass any text to execute.
-l: less than (must pass threshold to test against as FIRST argument following flags)-g: greater than or equal to (must pass threshold like with-l)-c: at capacity (do not pass a test threshold)
/nop/null
Does literally nothing. There are no effects whatsoever. The sole purpose of this command is to allow using <wait.(delay)> when /wait is unavailable but you don't want anything to happen. If you don't use Macrology, you'll probably never use this.
None. Alternatively, anything that isn't -h, because it'll all be ignored anyway.
/ptimer/delay/pdelay
The first command ever implemented, to make a counterpart to the builtin /alarm command. This command takes a delay and an alarm name, calculates the (local) time that will come after waiting for the given delay, and creates a vanilla FFXIV alarm for that time with the given name. This allows you to set an alarm to go off after a certain period, rather than at a given time.
This command uses a variant custom parser (the original one implemented, actually) that also splits words, so if your alarm name contains spaces then you will need to enclose it in double quotes (") to work.
Fun fact: the inspiration for this command was that I wanted to easily set an alarm to go off when my tea was done steeping but didn't feel like calculating the time myself, so I made a way to simply run /timer 5m tea and be done with it.
-v: display the/alarmcommand that was generated, then run it-d: display the generated/alarmcommand, but don't run it
/echoerror/error
It works just like the builtin /echo command, but it sends messages on the "error" channel instead. The idea is to be used with this plugin's conditional commands so that an emote macro can warn you if you need to have a target but don't, for example. An actual implementation of that would be simple, and might look similar to this:
/macroicon Poke emote
/ifcmd -Tf /target <f>
/ifcmd -t /poke motion
/ifcmd -t /em prods <t> gently to get their attention
/ifcmd -T /error You must have a target (or focus target) to use this!
This example macro would effectively change the message for the /poke animation, and also prevent you from using it unless you have a target. It doesn't make much sense to prod the air, after all.
-p: display the error message with the plugin's usual prefix text, instead of as a "bare" message
/playsfx
It can be annoying to keep /echoing the <se.##> placeholders to find one you want to use for something, especially with the way it clutters up your chatlog. This won't save you from needing to change the ID each time, but at least now it's a single backspace and there's no output message. Unless something goes wrong, like using an invalid index.
None.