MacroQuest

From Raid Addicts Wiki
Jump to: navigation, search

Word up Front

Macroquest, or often referenced to as MQ2, is a fantastic tool to help you in game.
Mostly it is used for boxing, since it's the easiest program out there, that allows you to send commands to your box toons.
It can quickly get very detailed and extensive, but this guide is to act as a helpful "start-up" reference.
If you are going to be boxing, it is suggestible to use something like Wineq.
It is very easy to set up, and lets you work easier with multiple clients from the same directory.
If you want to do this, at the bottom of the page, the very last topic, is a "quick" explain on how to.

Ofcourse if you are already very formilar with it, this guide is probably not for you.
MQ2 can also be used in combinations with Keypress, but that is overall even more complicated to memorize / work with.
Keypress is something that allows commands to be used by pressing certain keys, like movement, or attacking.
If you are interested in using / learning that, please take a look here or here.
You can also use / build batch macro's, but this is even more complicated.
It would also require a minimal amount of knowledge regarding scripting this.

For this guide though, we are going to stick to the basics, and a little bit extra.
You can obtain MQ2 here, here, or here (server specific).
Make sure you download the version suited for the EQ client you are running!
There are of course tons of guides, info, and websites to be found on the internet with information regarding MQ2,
and with that in mind, this page is just a guide to get the basic info that is useful to start using it.

Also, in some cases there are several varieties possible, but in this guide I'll highlight the most simple ones.
When speaking of Macro's in this guide, it's a reference to the actions window socials page (default CTRL+O),
where you can customize 10 pages worth (120 macros in total) of macros.

Options that are going to be treated

Getting started

After downloading, extracting and installing it,
Best / easiest is to right click the rar file, select the option extract to <same name as the rar file>, then after that rename the folder to how you want it,
Cut and paste it to a proper place (it would be best to put it into your EQ directory since it sort of belongs together),
and then from inside that folder, right click the EQBCserver and MacroQuest2.exe files, and copy them to your desktop for easy access.
This is merely a suggestion, you don't have to do this!

EQBCserver is used to proces commands you are giving from your main (or currently played) character to your boxes / the rest.
EQBC means EverQuest Box Chat, or if you prefer to memorize as a more flowing name, EverQuest BroadCast.
Macroquest ofcourse takes care of the rest.

Before you start your EQ client, first run MQ2.exe and EQBC.exe.
Normally the IP set up in the MQ2Eqbc.ini file works properly.
Should it not work properly, you can set it up with your personal IP address.
If you do not know how to do this, find a way on your pc to open up the command prompt (CMD).
The way to open this, varies per windows version.
Once you do have it open, type in ipconfig and hit enter.
In there find the line : IPv4-address, and copy / type over that number in your MQ2Eqbc.ini file, which is located in the MQ2 folder.

Even if the default IP address works, you can change it to yours, it does not make any difference though.
For each following time, before you start up EQ, run MQ2 and EQBC first, that's all you have to do.
The above info is only needed for the very first use.

Plugins

MQ2 is dependent on plugins.
Plugins determine what commands you can pass to your boxes.
The more plugins you use, the more variety you have, but also the more unstable / buggy MQ2 becomes.
Do not worry though, before it actually starts to become buggy, you'll need to be using 20+ plugins,
or plugins that are simply incompatible (IE : downloaded from the internet).
One of the best websites to find detailed information per plugin, is MMObugs.
Overall you should not need that many.
To find out which plugins are loaded / active, in game, type in : /plugin list.
To load / enable a plugin, type the following : /plugin MQ2<plugin name>... /plugin MQ2melee
Here are the most used plugins :

  • MQ2Chatwind

This provides an additional chat window, that lists commands and events used in MQ2.

  • MQ2Autologin

This is to set up your characters automatically logging in.
This again is best to be used with a program like Wineq, to easily create multiple clients.
You have to manually configure autologin for each character.
Below is a copy/paste of the default information, and sections broken down into pieces.

[Settings]
KickActiveCharacter=1
InstantCamp=0
UseStationNamesInsteadOfSessions=1
UseINIServerList=1

[ServerList]

[Accountname]
Password=
Server=
Character=


This bit is default in the MQ2Autologin.ini file

