The Hidden Forest

If any of the follow has happened, then this is for you. Have you...
*Sent one or more boxes running to their doom because they were at the zone-in or in another zone all together?
*Not realized one of your boxes is lost because they never actually started following you (perhaps because they were behind a wall or object)?
*Painstakingly made a unique /stick <blablabla> hotkey for each and every character?

Simply paste this line into your MacroQuest2.ini file under the [Aliases] section (thanks goes to an old friend who taught me what aliases are, some time ago!), save it, restart MQ2 (this may require you to restart your EQ clients in some instances), and then access it with /stickme when in game.

It's not a short command, but it should do exactly what you want it to (and then some).



/stickme Will broadcast commands to your boxes to do the following...
[1] Declare two global variables if they do not exist. They are StickZone and StickTar. Global variables do not need an actively running macro to be created, accessed, or modified. This should meet the needs of both people that run macros and people that just do basic hotkeys with EQBCServer and plugins.
[2] Set those variables to the zone name (string) and ID (int) of the broadcasting character.
[3] Check if they are in the same zone, within range (200 units), and within line of sight of the broadcasting character. Then proceed to stick if these are all true.
[4] If anything in [3] is false, then they will broadcast that they cannot stick to this character in the MQ2 window.

I hope it makes some people's lives a little bit easier! Feel free to modify this to your needs if you know how. You can remove LoS requirements, change the range req, and of course change the type and distance of the /stick command.

Cool, thanks. I might try this out. I currently use netbots to check the broadcasting characters zone so I avoid most stick of doom scenarios. I also use the same logic with attack/attack off code so I can manage two or more camps in multiple zones, without conflict.

wow noren! very good work!

Creative use of global variables and the alias section of Macroquest.ini
I like seeing other people do stuff like this. Rate this a 12 out of 10!

Yup! Very good work. Has rekindled my desire to delete my normal mac and start from scratch, using this and simple bc commands as the follow routine

I tried this, new to MQ2 and all , figured it would be a good first step and a really usefull one

sadly cant get it to work, says for all chars : "Stick target isn't nearby. Staying put". even when on top of each other.

Any advice ?

ikaf wrote:I tried this, new to MQ2 and all , figured it would be a good first step and a really usefull one

sadly cant get it to work, says for all chars : "Stick target isn't nearby. Staying put". even when on top of each other.

Any advice ?

We may be using a different version of MQ2. I would try breaking down each requirement individually to see which one is holding you up.

[1] Issue the /stickme command (expecting no sticking to actually happen) and then do the following on another character than the one that issued the command.
[2] /echo ${StickZone}
[3] /echo ${StickTar}
If [2] and [3] are defined and hold values, then move on to [4].
[4] /echo ${Zone.Name.Equal[${StickZone}]}
[5] /echo ${Spawn[${StickTar}].ID}
[6] /echo ${Spawn[${StickTar}].Distance}<200
[7] /echo ${LineOfSight[${Me.Y},${Me.X},${Me.Z}:${Spawn[${StickTar}].Y},${Spawn[${StickTar}].X},${Spawn[${StickTar}].Z}]}
[8] /echo ${Stick.Status.Equal[ON]}
[9] /echo ${Stick.Status.Equal[OFF]}

Please report back with the value MQ2 gives you for each line. None of them should return errors or NULL. They should all have a value.

Oh and a tip!
If you didn't know (at least for the UF client), you can enable the Windows clipboard in-game for pasting. See pic.

Here's what i get.
Command issued from SK and failed on both cleric and monk ( only had those loged ). they only turn to the SK.

Not sure on the MQ2 version , but using Titanium client.

Great tip on the clipboard option btw, never knew that was possible.


[2] /echo ${StickZone} * Icewell Keep
[3] /echo ${StickTar} * 332
If [2] and [3] are defined and hold values, then move on to [4].
[4] /echo ${Zone.Name.Equal[${StickZone}]} * TRUE
[5] /echo ${Spawn[${StickTar}].ID} * 332
[6] /echo ${Spawn[${StickTar}].Distance}<200 * 18.38<200
[7] /echo ${LineOfSight[${Me.Y},${Me.X},${Me.Z}:${Spawn[${StickTar}].Y},${Spawn[${StickTar}].X},${Spawn[${StickTar}].Z}]} * TRUE
[8] /echo ${Stick.Status.Equal[ON]} * FALSE
[9] /echo ${Stick.Status.Equal[OFF]} * TRUE

For whatever reason, yours might need a longer delay before checking if stick is on. If you find where it says "//timed 3" try increasing that. That is in 1/10ths of a second. You can try //timed 10 to be very conservative, or //timed 6 for middle of the road.

Hope that works.

Guildmember has the same problem, result:

1-Guild Hall
3 - 43
4 - TRUE
5 - 43
6 - 64.87<200
7 - TRUE
8 - FALSE (Sticking on ?)
9 - TRUE

Couldnt find any error in the command, couldnt check ingame tho.
Thank you Noren for the idea, he will try with higher delay, for me the command is working.