Page 1 of 1
Anti-Idle Bazaar macro
Posted: Tue Jun 01, 2004 2:42 pm
by loadingpleasewait
Ok, I dont know what the threshold is, but I have been kicked 4 times now because I was idle too long in the bazaar. If you havn't, eq actually pops up a box after being disconnected saying this is why you were.
So, I threw together this little anti idle macro so I could leave my trader up for as long as I like.
Code: Select all
|anti idle bazaar macro
|created by loadingpleasewait
sub main
/declare timetowait outer
/echo anti idle macro starting..
:loop
:randagain
/varset timetowait ${Math.Rand[30]}
/if (${timetowait}==0) /goto :randagain
/if (${Me.Sitting}) {
/stand
/echo Standing back up at ${Time.Time12} for ${timetowait} Minutes
} else {
/sit
/echo Sitting back down at ${Time.Time12} for ${timetowait} Minutes
}
/delay ${timetowait}m
/goto :loop
/return
Basically it just sits you if yer standing, and stands you if yer sitting. It does this at random intervals anywhere from 1 minute to 30 minutes.
works for me..
Posted: Tue Jun 01, 2004 5:09 pm
by pooz
You get kicked from the bazaar because the server crashes.
Posted: Tue Jun 01, 2004 8:20 pm
by Drumstix42
I was AFK in bazaar for overnight just last night... at least 13 hours strait...
Posted: Tue Jun 01, 2004 10:21 pm
by Elric
Nah. There's new idle code. I stood in GFay for five hours.. And ended up with an Idle Boot.
However, for some reason, if you idle in windowed mode, with another application open over EQ, you won't get the idle boot.
Posted: Tue Jun 01, 2004 10:31 pm
by Drumstix42
Ah, well EQ was minimized, and I probably had musicplayer going and some IM service I'm sure.
Posted: Tue Jun 01, 2004 10:34 pm
by JimJohnson
only idle disconect if your minamized. bazaar mule up and going on 5th day now.
Posted: Tue Jun 01, 2004 11:20 pm
by loadingpleasewait
maybe thats it, cause I always minimize my bazaar mule.. It is an idle code, other people in my guild have mentioned it as well. I know where I would be kicked and others would stay fine.. Its not LD, its not a zone crash, but this macro prevents it.. thats all I know.. /shrug
Posted: Wed Jun 02, 2004 2:54 am
by A_Rogue00
No, you did go LD. The idle message is the same as the "Connection to login server timed out" or whatever when you left server select screen open too long on old frontend. You get booted to server select for whatever reason, then that times you out so some random person doesn't show up at your comp and log in to your server and mess with your stuff or something. Nothing new really.
Posted: Wed Jun 02, 2004 8:00 am
by MoonRaverX
I ONLY get this message when I idle in the bazaar. I go to bed my char sits in Time, Tranquility, POK, hell.. Shar Vahl... and never gets an idle message. ONLY happens to my mule, and then it's somewhere in the 6 hour range. This isn't a bad idea, and bot stayed up, go figure.
Posted: Wed Jun 02, 2004 1:49 pm
by secrettoo
Sounds like a setting at your ISP end, not EQ. Some ISPs have the option to setting disconnects to certain times or not at all. Or it could be your service provider being pants, like mine is sometimes.
Posted: Wed Jun 02, 2004 10:11 pm
by Elric
No. It's specific in-game code. Jesus people.
Posted: Wed Jun 02, 2004 10:27 pm
by JimJohnson
anytime you leave a a session running in the background for a LONG period of time you will go LD its in game codeing. dont care whaat zone you are in. Tranq Time Fear Rivervale. window then minamize it and leave it at your desktop.. come back 3 -4 hours your LD ever time
Posted: Thu Jun 03, 2004 1:47 pm
by secrettoo
So the fact, and it is fact, that I leave 2 windows minimized overnight and all day and just actually maximize them in the evenings for playing, and I dont go LD, but you do, is still in game idle coding? Either its for all people, or no people, not just some of us.
Posted: Fri Jun 04, 2004 5:46 pm
by Maestro
Go to server select screen, leave it there for a few minutes, and you will get that idle message. The bazaar itself is buggy/laggy, and on some connections will make you ld to server select frequently, leading to that message. It's misleading, and I've /bug'ed it a few times, but it's not gamebreaking or anything, just worded wrong.