LOL! you guys are too f*cking much. I just read this whole goddam thread for the 1st time. Sorry for my potty mouth.
I want to add a few things.
a.) I do know for certain that part of the function of the client issuing a /report is that the last x lines of text are recorded into a queue that only the GMs (VI employees) have access to.
b.) As somebody else said, MQSEQ is incorrect that they need some type of TCP or UDP server. Both the eq client and eq server are free to send requests to each other using the eq protocol (which I am behind on since I haven’t worked on EthernalQuest in years). Therefore, it's theoretically very possible for GMs to request this data, I doubt they would do it without some reason.
c.) From a paranoid standpoint, it's possible for the EQ client to look for crap in it's own memory space that looks like macroquest and create a flag. I could see this being done if VI wanted to spend some money putting yet another anit-hacking piece of code in the works. Because I don't yet know fully enough the scope of MQs usage and how much attention it's gotten from VI, I can't guess accurately at the possibility of this. Doesn't look very strong tho (but maybe %20).
d.) Before Brad bailed, there was as tendency to collect cheating data over a period of time and then do bannings all at once (as with one of the earlier tools that let you run super fast, etc). He's gone and my observation is less paranoia on VI's behalf about cheaters and "overpowering players" (especially since DAoC) while they are still trying to maintain their policies.
e.) I do agree that VI has an interest in maintaining the integrity of the game to prevent devoted players who followed more strict guidelines from leaving. This is the big claim they make about why they don't want anybody to have tools that would create an unfair advantage. They probably know the effect of this better than I if they analyze their trends well enough (subscriber and usage populations relative to the release of new hacking programs) but I seriously doubt there's ever been any meaningful impact on their subscriber base. To the contrary, I suspect that poor customer service has cost them over 100 times the losses than that of some straight player feeling cheated because they raised 3 trade skills to 250 over a 2 years and some MQ bozo did it in 2 days.
f.) Somebody mentioned something about running eq in debug mode… I forget who. I tried this years ago and found that I couldn’t break in because they used a catch all somewhere, i.e.,
Code: Select all
void somewhereNearEntryPoint()
try {
….
// Lots of stuff…
}
catch(…)
{
// assume the game crashed and exit to windows.
}
Edit: here where I use the catch(...) I literally mean "..." (without the quotes) otherwise known as an elipse.
g.) I’m no lawyer but depending on what the EQ license says, they may actually be in the clear to send data relating to the EQ process. If I remember reading the press release/patch message/whatever on the reversal of the snooping decision the words were “monitoring processes and files” that they promised not to do. So I believe they are legally and ethically in the clear to monitor memory in their own process space. Like a lot of other people have said, implementing stuff like this costs money. Not a great deal, but at least a fairly considerable amount. Then it takes time to analyze the logs, etc. I know that they do this to some degree and have some things automated to the point where they just get a flag and it’s a positive violation, but this is for old cheats I would suspect and new code has to be written for new cheats/hacks, etc.
h.) I would like to see more testing with $gm. It’s theoretically possible for a GM to be “present” in the zone and the eq server not send any entity data for that user (the GM). Now have they done it this way I don’t know. Best way to find out is log packets and claim that your friend is KSing you and have them come observe him. Then have your friend not KS you while the GM/guide watches until the GM claims that he/she hasn’t witnessed him KS you. Then you know that the GM was present. Analyze the logs and I bet we’ll have a solid answer. This assumes of course that you do /who and don’t see the GM in the zone. In other words do you not see them in the /who list because they aren’t in the list or because there’s some flag that tells the client not to show it.
i.) The disconnects described at the beginning of this post could also be related to a bug in MQ (memory leak, buffer over-run, etc) that just caused something to crash and/or otherwise get disconnected. Dunno…
j.) Wrapping your cable modem/dsl modem in tin foil and then grounding the tin foil can actually help you achieve higher connection speeds and prevent disconnects from electrical noise. However, if you do this don’t plug up your air vents or you run the risk of overheating the thing.
k.) I like the idea of not writing to an EQ window object if possible. Can we still issue commands from the EQ terminal and have them get stripped out by MQ I wonder so that they don’t appear in EQ’s normal memory space (it’s normal structs, etc).
l.) ap50: Nice tits!
m.) On to the worry about controlling bots and /tell message being monitored. I do highly recommend that such “commands” be easily configurable and changed regularly. Also that they be weaved into the conversation as others have said. For instance “<<a decaying skeleton>> incoming!!” would be a “command” to assist and run auto attack macro. Any sentence with the word “heal” in it in group chat would be a “command” for the cleric to heal, etc, etc.
n.) Random factor: I think that a simulated human random factor would be a very good thing to implement for the safety of MQ users. It isn’t very hard to do analysis and find that a certain string of actions happens on a perfectly accurate time table. For macros to have some randomness in the delay between the event and reaction and also between sequential commands would IMO be a good thing. If I ever finish this java add on that’s one thing I hope to make a neato class for.
I know it’s funny when noobs are paranoid, but I do think that this is a good conversation to maintain. As somebody else said loosing an account with 4 60+ characters doesn’t sound so appealing.
Sorry for the long post, I had to respond to a lot of things in the 1st 5 pages.