[Settings]
KickActiveCharacter=1
InstantCamp=0
UseStationNamesInsteadOfSessions=1
UseINIServerList=1



Under serverlist, you fill in the server name and its ID.
The ID however, changes when the server has been rebooted, reset, or when Eqemu has had a reset or update.
You'll notice this when your character won't properly log in, or when your EQ client ends up at a blank character selection.
That means it has taken the wrong server (since the ID has changed).
If so, you need to manually log in to the game, and after that, find and open the following file in your EQ directory :
eqlsPlayerData
In there, at the start you'll see : LastServerID=<nr>.
This number is the one you need to put in the below section than.
If you use WinEq, the file you need to look at for the server id is called : eqlsPlayerData.WinEQProfile1.

[ServerList]
Raidaddicts=30



Per account and character you need to fill in the appropriate info.
Below are examples :

[Accountname]
Password=
Server=Raidaddicts
Character=

[Mortenson]
Password=Mortenson1
Server=Raidaddicts
Character=Mortenson

[Mortenson2]
Password=Mortenson2
Server=Raidaddicts
Character=Kingmort

Etc etc.



  • MQ2EQBC

This is needed to be able to actually send commands to your box chars.

  • MQ2Map

This is used to see all npc's and mobs, and their movements on your in game map.
You can also filter settings by using the in game command /mapfilter

  • MQ2Itemdisplay

This displays additional information on items and spells that the base game does not.

  • MQ2Moveutils

This plugin makes sure you can have your boxes follow you around, and is a far improved version of EQ's basic follow command.

  • MQ2Exchange

This allows you to swap items from your inventory to equipped slots, without actually having to do it yourself (IE via macro).
This can come in quite handy for having a box char swap out a weapon or item that is required to be equipped to be cast,
and swap it back out to its inventory when done casting.

  • MQ2Melee

This plugin lets you, or your box toons, automatically use skills in combat.
It is quite an extensive plugin, and has to be fine-tuned by using the command /melee.
It actually differs in options per class, and as is obvious, should only be used for melee (and hybrid) classes.

  • MQ2Cast

This is the opposite of the melee plugin, and is mostly used for casting spells, discs, and AA's.
This also is quite extensive, and in some cases is dependent on the Bandolier (MQ2Bandolier) and Exchange (MQ2Exchange) plugins.

  • MQ2Twist

This is mostly used for bards. It can be used to twist cast spells, but simply isn't working as proper as it does with bard songs.

Besides these plugins, there are tons more, but are a personal choice if you want to run them or not.
To remove a plugin that is active, when offline,
open the MacroQuest.ini file in your MQ2 folder, and remove the one you do not want anymore, save and close.

Giving Commands

To actually use commands, you (almost) always have to start with the following :

  • /bca

To use a mnemonic, this means BroadCast Announce.
That means that any line starting with this command,
sends out commands to all other connected clients to do something.
Examples of what, follow below in the other topics.

  • /bcaa

This means BroadCast Announce All. Which means it does the same as above,
but in this case it ALSO includes the client (character) that is actually giving the command.
For example : /bcaa //camp desktop.
This would result in all your clients, be it one, or 24, camping to desktop.
More examples will follow below.

  • /bct

This means BroadCast Tell.
This allows you to send a command to a specific channel (that you set up, how to do that you'll see below in the topic Channels).

To make it clear, it probably does not actually mean BroadCast Announce, or BroadCast Tell, but it is an easy reference to explain this.
I have not yet actually found out what it would actually mean, if it is an acronym at all :)

As you also notice above with the /bcaa // example, there are 2x a // after it.
This is required to give the command, all that bcaa does is provide an entry to somewhere (in this case, every client).
The 2x // that follow, will let you initate whatever you want your clients to do.

Channels

