I know I'm bumping an old thread here, but I wanted to make sure everyone knew that I'm still around and still working on the parser (when I have the time). I appreciate all of the feedback that I get and I do my best to respond and discuss future options and capabilities. On that note, I know it's been over a month since my last update and I wanted to let everyone know that I pushed out a new version today. Version 0.9.9.3 includes a human readable live combat log for those who want to be able to examine the details of their combat quickly and easily while playing. As always, my latest release notes are on my web site for those who are curious. I also wanted to say thank you again to all of the MOX parser users out there and I hope that the tool is still serving its purpose.

There are a few reasons, but mainly it has to do with performance and load balancing. I don't want too much data stored under a single key for when you go to look at it on the web site. It's also part of how I'm managing my infrastructure on the back end.

Are you all synced to the same raid key? Are you all running the latest version of the parser? Proximity should have no effect on the tool. However, you do need to be in combat to see numbers. For example, if you're hanging around outside the instance and people are fighting inside, you won't see their numbers. It could be other general network problems as well (which would be tougher to diagnose). The people who aren't showing up, are they getting updates and seeing the same numbers as everyone else?

Are you guys using the latest version of the parser? There were some pretty significant performance issues that I addressed in version 0.9.7.0. That being said, the parser is relatively processor intensive so its not surprising if its taking up small chunk of your CPU power while its active. I've contemplated some other performance improvements, but haven't made any yet. I know there is still some room for improvement there though. Either way, it shouldn't be so bad that its causing your game to run poorly, that is certainly not the average user experience.

I noticed this thread in dev tracker and just wanted to clarify a couple of things. 1) MOX Parser is not doing anything malicious and it is not doing anything to violate SWTOR's terms of service. It is purely accessing a text file, it just happens to be a text file created by the game. 2) There are several thousand people using MOX Parser everyday and I'm pretty sure you would hear a lot of complaining if Bioware started banning that many people everyday for it. 3) If for some reason you were banned in error, unfortunately all you can do is attempt to go through customer service (as previously mentioned in this thread). If anyone really was banned for the reason of using MOX Parser and you can provide a ticket from a CSR as to why, please send it to my email (on the web site). If it's anything I can help with, I will try.

So, there are definitely slight differences in the duration. On the Bonethrasher fight, for example, its a difference of 6 seconds. There's a couple possibilities for this discrepency: 1) Right now, I'm using the raid leader's duration to calculate those DPS figures on the web site. If for some reason, your leader's state was off (his character was dead, he was lagging, etc.) then you can see slight differences from the duration in your log. 2) They are calculating the end of combat differently than I am. If there is some residual damage at the end of the fight, I may be adding that into the total duration (a lingering DOT for example). Exiting combat can be inconsistant across 4/8/16 players. Those things being said, there are some things I could attempt to do to fix this. I could try averaging the duration across multiple people to maybe get it more accurate. Or I could not add to the duration when dealing/receiving damage after combat is completed (this is possible, but I don't know if that's what is going on here). In general, the dps I'm showing is meant to be a relative comparison (within that fight), but I understand it has value if it can be accurately compared between fights. I'm definitely keeping this stuff in mind for now though.

Could you please email me your log and I will take a look at it? This issue is a pain and I really want it fixed.

^ This I'm being very careful not to do anything that would violate any of the games terms and this is the first I've heard of this "incident". If for some reason this really is true, please tell this person to feel free to give me the exact details of what my program violated.

