Karana is a marked server.

MQFan · Post by **MQFan** » Wed Oct 15, 2003 9:10 am

Forgive me for asking a n00b question, but wouldn't /filter macros none work pretty damn well for fixing the "GM can see the last 20 lines" problem?

For example, If i run a tradeskill macro, and all output is filtered, all the GM is gonna see is 20 lines of "You have sunk another 30pp into making an item you can't possibly hope to sell for a profit.".

Edited by Eqmule... its "none" not "all" to filter out macros completely...

insanitywiz · Post by **insanitywiz** » Wed Oct 15, 2003 10:15 am

Yes, it would work perfectly for that.

MQSEQ · Post by **MQSEQ** » Wed Oct 15, 2003 10:36 am

The best way is to /filter so no MQ stuff is sent to the EQ client and then use a Telnet session to send the commands so your /macro commands and not tied to EQ period.

If you are trying to Bot your machince use/change the commands in the scripts so if EQ folks monitor these sites they cant see what the actual trigger (ie. Tell JoeBob heal me now I'm dieing!) But enough paranoid thoughts. I go with the basic principle I have 3 accounts which is ~$40 a month, give me a reason not to pay them by banning me. SOE realized when they banned all the folks using EQW they were losing alot of $$$ and so they added the Windows feature in EQ and said if we banned you for using EQW please come back now and play (aka please pay us). Simple math would say SOE would loose alot of $$ if they banned everyone using MQ and/or SEQ types of software. Now thinking about the SOE Board of Directors do you really think they care if 20k or 30k folks are using 3rd paty software? All they really care about is getting paid.

The moral of the post is don't do things that would get you caught (ie shouting in zone you are using macros) . I have learned over the past few years on how to use 3rd party software so others can't tell I'm using anything (unless I have told them directly). I can use SEQ and tell when folks are BOTing and it's funny to watch. Rule number 1 is never run straight to a mob that is on the other side of the zone (not even a ranger can see that far (in most zones)) exspecially if you not a tracking class. Thats how you get reported. Use delays in your macros so you don't do 60+ combines/minute.

Coming down off the soapbox now.

Lax · Post by **Lax** » Wed Oct 15, 2003 11:36 am

Hence the point of using a custom CSidlWindow/CChatWindow and a replaced WriteChatColor.

Actually you could disable the array used by /report fairly easily also...

Mckorr · Post by **Mckorr** » Wed Oct 15, 2003 11:53 am

It's easier to just not do a /report.

Lax · Post by **Lax** » Wed Oct 15, 2003 12:25 pm

You're missing the point. The point is for those that assume that a GM can issue your client a request for a /report. I have no idea if they can or not, but it's a distinct possibility. To allow MQ to have normal usage of writing to the chat window without possible ill effects from that type of request, you could make sure it doesn't appear in the array used by /report

Kint · Post by **Kint** » Wed Oct 15, 2003 7:56 pm

wouldn't they get suspicious if they do a /report for you and nothing comes back?

MQSEQ · Post by **MQSEQ** » Thu Oct 16, 2003 8:58 am

If your Skilling or Killing you would have normal EQ type messages but what you don't want is the [MacroQuest] messages showing up in your EQ chat windows. Hence using the /filter commands to prevent MQ from writing text to the EQ chat windows.

I have noticed tho if you do a /tell command via a Telnet session it does not buffer it in the EQ client meaning if you do a Enter and Shift Up or Down it does not show up in the list. Now that could cause someone to wonder how you can be chatting to someone if there is no buffered keystrokes.

mackster · Post by **mackster** » Thu Oct 16, 2003 1:21 pm

I dunno if the crashing is only related to MQ use. My friend last night told me about how he crashes often when he accepts a mass TL, and he doesn't run MQ. I personally crash on occasion when I'm not running MQ and I take a rez or a TL.

Shocks · Post by **Shocks** » Thu Oct 16, 2003 2:21 pm

Here is my thoughts. SOE would do well to add the commands that SEQ and MQ offer. Mabey not all of them JUST like UO did with UOAssist. It only makes sence. I mean hell if people will spend all this time to add this type of function to there game why not. More ppl would play. The more ppl they get playing the more cash they make.

Work with your hackers to prevent the REAL hacks not these added functions. As MQSEQ said before maybe they will buy a clue for 50,000k. Just my 2 Cents.

mackster · Post by **mackster** » Thu Oct 16, 2003 2:51 pm

Well, they should certainly take into account some of the ergonomic functions of MQ. By that I mean how MQ utilizes the computer's ability to perform repetitive tasks without complaint. I've acquired carpal tunnel syndrome from doing tradeskills in EQ (god damn those halas meat pies, just pure fucking torture), and my aggressive playstyle in combat has added to that.

These days I don't do any tradeskills (the whole system is corrupt and totally hopeless IMO, and I can't even imagine the pain those poor souls who have manually skilled up thier tradeskills have endured), but combat hurts. I mean my wrists and hands hurt if I try and play like I used to. I wear a wrist brace on each hand now to prevent further damage, and I rely on macros to simply perform in battle now.

