Working Parser?

[Motenten]

Which version are you currently using?

[Callisto]

I just updated to the new one tonight, but prior to that it was the one before this last FFXI update. Or maybe slightly older, it was 1.47something I think.

Edit: yeah, 1.4.7

[Motenten]

Ok, there have been 12 updates since 1.4.7, including a number of changes in terms of identifying entity types (players vs mobs) that was designed to make it more reliable in not misidentifying mobs as players and vice versa. 1.4.11 and 1.4.15 were the main updates for that.

If you were having the problem only in 1.4.7, then yes, it should be much better now. If you were seeing the problem after updating to 1.5.1.1 then I need to get a look at a sample parse to see what's going on.

[Callisto]

I have einherjar tonight and that's the #1 offender, I have 1.5.1.1 now so I'll let you know if it still does something funky, but good to know that's something that was fixed up.

[fndragon]

Slight necrobump, but here's what happened to me today while using KParser:

http://i42.photobucket.com/albums/e3...gon/fnjail.png

Needless to say I won't be using it again.

[Iresire]

Slight necrobump, but here's what happened to me today while using KParser:

Needless to say I won't be using it again.

Did you happen to mention the fact you were parsing in the game directly or indirectly? Someone could have been a dick and reported you for it.

[Khajit]

Probably one of those gimp douches that hate it when people put a quantitive number on how shitty they are
There's a drk on my serve who always vanishes whenever the word parser shows up.

[Motenten]

Hmm.. Well that is rather unfortunate. It's the first time I've ever come across an issue of a warning for use of a parser.

However there is one slightly ambiguous element. The GM mentioned being able to "view the statistics of players and other information". While one could easily assume it as a reference to the detailed statistical information provided by KParser, one could also interpret it as referring to players' in-game stats (str, agi, actual accuracy stat, etc), which I could certainly see as being a type of violation. There is also no context of what was occuring/being said beforehand (though if it was reported by someone, it could easily be that any issue occured well before the jailing), nor is there clarification from the GM.


As an aside, while KParser does parse and analyze game data, the manner in which it interacts with the game is more akin to FRAPS, which is known to be allowed, or even simple screenshots (eg: the screenshot you posted as a record of the conversation with the GM). FRAPS keeps a record of what occured in the game using video; KParser keeps a record of only the text that came through the chat log. Everything it displays is merely an analysis after the fact.

[fndragon]

However there is one slightly ambiguous element. The GM mentioned being able to "view the statistics of players and other information". While one could easily assume it as a reference to the detailed statistical information provided by KParser, one could also interpret it as referring to players' in-game stats (str, agi, actual accuracy stat, etc), which I could certainly see as being a type of violation. There is also no context of what was occuring/being said beforehand (though if it was reported by someone, it could easily be that any issue occured well before the jailing), nor is there clarification from the GM.


As an aside, while KParser does parse and analyze game data, the manner in which it interacts with the game is more akin to FRAPS, which is known to be allowed, or even simple screenshots (eg: the screenshot you posted as a record of the conversation with the GM). FRAPS keeps a record of what occured in the game using video; KParser keeps a record of only the text that came through the chat log. Everything it displays is merely an analysis after the fact.

