Interesting (not a sky is falling post)

A forum for the general posts relating to MacroQuest. *DEPRECATED: This forum is no longer in public use, but remains here for your reading pleasure. Enjoy

Moderator: MacroQuest Developers

secrettoo
orc pawn
orc pawn
Posts: 29
Joined: Sat Oct 25, 2003 10:56 am

Post by secrettoo » Fri Jul 23, 2004 9:33 am

Next time you do the glyphed ring in Ssra and you are a forager, when the mob does area FD, see what happens when you press Forage ...

Moeymoejoe
a snow griffon
a snow griffon
Posts: 363
Joined: Sun Jul 18, 2004 10:17 pm

Post by Moeymoejoe » Fri Jul 23, 2004 10:10 am

Ohh! What does it do?

magictiger
a snow griffon
a snow griffon
Posts: 450
Joined: Sun Mar 21, 2004 2:24 pm

Post by magictiger » Fri Jul 23, 2004 5:12 pm

Should do the same thing as trying to forage while sitting.

Rusty~
a hill giant
a hill giant
Posts: 244
Joined: Wed Apr 14, 2004 2:55 pm

Post by Rusty~ » Fri Jul 23, 2004 5:16 pm

assuming the fd thing is a trick to test if someone's afk...

Code: Select all

/if ( !${Me.State.Equal[stand]} ) {
   /delay ${Math.Calc[5+${Math.Rand[10]}*2]}
   /stand
}
should fix it easy enough, without instant standing the second you get FDed

magictiger
a snow griffon
a snow griffon
Posts: 450
Joined: Sun Mar 21, 2004 2:24 pm

Post by magictiger » Fri Jul 23, 2004 5:24 pm

I was thinking along the lines of

Code: Select all

Loop:
/if (${Me.State.Equal[STAND]}) {
/doability Forage
/autoinventory
/delay whateverforagedelayis
/goto Loop
}
/delay ${Math.Calc[5+${Math.Rand[10]}*2]}
/stand
/goto Loop
Should check every loop to see if you're standing. If so, it forages and autoinventories, delays until forage is ready again, then recalls the loop. If you're not standing, it delays for a random time, stands you up, and goes back to the loop. I do more UI/HUD work than macro work, so my syntax may be off.

Jerle69
a hill giant
a hill giant
Posts: 263
Joined: Wed Apr 28, 2004 3:26 pm

Post by Jerle69 » Sat Jul 24, 2004 8:49 am

I'm no chicken little either, but I have seen some things that may corroborate this FD warning. A bard buddy of mine was "forced" to FD the other day after a raid. No GM spoke to him, but I do know he's a rather skilled player (as often bards are), so they may have suspected him of using MQ2. Hell, for all I know they may have been checking me out too!

Anyway, here's the SS I took. I *did* edit this in that I smeared the names out to protect the innocent, but that's it. If you look closely you'll see the bard epic in his left hand (the hilt at least--the blade of the weapon is driven through his chest and obscured in the picture). Also, his name is above his head and he's invisible (hence the parenthesis). He's *not* dead.

Image
--Jerle

User avatar
aChallenged1
a grimling bloodguard
a grimling bloodguard
Posts: 1804
Joined: Mon Jun 28, 2004 10:12 pm

Post by aChallenged1 » Sat Jul 24, 2004 8:56 am

The armor gives it away that it's a bard as well.

We've agreed that yes, GMs can force FD, and apparently they do have the ability to FD singles and not just the old well known AE version.

But, as you mentioned, the GM did not talk with him. That was my main point all a long. GM's aren't going to talk with you about it, just going to do it and move on if nothing improper happens.
Fuck writing MQ2 macros. Go with IS scripts; IS Rules!

s16z
a ghoul
a ghoul
Posts: 97
Joined: Thu Apr 01, 2004 12:03 pm

Post by s16z » Sat Jul 24, 2004 9:43 am

should fix it easy enough, without instant standing the second you get FDed
If you are AFK foraging, probably *not* a good idea to implement this. Standing up after being forced to FD/sit would indicate to me that you should be at the keyboard and answering tells, if I were a GM, and I cared if people AFK foraged since it obviously is a game breaking issue.

User avatar
SnaggleFuzz
orc pawn
orc pawn
Posts: 13
Joined: Wed Jul 21, 2004 4:45 pm
Contact:

This is the greatest thread !

Post by SnaggleFuzz » Mon Jul 26, 2004 1:21 pm

This is the greatest thread simply because it may lead to this:

GM handler .inc

Just imagine it...

Code: Select all

#event ("GM" * "tells you")

/varset answerA1 "what's up?"
/varset answerA2 "hi htere, Mr gam Master."
/varset answerA3 "leave me the Fuck alone!"
/varset answerA4 "what's going on?"

/delay 3s
/varset speaker ${me.name}
/varset logtext ${answerA${Math.Rand[4]}}
/t ${gm.name} logtext
/screenshot
/ini "MyVictories.ini" "${gm.name}" "${Speaker}" "${logtext}"
/delay 10

/varset ExcuseA1 "My boss is coming!!!"
/varset ExcuseA2 "The dog is starting to take a dump on my mom's carpet!! SOrry! gottas log NOW"
/varset ExcuseA3 "so sorry...the time I have allotted to speaking with GMs is over...I think I am going to log on to Ultima Online now."
/varset ExcuseA4 "My computer is blinking out again!!"

/varset random excuse ${ExcuseA${Math.Rand[4]}}

/if ${Zone.GM} {
  /tell ${Gm.name} "Oh SHIT! ${randomExcuse}"

/plugin Run-outside-program-from-desktop | EQstartup | 10 minutes | forager.mac

/quit
Can you imagine!!!
Last edited by SnaggleFuzz on Mon Jul 26, 2004 1:38 pm, edited 1 time in total.
Gnome-tinker Macro-muncher

User avatar
aChallenged1
a grimling bloodguard
a grimling bloodguard
Posts: 1804
Joined: Mon Jun 28, 2004 10:12 pm

Post by aChallenged1 » Mon Jul 26, 2004 1:34 pm

Imagine, definately. Though my var answers would probably end up being about 100 lines, and I would want a check to ensure that if it has been said once it won't get said again. I remember a script for another program that had an INI or was it an H file that contained a list of three sets of text. Each set was defined as param0, param1, param2. The script itself would grab randomly from the groups and make sentences. That makes it much more flexible and less likely to repeat anything in short order.
Fuck writing MQ2 macros. Go with IS scripts; IS Rules!