Hello
@Chase1011
There is something to mention, as it tripped me up for a little time when I first started.
There are commands we can issue all the time, as part of MQ2, then there are commands that come as part of a plugin (e.g. MQ2Cleric, MQ2Nav etc ), or in a macro (e.g. KissAssist ). The plugin must be loaded for its commands to work. KA macro must be started, for its commands to work. It may feel obvious, but honestly it tripped me up for a time.
CTWN plugin, (MQ2Cleric )
The term used with these family of plugins, is "mode".
mode 0, manual.
mode 1, assist
mode 2, chase assist.
You want to be using mode 1, for making a camp at the spot the command is issued.
KissAssist
/camphere
That is actually a command to change value of "ReturnToCamp", something that is defined in your characters KA ini file.
From watching Sic videos, there is a macro style that can be done and I picked up the following:-
Making Camp
/bcg //camphere on
//noparse /bcga //docommand /${Me.Class.ShortName} pause off
//noparse /bcg //docommand /${Me.Class.ShortName} mode 1
//noparse /bcga //docommand /${Me.Class.ShortName} resetcamp
Breaking Camp
/bcga //returntocamp 0
//noparse /bcg //docommand /${Me.Class.ShortName} mode 0
The above can be executed on one EQ window, and will send instructions to the other characters boxed via EQBC.
The long winded lines have /${Me.Class.ShortName} in them, so that the class is determined by the instance of EQ processing it.
if it was just a cleric then it could e done as /clr instead of /${Me.Class.ShortName}.
But the encouragement is to keep it generic, so can use the same command with any of the cwtn plugins, including cleric.
Key lesson- if it says not a valid command for /camphere, then KA is not running.