Yeah. I only told one person that I was using a parser, and that was only after he asked to know how I knew that his accuracy was so bad. (Ksg, the one who lol's in the screenshot). And yeah, I was only using KParser at the time. I wasn't a dick to him; I offered him some sushi on the cheap to help out his accuracy, and I also suggested that he get more accuracy gear since he was parsing accuracy at 10% below the DRG's wyvern.. So I'm fairly confident that he called a GM on me for parsing because he was angry at me for that suggestion. But I did it in the context of trying to help an XP party's progress.

And yeah, I agree with the aside as well. KParser a fairly benign third-party product, it violates the letter of the law but not the spirit. It interacts with the FFXI client in a passive way. Plus it's an open-source project, so if SE wanted to crack down on parser usage, they have a pretty clear idea of where to go to find the program. Windower, in comparision, is about 900 times worse than KParser, and people aren't getting warnings for it. And that's ignoring the 3rd party tools that are 900 times worse than Windower as well.

[Masamune]

Yeah. I only told one person that I was using a parser, and that was only after he asked to know how I knew that his accuracy was so bad. (Ksg, the one who lol's in the screenshot). And yeah, I was only using KParser at the time. I wasn't a dick to him; I offered him some sushi on the cheap to help out his accuracy, and I also suggested that he get more accuracy gear since he was parsing accuracy at 10% below the DRG's wyvern.. So I'm fairly confident that he called a GM on me for parsing because he was angry at me for that suggestion. But I did it in the context of trying to help an XP party's progress.

And yeah, I agree with the aside as well. KParser a fairly benign third-party product, it violates the letter of the law but not the spirit. It interacts with the FFXI client in a passive way. Plus it's an open-source project, so if SE wanted to crack down on parser usage, they have a pretty clear idea of where to go to find the program. Windower, in comparision, is about 900 times worse than KParser, and people aren't getting warnings for it. And that's ignoring the 3rd party tools that are 900 times worse than Windower as well.

In my humble opinion after reading that GM conversation, i'm pretty sure he were NOT refering to KParser with the sentence "...view statistics of other players".

I think may be related to your Windower plugins actually, thinking especially about TPparty and Yarnball for examples :s

Which plugins were you using ?

Also, what's freak me is that may proves SE is capable of scanning your PC without you noticing it ?

[konoko]

Well i sent some non too nice tells to ksg, and apparently he did GM you when you mentioned his acc, Nothing worse than a noob douchebag :/

[Cream Soda]

Kparse isn't detectable. You got busted because you opened your flapps.

[Motenten]

Version 1.5.2 released.

Changelog:

1.5.2 (April 13, 2010)
- Clean up synchronization methodologies.
- Several additional improvements in message handling to avoid entity mismatches.
- Fix Copy Summary on Offense tab to use display names.
- Fix AOE damage association bug.
- Fix issue with tallying followup rolls on the Corsair plugin.
- Don't display buffs/debuffs that aren't relevant to the currently selected battle(s) in Buffs by Time plugin.
+ New plugin for reviewing rates that Additional Effect statuses proc.
+ New graph plugin type.
+ New graph plugin (Damage Graph) to show damage progression over time.

~ For the Damage Graph plugin, there are four basic modes of view:
~ If you set "Show Collective Damage", it displays the total damage of all players over the time spread. If it's not checked, it will show each individual player's damage as a separate line. If you set "Show Cumulative Damage", it displays the total accumulated damage over time, either for all players or each individually. If it's not checked it displays the 'instantaneous' damage at each time interval, where the resolution is per second.
~ The data can be filtered by mob as usual (primary use is likely to analyze performance over a long NM-type fight), as well as isolated by player.
~ The graph can be manipulated in various ways. For example, drawing a box around an area of interest causes it to zoom in on the selected area. Right-clicking on the graph can give you various options such as resetting a zoomed graph back to the original state, saving the graph as an image, or seeing the x/y values under the mouse cursor.

[Masamune]

is it a late April foo ? :D

Incredibly tough good job Motenten as usual, Keep up !

[Imoq]

That's odd. Is KParser closing down properly? Try just running KParser, editing the memloc, then shut it down and restart it and see if it remains changed. Also try using the Reset button in the dialog (readjust other settings as needed).

Also, check the error log ('Errors' in the About dialog) for anything recent (bottom of the file) that seems related. If there's a lot of stuff in there and you're not sure, just delete everything in the file (and save the file afterwards), then do the above procedure again and see if any new errors show up.

I have to add a "me too" to the issue another poster had and you answered here.

Everytime I open Kparser my memloc gets reset to "005801D8" and of course, it doesn't work until I put the right one (00581518, see? I even memorized that!). I already tried closing and opening Kparser, changing settings and cleanly closing it and opening again... nothing. Is there a config file / registry entry I can erase so settings just go back to default and I start from there? It's kinda annoying having to reset settings every time I want to use it . I am using 1.5.2.0 but it did happen on every version after the memloc update.

About logs, don't see anything relevant, latest show:

---------------------------------------------------------------
martes, 13 de abril de 2010 10:25 p.m.
WaywardGamers.KParser.ParserCore, Version=1.5.2.0, Culture=neutral, PublicKeyToken=null
Error severity level: Error

System.InvalidOperationException

System.InvalidOperationException: Error dereferencing memloc pointer.
   en WaywardGamers.KParser.Monitoring.RamReader.LocateChatLog()
   en WaywardGamers.KParser.Monitoring.RamReader.Monitor()

Duplicate: 1 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 2 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 3 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 4 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 5 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 6 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 7 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 8 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 9 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 10 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 11 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 12 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 13 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 14 @ martes, 13 de abril de 2010 10:25 p.m.
Duplicate: 15 @ martes, 13 de abril de 2010 10:25 p.m.

And those are from last night, no new logs/errors for today (haven't played FFXI today, working at office).

Thanks in advance for your answer, and also thanks A LOT for this wonderful tool! (gotta love the new graphs plugin, btw!).

[Motenten]

Ok, I can't seem to find a reason for this behavior. So, you'll want to look for a directory in: C:\Users\YourUserName (on Win7 and probably Vista) or C:\Documents and Settings\YourUserName (for XP), AppData or Application Data subdirectory, Local (if Win7/Vista), Wayward_Gamers, and a subdirectory like KParser.exe_Url_pyqh5cgcjfgdy5t3c2wcuywjlpar2ik (random gibberish at end will be unique for you).

Within that directory will be subdirectories for each version of KParser that you've run. If you do not save your parse data there (that's the default save location) then just delete all those subdirectories. If you do save your parse data there, go through all of them and move any parses to another directory that's user-accessible (eg: "D:\KParser Parse Files"). After that, delete all those directories.

That will get rid of all settings that KParser has saved. After that, run KParser again and you should be given a basic default config. Readjust the default save directory and verify that the memloc is correct.

If after that the memloc is still incorrect, and you used the installer version of the program, uninstall KParser and reinstall the latest version (1.5.2) and try again.

[Imoq]

Ok, I can't seem to find a reason for this behavior. So, you'll want to look for a directory in: C:\Users\YourUserName (on Win7 and probably Vista) or C:\Documents and Settings\YourUserName (for XP), AppData or Application Data subdirectory, Local (if Win7/Vista), Wayward_Gamers, and a subdirectory like KParser.exe_Url_pyqh5cgcjfgdy5t3c2wcuywjlpar2ik (random gibberish at end will be unique for you).

Within that directory will be subdirectories for each version of KParser that you've run. If you do not save your parse data there (that's the default save location) then just delete all those subdirectories. If you do save your parse data there, go through all of them and move any parses to another directory that's user-accessible (eg: "D:\KParser Parse Files"). After that, delete all those directories.

That will get rid of all settings that KParser has saved. After that, run KParser again and you should be given a basic default config. Readjust the default save directory and verify that the memloc is correct.

That fixed it

I had info there since 1.4.7.0 release, so, lots of directories were erased.

Thanks a lot!

[Xerxes]

Slight necrobump, but here's what happened to me today while using KParser:

Needless to say I won't be using it again.

i wonder how they detected the parser.

[Zirk]

i wonder how they detected the parser.

If you read the thread it was because Fndragon told someone their accuracy sucked and they got butthurt and called a GM.

[Motenten]

1.5.3 released.

1.5.3 (April 25, 2010)
+ Added reporting of multi-attack rates for ranged weapons in Extra Attacks plugin, for new magian weapons.
* Change default options for Damage Graph plugin to Individual/Cumulative. I believe that will be more useful for most people.
- Fix minor bug when filtering counters in Defense plugin.
- Fix minor bug in WSRates plugin.
- Fix parsing of interruptions of ranged attacks by moving.