Log Parsers

[Klath]

Originally Posted by john_savage1982 [You must be logged in to view images. Log in or Register.]

That's exactly what I'm building.

It works great when you bind your arrow keys to a /loc macro and filter them to a mostly-hidden window.

I always liked the EQ Atlas maps although some of them need to be massaged a bit in order to get them to scale. Lower Guk was a challenge.

I had a couple of additions planned but stopped working on it before I got to them. One was to add a fade-over-time marker on the map for locs posted to group or guild chat and another was to add support for toggling between the picture file maps and the vector maps the game used. I suspect that those sorts of additions wouldn't improve the likelihood that the server gods would sanction its use though. [You must be logged in to view images. Log in or Register.]

[john_savage1982]

I don't see how they can stop us from reading the logs and running our own programs that use log data to generate useful information.

[Flunklesnarkin]

Originally Posted by john_savage1982 [You must be logged in to view images. Log in or Register.]

I don't see how they can stop us from reading the logs and running our own programs that use log data to generate useful information.

yah.. doing w/o detection is one thing.. promoting is another.

[Klath]

Originally Posted by john_savage1982 [You must be logged in to view images. Log in or Register.]

I don't see how they can stop us from reading the logs and running our own programs that use log data to generate useful information.

From a technical standpoint, it would be virtually impossible to stop people from using a log parser approach to mapping. For example, even if the parser process was identifiable, if you ran the parser on another computer (or in a virtual machine) and accessed the log file remotely the process would be effectively hidden from detection.

I'll post a follow-up to my original query in the "Petition / Exploit" forum and see if I can get someone to weigh in officially.

[gnomishfirework]

Klath, I would love to get a download if you ever find out if its allowed. seems useful.

technically, you could have done this in classic it just reads logs, and its not showeq where it shows you thinks you cant see.

Should be allowed, but i wouldnt use it until you are sure.

[Klath]

Originally Posted by gnomishfirework [You must be logged in to view images. Log in or Register.]

Klath, I would love to get a download if you ever find out if its allowed. seems useful.

Absolutely. If it officially falls within the rules I'll make it available for everyone.

[Flunklesnarkin]

*Debbie Downer* i really hope it isn't within the rules...

but yar gonna channel my inner KMFDM.... anarchy... nuff said

aka ( if you smart enough to not get caught good on you but don't promote...maybe...prolly idk)

[Mardur]

Lol @ people who think a log parsing map program is against the rules. People were doing that stuff in classic. What's next, bans for people who visit eqatlas?

[Klath]

Originally Posted by Mardur [You must be logged in to view images. Log in or Register.]

Lol @ people who think a log parsing map program is against the rules. People were doing that stuff in classic. What's next, bans for people who visit eqatlas?

"Any type of program or script that gives you an unfair advantage (eg. MacroQuest, ShowEQ or packet modification) will result in an instant ban with no lenience. Cheating will be ruled with an iron first regardless of who you are."

"Unfair advantage" is open to interpretation. As written, the rule could conceivably allow some log parsers and forbid others depending on whether the advantage given is deemed unfair. The fact that they list programs that muck around with the internals of the EQ process doesn't necessarily mean that these are the only types of programs that violate the rule.

It doesn't seem unreasonable to ask for clarification -- especially when the penalty is "an instant ban with no lenience."

[knottyb0y]

I wouldn't see a log parsing program that points out /loc commands and transposes that onto a map hosted by the program.

1. You aren't getting info that you cannot got in the client
2. you are not gaining an unfair advantage (doesn't tell you where npc's are, or spawning)
3. it is not changing the way the interface or the way your client interacts with the server

really little difference between an app that does this, and using eqatlas, other than it helps you determine your exact location (with probably limited accuracy).

THe Real difference is ShowEQ reads the packets sent to the server to give you information that you would not have.

Macroquest changes the way the client interacts with the server to give you abilities you would not have.

This would just read /loc commands stored in the log files and estimate where your player is on a map.

With that said it's just a matter of hearing an official explanation or "use at your own risk".