I agree this can be frustrating and happens because you're taken briefly out of combat between Z&T and the handler. Due to the nature of how the raid data is compiled, I don't plan on having a dropdown in the tool for past raid fights, that is the purpose of the web site. I know the archived fights on the site have had a lot of issues, but I've been working a lot on it and we ran an 8 man raid last night and for the first time it actually recorded every pull correctly for the whole night. So, I'm finally starting to feel better about this. (I'm sure its not perfect though)

I'm sorry to hear that people are having problems with anti-virus applications. I assure you there is nothing malicious in my application. I've ran my files through the scanner at https://www.virustotal.com/ and nothing is being flagged by any of the vendors on there. If you wish to continue using the tool, there should be a way to mark the files as safe to prevent them from being quarantined and allow them to run. There are 2 executables that are involved. The first is RunParser.exe that you get from downloading the zip file off of my site. When RunParser.exe runs for the first time, one of the files it will download is MOXDesktopParser.exe. Both of these should be marked as safe if you are having problems. I apologize to those who are having problems and I wish I knew why my files are being flagged.

Sorry I didn't post an item for it (I did now on the site), but 0.9.6.5 was a quick follow up fix to the overflow crash bug. Also, I just pushed out 0.9.7.0 which has a fair amount of changes and new things. Here's a summary of the changes: • Added a new tab for damage absorbed (under the personal tab) • Added mitigation data to the personal damage taken section (hits, misses, dodges, etc.) • Added another fix for in-combat revives • Added scroll bars to the main client panes • Fixed a bug that could cause the entire application to freeze • Improved the performance of the client • Improved the rendering of the client (and pop outs) Note: Damage absorbed and mitigation data will not been seen on the web archive yet (still working on this).

I appreciate you posting this and I am aware of this. In most cases it could be decently accurate, but certainly not in all. Tracking modifications to threat can be difficult (or impossible). For example, the threat reduction from talents. I have no way of seeing this and it is different on each class and there's the possilbity that you didn't put any points into it at all. Other threat reducing things can be tracked (although it may be more difficult). For example, being shielded by a tank. These are other modifiers that I would have to track and even then, it may not be completely accurate. Personally, I would rather its just added to the logging so that there is no question about it. I know its an important stat to healers, but if its going to be very time consuming to implement and not necessarily accurate, I am not inclined to work on it. There are other issues that could be more easily tackled that will provide value. If anything, you should petition Bioware to add it properly to the logs (along with healing from shields). Healing is probably the most poorly logged statistic in general right now.

This will hopefully be less of a problem with the latest version, the last item was related to that: "Made an adjustment to how end time and duration are calculated on failed attempts ("wipes")" Also, for now i have been counting time while dead since I am tracking total time of the encounter (in the event of being revived mid-fight). I could attempt to track time alive more accurately, but that could produce other bad results. For example, I apply a bunch of DOTs and die, I will be dealing damage, but not alive. For these reasons, I'm not a big fan of DPS, its a very point-in-time type of statistic. I've considering re-writing my calculated DPS to be more variable and not just an average for the entire duration of a fight. Both can provide different insights. For now, I hope that sheds some light on the subject. Also, on an different note, I had a fix failed scenario with the bad int32 crash during my deeper testing. I fixed it and pushed another update this evening (0.9.6.5). I apologize to anyone on 0.9.6.4 that is still getting that problem.

Thanks again to everyone for the feedback, suggestions, bug reports, etc. I know there are a lot of feature requests/improvements out there and I want to get to them, but stabilizing the tool and my infrastructure are top priorities. With the said, I feel like things are working rather well at this point. I just rolled out a new version today (v 0.9.6.4). Here's a summary of the latest changes: • Fixed a crash involving the raid healing popout • Fixed the overflow/bad Int32 crash • Fixed a parsing error involving incomplete time stamps • Jedi Shadows should no longer have their stats reset when using Force Cloak during combat • Made a fix to in combat revives • Made an adjustment to how end time and duration are calculated on failed attempts ("wipes") Known Issues: • Scoundrels are still having their stats reset when vanishing during combat, I need one to please send me an email with a sample scoundrel log so I can get this taken care of Like I said earlier in the post, I feel like things are getting much more stable/accurate. There are some specific things I'd like people to keep an eye on: Vanishing mid-combat should be fixed for shadows, operatives, and assassins. If you are one of those classes and are still having problems (under the latest version), please email me a log sample. Raid archiving is now working significantly better (at least it has been in my tests). If anyone is seeing any major problems with their archived fight data (e.g. missing fights completely, very bad/inaccurate numbers, etc.) please email me your raid key and I can look into it. If you get any crashes/errors please try to email me with any relevant data you can provide. People have been very helpful thus far in helping me identify specific problems very quickly (Thank you!) Feature requests are great and I'm doing my best to keep track of what's important and desired by a lot of people. Please be patient, I am reading your ideas and I do plan to continue to add and improve this. Thanks again for everyone's support.

I pushed out an update earlier today (v 0.9.6.0). The following items were fixed/changed: • Fixed the "index out of range" crash. • CC abilities that heal will no longer count towards healing done. • When using raid meters, your name will be highlighted. • Raid dps/hps can be seen by right-clicking the respective popout and selecting the toggle dps/hps option. • Being resurrected in combat should no longer reset your stats. • Vanishing during combat should no longer reset your stats. • Failed attempts (wipes) should now be archived. • Other minor archiving and performance updates.