Channels are something you can set up, if you are running multiple different toons from different classes.
It isn't necessary to do this, since you can dedicate your commands into tells as well (/bct),
Here is an example though of when it actually COULD be useful.
Say you run 2 groups, with in total 2 tanks, 2 heals, 4 rangers, and 4 mages...(it's only an example).
In that case you can set up your rangers in a channel, your mages in a different channel, and your healers in a 3rd channel.

Now not all channel names work.
I do not know why, but cases like a class name often seems to not work (like using a channel named Mage or Magician).
Nevertheless, you can easily set up channels in 2 ways.

- One way is by typing it in via the client (character) that needs to be in a certain channel.
For example on ranger one, you can type /bccmd channel Raanja.
Doing so would result in your MQ2 window displaying that <name of ranger one> has joined channel Raanja.
(bccmd command comes from the EQBC server, and has A LOT of options, to find out more about those, check this)
Then on your mage one, you could do for example /bccmd channel maage.
And so on, and so on.
Sometimes though, this also will not work properly.
Sadly there is no explain as to why, but in case it is, you can result to the alternative method.

- In your MQ2 folder, you have a file called MQ2Eqbc.ini.
Open this, and you can manually add channels like this :
[Character name]
Channels=channel name

[Mortenson] (this would be a ranger)
Channels=Mortierules
[Kingmort] (this would be a mage)
Channels=Mortieowns
[Mortensen] (this would be a warrior)
Channels=Mortierawr

You can add as many char names and channels as you want in here.
Reminder : The actual main client (the one that would mostly if not always initiate all commands)
does NOT have to be in the channel, or any channel that you use for your box toons, to give commands.
When you are all set, you can easily test them out in game.

For example, log in one, or all chars that are in that channel you are wanting to try out.
When they are online, you can for example try out something like this :
/bct raanja //target Kingly
Then switch to one of the characters in that channel, to see if they actually have Kinglykrab the Exchanger targeted.
If so, you know that your channel set up works properly.

Targets & Targetting

Targetting works with multiple signs and letters.
They also vary for a mob or yourself.
Make no mistake, that using as a command /target Mortenson, could very well result in the ones needing to target Mortenson,
to actually target his pet instead of him (if he would be a mage).
This is because the /target option, works to target that what is closest and matches the name.
For example would you be in Suncrest Isle, and do a /target King, you would target Kinglykrab, instead of King Mortenson.
This is because he is closer.
That is why targetting is mostly used as described below.

  • Targetting self

You might use this more often then you would think.
Mostly used for the follow (stick) command, or if need be, a specific buff from a box char that requires a target.
//target id ${Me.ID}
This causes whoever to get the command, to target the person responsible for giving the command. Me in this case.
For example :
/bct Kingmort //target id ${Me.ID}
/bct Kingmort //casting 0000
This means that the main client is telling kingmort to target me, and cast a spell.
The 0000 would be the spell ID number, which you can find by inspecting spells on the designated character.
To be able to read this information, you would need the MQ2Itemdisplay plugin as listed above.
As you can also see, it takes 2 up lines in a macro window from EQ.
This could potentionally form an issue, that is why further below the section Multilines is being addressed.

  • Targetting NPCs and Mobs

This is mostly initiated from the main client.
That means that this client is the first one to target this npc or mob, and give out further commands to the rest.
(as in, you guys need to target this mob).
Ofcourse this can be performed from any client.
/bca //target ID ${Target.ID}
If you perform this in game trying to explain to somebody what to type, you'll end up with the following :
//target ID NULL
That is because MQ2 can not process a blank target, hence it comes up as NULL.
A good example of this usage would be a pet attack button (or players, but we'll stick to pets for the example).
/bca //target ID ${Target.ID}
/bca //pet attack
If in the above example, you are a pet class as well,
you could change the 2nd line to /bcaa, so it includes your pet as well.

Sticking

Sticking is the advanced and improved version of EQ's /follow.
The best macro you can have for this is the following :

To start having everyone follow you :
/bca //stick uw id ${Me.ID}
In this case the uw stands for underwater.
It does not literally mean that, but more so to face the sticking target.
Meaning everyone following, would automatically look up and/or down if need be,
When you go over a hill, or dive into water.
Notice in the above case, there's only 1 a.
/bca instead of /bcaa.
That is because would you try to use /bcaa, the client would try to have you follow yourself, which is impossible.

To turn this off, simply use : /bca //stick off

Both these options are best made into a macro and put on your hotbar for you to quickly use.

Multilines

Multilines are there to solve the space problem you can run into when making macros.
Multilines can also easily appear to get messy, but once you get the hang of it, it's not so bad.

When using multilines, you are required to use the ; sign to split the commands.
Only 2 commands can be executed after a multiline, before needing to re-enter a new command (by using the ; sign)
Multilines can be used in 2 ways.
One is to start with them, as in that being the initial command,
the other is to put them in after starting another command.

Here are some examples :

/multiline ; /bct Raanja //target ID ${Target.ID} ; /bct Maage //target ID ${Target.ID}
/multiline ; /bct Mortenson //casting 1234 ; /bct Mortenson //timed 39 /casting 5678
/multiline ; /bct Kingmort //casting 8765 ; /bct Kingmort //timed 35 /casting 4321

As you see, these examples are where the multiline starts as initial command.
Now these 2 examples mean the following :
The first multiline indicates sending tells to channels for the Rangers and Mages, to target something.
Now you might wonder why the /bca option isn't being used,
In this case it would mean that only the rangers and mages are supposed to target this specific target.
And that for example the healers and tank are supposed to target different targets.
This is also a perfect example of why channels can be used.

For the example also you see a tell specifically to mortenson and Kingmort instead of the channel Raanja and Maage.
This is to simply show that the multiline works in various settings.
The casting and timed sections will be treated further below in this guide.

Here is another example :

/bct Mortenson //multiline ; /stick behind 150 ; /autofire on
/bct Mortensen //multiline ; /stick front 10 ; /attack

As you see, here the multiline is the command to start doing things, rather then initiating.
You also can see that in this case the multiline has 2x a //, instead of 1x as in the 3 above examples.
That is because here, it acts as a command starter (like //stick, or //target), rather then an initiation (like /bct, or /bca).

In this example, that first line is only dedicated to Mortenson, and for it to do multiple things.
The second line goes for Mortensen, to also do multiple things, but different ones.

Overall the multiline option starts in a line.
You can basically put in endless commands (or atleast untill the macro window doesn't allow any more input),
as long as you split them after 2 commands with the ; sign as shown above.

Group / Raid invite & Auto Accepting

This is a quite short sweet and simple macro.
To set up a group invite, and have them automatically join the invite, put the following in a macro :

/multiline ; /invite Mortenson; /invite Mortensen; /invite Kingmort
/bca //timed 1 /invite

The timed 1 is to cause a 1 milisecond delay for them to get the invitation.
The multiline allows you to invite multiple people in one line, rather then filling up all 5 lines in a macro.
For this macro to work though, you have to make sure that all members receiving the invite,
are currently not in another group, or raid.
If they are, they will not be invited, but it can also cause others that are not, to not accept the invite.
Also note that the ; sign has NO space between it and the name.
This is needed, because with a space, the name would not be recognized for the invite command.

Raidinviting basically works the same way.
But! In order to be able to use the raidinvite option, you will have to load the plugin : MQ2Autogroup
This is needed because MQ2 otherwise doesn't handle the raidinvite window (since groupinvite comes in chat, rather then a confirmation window).
(To add names to Autogroup, simply type /autogroup Mortenson, and this will create an ini file with names from who to automatically accept invites from).
(or you can open up the ini file and manually put the names in, using lines like Name0=Mortenson, Name1=Mortensen).

Alternatively you can add the Squelch line in the second line of the macro,
(in this case you do not have to use / load the autogroup plugin), this should also cause all toons to accept the invite,
but it can cause lag or even disconnects since it's alot of commands wrapped into 1 massive line.
How this line is set up, you can see at the bottom topic Extras.

Instead of /invite Mortenson, you would type /raidinvite mortenson.
This though can become very messy, since it doesn't autmatically form groups,
meaning you'd still have to manually place everyone in a group.
Nevertheless the option is there should you want to forum multiple raidgroups.

For example Mortensen is a group leader, and Kingmort also,
Then you would have the following :

/multiline ; /raidinvite Mortensen; /raidinvite Kingmort
After 2 seconds, they will automatically accept the invite into the raid.

Attack

Using attack macros is where it gets more interesting.
Also where you will more often start using multilines, timed commands, and casting.
In an attack macro it is always good to have a target id line.
This is not necessary ofcourse, you can easily have a seperate macro for that, but it cannot hurt.
Besides that, you'll soon run into having to have multiple attack macros,
for multiple actions, classes, spells, skills, discs, etc.

Here is an example of an attack macro.

/bca //target ID ${Target.ID}
/bct Mortsmonk //multiline ; /stick behind 10 ; /killthis
/multiline ; /bct Raanja //face ; /bct Raanja //timed 2 /autofire on


As you can see, line one is to get the apropriate target. Ofcourse you can have a seperate target button,
but in case you need to be fast, or forget it, it's nice to have it in there.

Line two, as you can see, is a multiline to tell the monk to not only get behind the mob at a certain distance,
but also to keep attacking until the mob is dead.
This stick command also causes the monk to keep on the mob, even if it moves away.
You can also use //stick front <distance>, which could be usefull for example for a 2nd tank.
The range you van vary as much as you like, but after a certain distance the monk stops hitting due to range ofcourse.

Line three is focused towards the rangers.
You see it tells them to face the target. You can also use a distance stick, like with the monk,
but too close and they cannot range attack, too far, and they cannot cast nukes (if you want to use those).
Also, at times, it can cause problems with spellcasting during a distance stick for them,
and, if you are in enclosed spaces, or with lots of mobs / close agro range, this can cause problems for you.
Nevertheless, the option is available if you want to use it.
In this case tho, the option //face has been chosen, causing them to face the mob, regardless of where he runs.

In the topic below, we'll treat casting more.
You can add casting commands to the above attack macro without issues,
On this example it is left out to be treated in the next topic though.

Casting (items), AA's & Discs

Casting doesn't differ as much from the attack setup, but has more options to work with.
As it can be used for spellcasting, AA activation, and Disc usage.
Casting also can be used in two ways.
Either you use a casting ID, which you can find out by inspecting a spell,
or you can use the name of the spell, with quotes.
Here is an example of an actual spell :

/casting "Word of Healus"
/casting 9897

Both these do exactly the same, but one is used with names, the other one with the Spell ID.<br
Below is an example of a spellcast macro.

/multiline ; /bct Kingmort //casting 1234 ; /bct Kingmort //timed 39 /casting 4567 -kill
/bct Kingmort //casting 2345 -kill
/bct Maage //casting 2345 -kill

This example is towards a mage.
It tells him to cast a certain spell (once), and after that, wait a certain amount of time,
before casting another spell, and keep casting this untill the mob dies.
More on this delay in the below topic Delay commands, and the -kill command in the topic Extra.
In the second example, Kingmort is told to only cast one spell, but to keep doing so untill the target dies.
The third example does the same thing, but in this case towards the channel for the mages (and therefor everyone in it).

You could also use //twist instead of //casting, but that will be explained in another topic below.



Item clicky's are used almost via the same way.
Here is an example of such :

/bct Mortenson //itemnotify Mainhand rightmouseup
/bct Mortenson //itemnotify in pack8 8 rightmouseup

In example one, it's very simple, you just notify the item in a certain slot to be rightclicked.
The slotname can change to any of the inventory slots.
In example two, you see it notify's an item in a bagpack.
This will cause the macro to search in inventory bag 8, and within that bag, slot 8, to rightclick an item for the effect.
These slot numbers (in pack<nr>) can go all the way up to bank16.
So for example :

/bct Mortenson //itemnotify in bank16 7 rightmouseup

In some cases, you actually need to exchange an item to be equipped to be able to be clicked.
Below is an example of such.

Line 1 : /exchange "Lodizal's Ring of Power" rightfinger
Line 2 : /pause 5
Line 3 : /itemnotify rightfinger rightmouseup
Line 4 : /pause 12
Line 5 : /exchange "Ring of Bluebark" rightfinger

As you can see, both items are in quotes, and written exactly as they are called, to tell the plugin which item to find.
Without quotes, the item won't be recognized.
So line 1 means for the Lodizal ring to be equipped, and line 5 for the Bluebark ring to be equipped again when done.
The pause command in line 2, is to make sure the exchange actually happends before initiating anything else.
The pause command in line 4, is to give the item time to be clicked, and finishing its cast (if it's longer then instant).

You can wrap this in a macro in such a way to actually have a box toon do something like this,
or even an entire channel, provided they all have the same items.
To do so you can simply add (and replace) : /bct <name> //exchange, and /bct <name> //pause etc,
or you can use multilines in this case, but make sure to properly test it,
since a spacing, or incorrectly placed letter or something can easily cause it not to work.
When using multilines it would become something like this :

/multiline ; /bct Kingmort //exchange "Lodizal's Ring of Power" rightfinger ; /bct Kingmort //pause 5
/bct Kingmort //itemnotify rightfinger rightmouseup
/bct Kingmort //pause 12 /exchange "Ring of Bluebark" rightfinger

This way you'd have 2 lines left over in a macro to fill with something else, IF you would want to.
As you can see, the second line has no multiline, because a macro won't allow for 2 multilines both with a pause command.
Overall it is better though to dedicate such macro's to one single toon, without multilining.



The have your boxes, or some of them use their AA's, is really really simple.
All you need to do, is find the correct AAN (Alternate Ability Number) to use.
Once you have it, all you do is make a line in a macro with the following :
Either start with /bct or /bca, for whoever you are going to command this to,
Here is an example for an AA macro.

/bct Raanja //alt activate 462

In this case the AA macro is aimed at the rangers,
The 462 number is their Auspice of the Hunter AA.
That is all that is required for an AA macro.



Disc macros are also quite easy. Instead of using a number though, for discs you have to use the full name.
For example :

/bct Mortsmonk //disc What the F** is FD?

As you see, the command to use a disc is aimed at the monk. The disc name, is EXACTLY that.
To use a disc you have to use the exact name, no extra spaces or underscores.
That is all for a disc macro.

Delay Commands

Delay commands are there to help you cast more then one spell with a macro.
The reason delay is needed, because a spell, once cast, has a recovery time,
and once a spell is cast, all other spells gray out for the time being,
this is the refresh timer. Once that time has past, you can start casting your next spell.

This works quite simply, with a //timed command.
The numbers used in those commands count as miliseconds.
So a //timed 2, would be a 0.2 seconds delay.
And a //timed 43, would be a 4.3 seconds delay.

Now a timed delay macro only goes sofar.
It is unsure if it's caused by the macro, or by the plugin, or the actual scripting of MQ2,
but you cannot have more then 2 spells cast, with a delay timer, per macro.
That also means for example that you can NOT do something like this :

/bct Kingmort //casting 1234
/bct Kingmort //timed 45 /casting 5678
/bct Kingmort //timed 39 /casting 9012

In this example, Kingmort will cast a spell, then wait 4.5 seconds, and casts another spell.

(It could be that the spell that was cast, only takes 1.3 seconds to cast, and has a refresh of 0.7 seconds,
which adds up to 2.0 seconds, but that it still takes an additional second for other spells to become available again,
which would add up to 4.0 seconds, add another half a second in there, in case of fizzle,
so that there is enough total time delay before starting another cast).

Now in the above example, the 3rd line, with the 39 time delay, just won't cast.
For some reason, which is unknown, the macro / plugin / mq2 doesn't allow more then 1 delay.
This might seem annoying, but nevertheless this command still can come in quite handy for using DoT's or Slows or Heals.
Which would be mostly used for shamans, enchanters, and ofcourse healers.

This command also works great in combination with the use of AA's.
Here's an example of that :

/bct Kingmort //alt activate 0987
/bct Kingmort //timed 39 /casting 3456



If you would want to use more then 2 spells with this, you would have to resort to //twist,
but that has nothing to do with delay commands, and also makes the delay command redundant
Nevertheleless here is an example :

/bct Kingmort //casting 1234
/bct Kingmort //timed 45 /twist 3 4 5

In this example you see Kingmort would cast a spell, wait 4.5 seconds,
and twist (cast) spells memmed in gem (slot) 3, 4 and 5.
You can add several more gemslots to be twisted here if needed.
Keep in mind tho that the twist only works once, unless it's towards a bard.
More on this in the next topic.

Twisting

Twisting is a command mostly designed for bards.
It can be used for any class with spells as well, but there is a disadvantage.
You can "twist" multiple spells, but only once.
Twisting 1 spell, can go on endlessly.
Since only bards can actually sing a song (spell) rather then cast, only they can twist it for ever.
Twisting also has its limits though, which is that you cannot twist a song in slot 10, 11, or 12.
If you try to, you'll get the following error :

Undefined item specified (10) - ignoring (see INI file)

This means you'd have the configure your INI file in order to be able to use this slot.
How that is done though you can find out here
Twisting for bards persists upon zoning.
Another useful twist command is /twist stop.
This would be great in the following example :

/bct Mortsbard //twist stop
/bct Mortsbard //timed 5 /disc Million Blades
/bct Mortsbard //timed 5 /twist start

This example tells the bard to stop twisting its current twistroutine.
Then use its disc, and resume the previous twistroutine.
As you can see, there's a timed command in here, this is done on purpose for the example.
It's build in the make sure there is enough time after stopping to use the disc,
and after using the disc to start twisting again.
Since twisting songs is a continuous casting, it has to be interrupted to perform other actions such as AA's, Discs, and item clicky's

Extra

  • -maxtries

This command helps you avoid fizzles, or interrupt failures (for example when being hit).
You can add a number here, and it doesn't really matter how high it is, but overall it has no use making it a high number.

/bct Kingmort //casting 1234 -maxtries|5

This will issue a command to Kingmort, to cast the spell with ID 1234, and in case it would fail due to whatever reason,
try to recast it for a maximum amount of 5 times.

  • -kill

The -kill extension is a great command also.
This allows you to tell someone to keep casting a spell untill the target dies.

/bct Kingmort //casting 1234 -kill

The -kill extension also replaces the use of -maxtries.
This is because it is an endline command.
Meaning you cannot command another spell with a -kill once it has already been given.
The -maxtries command is only / mostly used when more spells are to follow.

It also works great for having a healer chain heal, or an enchanter chain rune.
The command would look simular to :
/bct Mortonsonheal //casting 9876 -kill

The use of -kill here would become endless, since the target that would receive the heal,
Is not (or hopefully) going to do die.
The command will stop though, if the target dies, or upon zoning.
Keep in mind though, if the heal, or rune requires you as a target, don't forget to add the proper target command line first in a macro!



Then there is something that is a BIG line, with a lot of text, but very useful.
This is a command that fits in just 1 line of a macro, and lets you MASS accept.
Accept quests, invites, notifications (such as returning to a mission), leaving missions etc.
Just be careful when using this when doing a mass #e leave,
because if the leader leaves before the rest does, they get bugged out.
This is the command :

/squelch /bcaa //multiline ; /notify ConfirmationDialogBox Yes_Button leftmouseup;/notify LargeDialogWindow LDW_YesButton leftmouseup;/notify TaskSelectWnd TSEL_AcceptButton leftmouseup;/notify GiveWnd GVW_Give_Button leftmouseup

To use this, simply copy it into a macro.
There is also a short version of this, but does not always work for every confirmation dialogue.

/notify ConfirmationDialogBox OK_Button leftmouseup

WinEQ

WinEQ is pretty easy to use, and a great addition to let you multibox.
Setting up is also quite simply.
After installing, you can start it up, and right click the icon in your taskbar.

Wineq1.jpg

Clicking on these preferences opens up a new window, as you can see below.

Wineq2.2.jpg

In here, you can find 32 profiles you can customize for your characters.
In here you also need to fill out a name for the client, and a title,
Such as :

- Name : Rangeraccount (Rangerone)
- Window Title : Rangerone
- Everquest Path : This is kind of speaking for itself.

This example is displayed as follows:
The name has the account name listed from that account, and in brackets the name of the character belonging to that account.
This ofcourse does NOT have to be done, but it is a nice mnemonic for yourself to remember which is which.
The window title is what is displayed in your taskbar when this client is running.
In this case also, it is handy to know which is which.
Once you are done setting up your account(s), you can once again right click on the wineq icon in your taskbar.

Wineq3.jpg

If you follow the above picture example, you'll see all the accounts listed you created under the Create Desktop Shortcut.
Simply click on the name of that account to create a shortcut.
You don't have to do this, you can also click on the Everquest topic,
and then above the Create shortcut option, you'll also find your accounts listed.
Clicking on this version will launch the client, though using shortcuts is a lot easier.