Working Parser?

[nekura]

Well, ffxiparser was more in reference to its functionality than as a suggested application title. As for wanting to see it on Sourceforge, that's completely understandable.

[Zhais]

Well, ffxiparser was more in reference to its functionality than as a suggested application title. As for wanting to see it on Sourceforge, that's completely understandable.

If you haven't started doing so yet, I may go ahead and get it uploaded to sourceforge and figure things out that way since I worked with it a bit before.


edit: so, names anyone? I'm horrible at coming up with names >.> BattleParse? BestParser? Z-Parse? (yarite) Project Parse?
Meme names: ParseForGranite Parser9001 SafeParse


double edit: quit staring at me ;;

[Hakamaru]

Ah, I thought you had renamed the project ffxiparser. My mistake. I appreciate the gesture (as I'm sure anyone interested in the parser does as well), but 3rd party hosting is the way to go here.

As for the naming thing... lol, you can call it whatever you want. The source is still gonna have DVS's name all over it. Tell us what to call the project that will make everyone happy, and someone (/stare zhais) will make the sourceforge repository.

[Croaker]

its come to my attention that dvs stole the chat parsing code from another well known FFXI program maker.......

....who learned it from someone else, who learned to program from a teacher in school, who learned it from his father, who got the idea of parsing while working in a post office, ect, ect. Everything in life is borrowed from someone else in some fashion. Assuming you are correct, this other persons contribution was likely minor and DVS never charged money for the program, so I don't understand why you are so annoyed.

I love my DVSparse and I am very thankfull to its author or authors, their cats and whomever else may have contributed.

[nekura]

Well, ffxiparser was more in reference to its functionality than as a suggested application title. As for wanting to see it on Sourceforge, that's completely understandable.

If you haven't started doing so yet, I may go ahead and get it uploaded to sourceforge and figure things out that way since I worked with it a bit before.

I haven't, so if you want to feel free. :)

I'm just accustomed to using my site for SVN hosting due to a combination of various school projects plus the school's SVN server sucking (well, when I went there at least), so I've never really looked into using Sourceforge for hosting and it's probably better someone else does it. :D

And no worries Haka. :) I hate naming things (not exactly a good thing for a writer, heh), so for code projects I tend to not worry about such things until release time. :P

[Zhais]

edit: naming the project NoNameParser for now, I'm sure I can change it later. Or atleast just have the files named differently if need be.

sourceforge reviewing the project request now

[Croaker]

edit: so, names anyone? I'm horrible at coming up with names >.> BattleParse? BestParser? Z-Parse? (yarite) Project Parse?
Meme names: ParseForGranite Parser9001 SafeParse

Going with the "something borrowed" theme, I suggest Project Fight Club with the popular soap logo, but maybe change the soap to blue to reflect the value added contributions that will be made.

http://www.layercake.net/wp-content/...07/07/soap.jpg

[Hakamaru]

DirectParse? Since it parses directly from FFXI program memory as opposed to indirectly through the logs.

Any objections or better suggestions?

[Alleya]

taj said he would fix it or code a new one

He better implement my idea.

what was your idea? maybe I can implement it into 1.7.3

I totally forgot about this thread. But no, it's a very mean idea and you wouldn't like it.

[Zhais]

DirectParse? Since it parses directly from FFXI program memory as opposed to indirectly through the logs.

Any objections or better suggestions?

that works.


and what is it alleya!

[nekura]

taj said he would fix it or code a new one

He better implement my idea.

what was your idea? maybe I can implement it into 1.7.3

I totally forgot about this thread. But no, it's a very mean idea and you wouldn't like it. :p

Sends "/p gtfo the party" when someone's not pulling their weight? :P

[Skeetaru]

Ok, here's the modified DvsParse I've been promising. I added a config file named "DvsConf.txt" to the directory. Currently the only thing it understands is 'MEMLOC=<number>', but it would be simple enough to add other configuration types to this file.

Hopefully this is the last DVS parser most users should have to download for a long time. Whenever FFXI is patched, all you have to do is come to BG and see what the latest MEMLOC is and update DvsConf.txt on your own.

If anyone wants the source to merge into their own tree, let me know. It's not a large or complex change.

So is the consensus that this is the Parser we are using now? With all the posts and reposts and links in this thread i really dont know what works and what doesnt, so short of DLing them all could someone confirm?

[Hakamaru]

Ok, here's the modified DvsParse I've been promising. I added a config file named "DvsConf.txt" to the directory. Currently the only thing it understands is 'MEMLOC=<number>', but it would be simple enough to add other configuration types to this file.

Hopefully this is the last DVS parser most users should have to download for a long time. Whenever FFXI is patched, all you have to do is come to BG and see what the latest MEMLOC is and update DvsConf.txt on your own.

If anyone wants the source to merge into their own tree, let me know. It's not a large or complex change.

So is the consensus that this is the Parser we are using now? With all the posts and reposts and links in this thread i really dont know what works and what doesnt, so short of DLing them all could someone confirm?

I sent the source for the build I posted there to Zhais. When he makes the sourceforge respository, I would assume it will be using the code that generated that binary (unless he made changes since last night). Then I'm sure things will evolve from there.

[Amele]

Ok, here's the modified DvsParse I've been promising. I added a config file named "DvsConf.txt" to the directory. Currently the only thing it understands is 'MEMLOC=<number>', but it would be simple enough to add other configuration types to this file.

Hopefully this is the last DVS parser most users should have to download for a long time. Whenever FFXI is patched, all you have to do is come to BG and see what the latest MEMLOC is and update DvsConf.txt on your own.

If anyone wants the source to merge into their own tree, let me know. It's not a large or complex change.

So is the consensus that this is the Parser we are using now? With all the posts and reposts and links in this thread i really dont know what works and what doesnt, so short of DLing them all could someone confirm?

zhais has a link in his sig to what I've started referring to as 1.7.4 (which is exactly 1.7.3 but with the new memloc) I would assume that is the version we will start the new trunk with.

both versions are currently working and the one you asked about will allow you to more readily fix the parser post update (since it won't require waiting for us to do a recompile) although only if you know enough / care to learn enough about how to trace the pointers in the memory map to resolve the new base pointer address yourself.


my vote is for GraniteParser (don't take this for granite!) but only because I find that meme quite amusing. I don't really have a vested interest as long as we don't make it something lame and trademark infringing like iParser. D:

[Plow]

"Hard Work Parser" imo

[Breemer]

i like directparse and graniteparse lol

[Bestovian]

Any options with "Insert New Name Parse Here" that allows you to track the number of WS like what is tracked with lildevil? Its really hard to get an accurate WS average with "OLD DVS" as it really is just your Hi/Low and the average is in between the two.

Would really make testing a little easier especially will the updates with WS damage.

[dvsparse]

Its really hard to get an accurate WS average with "OLD DVS" as it really is just your Hi/Low and the average is in between the two.

No it's not, the average is correct.

[VZX]

Haven't have chance to open the source yet =.=
How come the add effect is not parsed?

[Tanag]

I like GraniteParse.

It's fitting, since most of the community takes these apps and the work put into them for granite.