Apologies for the server problems lately. As you have noticed, SWMoniTOR has not been getting a lot of attention from me recently (I'm not actively playing anymore) and our forums are FUBAR now that the botters have broken Captcha for account validation. We've tried to find some work arounds for the forums but short of spending several hours a day cleaning them up, they are pretty useless now unfortunately. I can't believe it's even worth the trouble for these spammers to even make posts like this. Does anyone ever actually buy anything from them!?!?! Anyway, I've noticed that the server recently has gotten some strange error that I will be looking into when I can get some time away from my RL projects. In the meantime, if it seems that the server has crashed again and you can't create a group at all, you can contact me at makya@swmonitor.com. I won't be able to provide detailed technical support for every question but I will be able to bump the server until we can get a fix in there.

Our raid had similar problems, 3 of the 8 of us were getting constant kicks to the select screen. We called raid and then after I logged into some of my alts none of them appeared to be in guild anymore, including my main who is GM. Will be interesting to see what it's like when things restart.

Nope, the existing version should work fine. It doesn't yet use the new unique enemy ID but it will continue to function.

With the SWTOR 1.3 update the logs will be getting information in them that includes unique identifiers for each enemy even if they have the same name. To filter all incoming damage on a specific player do this: Double click on the encounter, double click on the player (Players tab), double click on "Damage Total (in)" (Summary Tab) and then select the Details tab.

I looked on the BitDefender website and didn't find any information on how to get them to actually check that the contents of our website are safe. I cannot even use their support form since that requires a serial number (I did however send a message to their sales contact point but I doubt anything will happen from that). If you can find some way for us to "fix" this please let us know. And for some related information on the accuracy of BitDefender you might want to read Bad BitDefender Update Clobbers Windows PCs from a few years ago.

As you said, you can use MoniTOR to join the logs in realtime and then you don't need to rely on everyone to upload the logs to askmrrobot after each raid by one of the leaders. More analization tools and easier to digest data graphs/display are on the way as well to help analyze things post-wipe and make the proper adjustments. Tracking overheals and blowthrough heals are in the works and while not 100% accurate given the current data provided in the logs, it should be pretty close. The threat display will be undergoing some dramatic changes to show hate positions for each individual enemy (something that is coming in the SWTOR 1.3 update). As for anyone focusing too much on any of the meters, the display of them are of course optional if they are too distracting. IMO, after the newness wears off, it's not likely something to be "stared" at anymore than you stare at the speedometer or odometer in your car while you are driving. Not sure if this was where you saw the negative threat but on the minefield fight in Denova the boss does a memwipe every so often (the red message about him changing targets) that throws up a large negative hate value for those with a lot of threat (i.e. the tank). A few videos would be a great idea. I'll look into those after we get this next update out. Thanks a bunch for the feedback!

I've noticed some pauses and lag myself since the server transfers so I doubt this is related to running MoniTOR or other 3rd party processes. We worked very hard to make MoniTOR as efficient as possible during combat in terms of both memory and CPU usage (on my computer it rarely gets above 1% CPU usage). Thanks for trying MoniTOR though and good luck.

MoniTOR adjusts all of the incoming data to your timezone so when you are examining the logs it should show times within the same timezone (yours). The problem we have fixed is related to the Windows APIs we were using to adjust the times from local to UTC (for transmission to other users) and then back from UTC to local (when receiving data from other users). These functions appear not to work properly on some systems (corrupt registry or something else) and so the times are not converted properly. The next release of MoniTOR will be using an alternate method to sync up the times.

We're getting very close to releasing a new build that should fix a lot of the connection issues that some players are having. There are also plans to spruce up the graphical output and analyzing tools as well. In my previous raiding game (EQ2) we used ACT a lot so I'm quite familiar with what it did and we'll be making MoniTOR do all of that and much more. In the meantime though, you can use MoniTOR to join all the combat informat together and then output the raid data to combat log format (it's the save to .TXT option on the Parse Viewer in MoniTOR) and then import that into ACT or even better upload it to Ask Mr. Robot to see something with a bit more graphics.

I've had something like this reported before and I suspect it's due to an invalid timezone setting on one of the player's computers (thus making the duration of the fights realllllly long). We've got a fix for this for the next release but if you could look at the details to see if it looks like some of the times are an hour or several hours off that would help confirm this is what is happening.

A quick note to everyone that we're still working on the next release for SWMoniTOR that includes quite a few changes in the connectivitiy area to handle those users with problematic routers (symmetric NATs) and some other nice additions to functionality as well. For those that are testing the 1.3 update that is currecntly on PTS, we also did some testing with the new log format and the good news is that the current SWMoniTOR parser already works with the new format (although the UI doesn't yet do anything with the new per-enemy IDs). We will be including some cool support for these new ID numbers soon as well as supporting any other changes that Bioware does to the logs. Hopefully more new combat log features are on the way from Bioware .

I haven't yet seen this in any testing of MoniTOR. One thing that might be going on is someone may have their timezone settings corrupted on their machine so the times are coming in really far off from the rest of the group (thus messing up the encounter durations). We did get a report for some incorrect timezone information from one user so this might be a more common "problem" on some machines that we'll need to find a way to work around. The current plan is to provide a timezone selection in the configuration rather than using the Windows APIs to do the conversion for us (which is where the problem is).

Just an FYI, there's a good thread already running with a whole list of suggestions for the devs (it's a carry over from the 1.2 beta thread). http://www.swtor.com/community/showthread.php?t=401531 Sure hope some combat log additions are in store for 1.3...

We've released a new version of the SWMoniTOR launcher program to fix all of the false positive anti-virus reports from the past few days. The fix was as simple as using a newer version of the internet library (which is open source) instead of the original version that came with the compiler. Just goes to show how misinformed quite a few anti-virus software programs are when they use generic internet library code to "identify" a virus/trojan instead of the actual virus/trojan code itself (which of course didn't exist in MoniTOR). Virustotal.com scan (0/42 results) Below are the patch notes for this installer/launcher only release (client application is still the same version as the previous release). If you have been having problems running MoniTOR because of your anti-virus software, please redownload and reinstall the installer from the SWMoniTOR website. Launcher Updated the internet library used by the MoniTOR launcher to a newer version which should no longer generate false positive reports in anti-virus software. To update to this version download and re-install the main installer from the SWMoniTOR download page.

Thanks for recognizing this as a false positive report (more details on the SWMoniTOR website FAQ about false positives for those that are concerned). I'd also recommend reading this blog (not written by me) that describes how anti-virus companies cause a big headache to small developers. I encourage anyone that gets a false positive report to send in the reported file (typically SWMoniTOR.exe or SWMoniTORClient.exe) to the maker of your anti-virus software so that they can verify it is not harmful and can adjust their detection methods to be more accurate. Unfortunately most companies don't really generate their own detection methods and just subscribe to common lists or use automated systems to generate signatures without actually verifying the file is actually malicious. Keeping your computer safe is extremely important but using a anti-virus program that doesn't allow whitelists of known good software or is overly aggressive on detecting/cleaning usually causes more problems than it's worth (which is unsafe since it eventually leads to the user uninstalling the anti-virus software). The two programs I use are Microsoft Security Essentials (comes with Windows) for the basic stuff and another excellent program called Malwarebytes (there are other good programs out there as well). I can scan anything that I download with Malwarebytes, schedule a whole computer scan when I'm not using the computer and it even blocks known websites that carry trojans/malware (which is the most common vector for most computer infections today). Malwarebytes also has very good detection methods with no false positives reported even though I've been using it for over 5 years. It's detected and cleaned up other computers that I've been called in to fix just fine though so I know it works on the real positives as well .