gmrun.mac

[Goge]

I made this to keep me sane while at school and mq is running ^_^
just stick it in where ever and as many times as you want ^_^

Code: Select all

/if $gm==TRUE /call Crap

Sub Crap
   /cleanup
   /sit
   /delay 20
   /camp
   /unload
/return

hasn't gone off yet. i quess i should add a mqlog saying "Crap GM!"
okay add the line /mqlog ahh crap GM in zone! i'm to lazy to go up and add it

[icon]

For added security against macroing:

Code: Select all

/if $gm==TRUE /call Crap

Sub Crap
  /cleanup
  /echo GM in zone... /camping
  /sit
  /reply Sorry, camping, can't talk now.
  /delay 20
  /camp
  /unload
/return

Not too much of a difference, but GM's usually send tells before actually entering the zone you are in... that little /reply can make a huge difference.

- Icon

[nikeman]

just add this to my .mac files? that i alrdy have? or make a newone?

[Plazmic]

It'd be something to drop into cheese.mac after the buy/sell routine.
Or in any macro's main loop..

[Troy]

I think using /camp is bad idea, a lot of time, GM just summon you if they want to talk to you. Would think /q is better.

[gingertips]

One question, how much of the chat screen can the GM view? can they view it without a /report or /petition?

Ive never been summoned by a GM - theyve always come to me, but then I never ever done anythin wrong! Still, I think sending a /reply and then a /q seems a lot more safer.

Not sure I would have the Echo line - after reviewing my log file after a /q, i would see why it quit, because of the "You tell GM camping cant talk now" line... Maybe Im just paranoid...

[Domosan]

A GM can view the last 10 lines of your chat window -- whether the comments there are from EQ or MQ, the GM can see them

Domosan

[gingertips]

so why not include a few lines of code at point of GM entering zone which fires off 10+ lines of general chat lines ie. /guildsay night everyone - gotta go the babies crying for bottle! etc etc etc??

[Domosan]

Or just not echo anything to the screen, and use your log if you want to see your results?

That's what I do anyway

[gingertips]

yes - definitely remove the echo. I will add in the /guildsay lines as well, as i want to make sure that any lines for /macro arent present...

[Domosan]

A GM doesn't have to be in your zone to /kick you or to log your chat screen. Adding in the /guildsay lines, etc. into an "/if $gm" is really kind of pointless.

Just an FYI.

Basically, if a GM finds out you're using a macro and wants to punish you for it, having the little GM check included in your script is going to do a total of squat for protecting you.

Domosan

[fwiggles]

ever thought of an echo that looks like a tell from a friend that says something like: yeah man, i'm outta hear to i guess, cya later? that would sound a LOT less suspicious and how could a GM tell the difference

[GD]

currently all echos have [MacroQuest] in front of them.

"/echo This is a test" would show:

[MacroQuest] This is a test

[gingertips]

y not have 2 accounts running at same time - and at alert send a /tell to other char, or to your guild saying well i better go - the missus just walked thru the door - see u tomorrow for the raid on Najena...and then 2nd account sending reply

[Zorg]

Correct me if I'm wrong, but could a GM see an /echo'ed Macroquest line? Since that part is completely server side, I don't see how they could detect it.