Without MQ I don't think I could play EQ worth a damn.

They've had auto-run in the game for years now, why not auto-taunt/bash/kick/slam/disarm etc?

EQ could definitely use some more body friendly features.

edit: haha smurf hut building

Benwin · Post by **Benwin** » Fri Oct 17, 2003 8:32 pm

MQSEQ wrote: SOE realized when they banned all the folks using EQW they were losing alot of $$$ and so they added the Windows feature in EQ and said if we banned you for using EQW please come back now and play (aka please pay us).

Actually, They put the Window mode feature in to comply with Microsoft's Windows Compatiblity program, Microsoft says that if your product displays the 'Microsoft Windows' Logo on it, then it must meet the requirements, one of them is being to ALT-Tab and Minimize programs at will... And before EQW this was not doable.

So, SOE Did that to cover their own arses, and they welcomed the people who were banned for using EQW back to *stop* class-action lawsuits, becuase they were banning people for illegal reasons (making a program work the way that it SHOULD work according to the people who wrote the software that program REQUIRES to be able to run)

insanitywiz · Post by **insanitywiz** » Sat Oct 18, 2003 1:07 am

Not to mention that no one in the history of the game was banned for using EQW, unless they came out and said to a GM that they were using it, and even then they had to have done something else to piss that GM off.

I think a total of 3 people affected when they made the offer to revoke those bannings.

vzmule · Post by **vzmule** » Wed Oct 22, 2003 3:26 pm

GMs can read your text. They can actually take complete control of your character while you're logged in.

I was a Guide for a couple years. Gms would goof around with me and move my character and make me jump off things to take damage etc.

I once was flirting in tells with a female guide I worked with. We had hooked up at a fan faire and our tells would have made Howard Stern blush.

One of my favorite GMs was on the server and sent me a tell asking why I never talked to her that way....She had been snooping on me just messing around so yeah, they have the ability to read your text if they want to.

As for the person that said they would have to open another port, that's incorrect. It would go right over the existing ports your client was already using. Only chat channels and cross server tells open extra ports.

Lax · Post by **Lax** » Wed Oct 22, 2003 4:19 pm

Tells are a bit different in that they go through the server to get to you. Anything that goes through the server, we assume that GMs can see at any time without touching your machine. The question, though, is whether they can uncover what simply gets displayed on your machine. Common sense suggests that they have to make an effort to look at you specifically, so as long as you don't do something obvious you're probably ok. On the other hand, they could spot check and happen to be watching your client's text.

Which is why I suggested using a custom MQ "chat" window that has nothing to do with the real chat windows (no logging to file, doesnt show up in reports, etc)... or we could write our own chat display function which also avoids those. hmm.