ParserFollow

Ok, first, do you have the pref set to select the process to monitor?

Following the break point where you get the trace message (and continue stepping through with F10, checking values as you go), you have one of two ways of filling the polProcesses[] array, depending on whether you selected the process or not.

If you did select the process, did it select the correct one? If you did not select the process, did the program find the pol.exe process in its query?

If the pol process you expect is inside the polProcesses[] array, continue.

If it found a pol process, it's going to try to find the ffximain.dll module within that process. Look at process.Modules when it gets to line 681; is ffximain.dll in that list?

This seems to be the most likely failure point if you were constantly seeing the output from
Trace.WriteLine(Thread.CurrentThread.Name + ": Attempting to connect to Final Fantasy.");
in the output log, but not seeing
Trace.WriteLine(string.Format("Module: {0} Base Address: 0x{1:X8}", module.ModuleName, (uint)module.BaseAddress));

If that does seem to be the failure point then look through the module list to find the dll used in the test server install. If this is not the failure point, get back to me.

KParser options, not Visual Studio options. In the Tools/Options dialog box.

The no name thread exiting doesn't matter; it's a debugger thing.

WOW is part of Windows itself (stands for Windows On Windows). It's the system that allows 32 bit programs to run on a 64 bit machine.

When you break the debugger at line 681 with the appropriate process, hover your cursor over the process.Modules variable in the code window. It should bring up a tooltip-like window with more info about the variable. When you hover over one of the sub-items, it pops up more details about that item, etc.

You want to look at:

process.Modules - base - Non-Public Members - list -

There should be a count of attached modules (mine has 61). Right click on "list" and select "Add Watch". That brings up that variable in the Watch window (should show up at the bottom of the IDE). Expand that at look at the values available.

Obviously, you should be in the full-fledged version of the game at this point. If you're still just in POL it won't work.

Anyway, try to locate ffximain.dll or something similar. Best bet is to look in the install directory for the test server version of FFXI and look at the dlls listed there, and see if any of them show up in the modules list. There's like 5 in the normal FFXI installation directory, so it should be easy enough to track down.

If you can find a new dll that you think matches what you're looking for, replace the text "ffximain.dll" on line 683 with that new dll name and try things again.

Only 5? Ahh.. ok, try this. Shut down VS2010, and open it again by right clicking and selecting "Run as Administrator". Then try tracking through again.

I'd only expect to see just 5 modules if you're not running as administrator. Another program I wrote does the same thing if I forget to run it as admin. You -should- be seeing tons of modules (as I said, there are 61 modules attached to pol on my machine).

Since you're running VS in admin and not seeing it... Well, actually, it should have prompted you for a permissions upgrade when you tried to run KParser before, if you hadn't started in admin mode, since KParser requires being run in admin mode all on its own.

Hmm.

New memloc for Sept patch: 0x005858d8

1.5.14 download available.

Hmm. There's really no good way, since kicks have different damage ratings than punches, and you only get one kick per round, which means you can't just swap in DA for it. Probably the "easiest" way would be to take the mnk spreadsheet and readjust all the base numbers (skill, 0 base kick rate) for pup, then add in the gear you want to compare. Messy, but less annoying than doing the statistics for adding kick attacks to pup's.

I was just going to come in and ask if this was in the program somewhere, or if you were going to add it lol.

Regarding the spreadsheets rather than the parser, but for TaimMeich since he posted here: Rebuilt the pup spreadsheet with the new format, and added in handling of kick attacks. Fixed a few bugs along the way as well. Doesn't fully account for AF3 set bonus yet, though (effect should be very minor).

I tried to use your new "invalid memlock" thing to make it parse the Test Server. It finds my character, but does not parse. I think that's the same problem I was having before. The test server client is the only version of FFXI open and the memlock is set to 00FFFFFF.

Perhaps I'm accessing it wrong or looking in the wrong place, but error.txt in the Kparser folder still has stuff from September 28th and nothing new.

I e-mailed you part of my error log.