Cool idea, maybe it will make it in to a build.

Technically, according to the log, you have left and resumed combat thus being in multiple fights. However, I have worked hard to detect combat rez and combat stealth in parsec and combine the fights appropriately. This has proven to be difficult for many reasons that I wont go into. It sounds like parsec should be stringing these fights together and this is a bug. Please send me this log file at support@parsecparser.com and i can find out what is up.

Any possibility you can provide more information about what is wrong with it?

Parsec is open source so you can download the code and use it or reverse engineer it if you would like. Bioware did not provide any resources but in the beginning i used a post that detailed the log format. The parser portion of parsec is in a stand alone library and can be used outside of the parsec client easily. Timestamps are server time and are adjusted to local timezone. For some reason events in the log can be slightly out of order. I believe this is because of server latency on certain actions.

I think it would be really funny to ride around on top of an NPC that has a jetpack or jet boots as a mount

Its not just about the bantha. In my guild we collectively opened over 150 packs. Not a single person got a single weapon. There are 6 weapons in the pack? In fact I have asked in fleet all day and not a single person responded that they got a weapon. I am wondering if they are even in there...

The desler is not a rare.

I agree... I opened 60 packs and got 1 rare mount, no pets and no weapons.

So I am playing an operative during double xp weekend and though he is only level 16 his flashbang is still an aoe CC. I thought they nerfed it to be only 1 target?

These questions were so good that they nerfed Guardians. Well done.

The problem is overlapping terminology. In beta absorption was called "glance rating" this differentiated it from the health buffer mechanic referred to as an absorb shield. In simple terms: 1) The absorption stat refers to how much damage is mitigated on a shielded attack. The log file reports attacks that were shielded but does not report the amount that was shielded. 2) Absorb shields are temporary health buffers that soak up a certain amount of damage. These can be applied by sorc/sage barriers, the guardian/jugg blade barrier/barricade, the guardian/jugg aoe taunt buff and the reactive warding relic proc. These are a few of the ways you gain an absorb shield. These events are much clearer in the log since it reports how much damage was dealt and how much absorbed. Your absorption or shield ratings have no effect on these types of shields. Parsec gives you some information on both scenarios. I have tried to explain things in parsec via tooltips so if you are wondering what something is try hovering over the label or column header.

In a few months? You mean in 6 months? Dread war was oct 2013... Lame exaggeration is lame.

I am confused why you recommend to take the legacy mission xp bonus (which I assume is the Class Mission XP Bonus Character Perk) and then you recommend skipping all the class missions? I have gotten a new level 55 on every dbl xp weekend going from 0 - 55. My method is similar but I do the following: I purchase the Class Mission Character Perk and the Exploration Character perk all the way to the top level. I use the same gearing strategy as the OP except I use alts to buy mods with their planetary comms and mail them over to the new toon. I use the new toons planetary coms to keep my companion geared. I do mostly class missions on the home planet making sure I am at least level 10 when I leave. Then I do all missions the coruscant / dk except heroics (do the heroic to get the modable offhand on DK if you need it) Only Class Missions on Balmorra/Tarris Class Missions and Planetary on Nar Shadda Class Missions and Planetary on Tatooine Only Class missions on Alderaan Only Class Missions on Balmorra/Tarris Class Missions and Planetary on Quesh Only Class Missions on Hoth Class Missions and some Planetary on Belsavis Class Missions and some Planetary on Voss Only Class Missions on Corellia Belsavis Bonus Ilum only if needed to get to 50 Black Hole Section X Do one flashpoint Group finder per day for the comms and the daily missions

Yeah, I need to get a tutorial on backing up data put on the site. Anyway, here is a quick run down: 1) Open Parsec 2) Click File > About Parsec 3) Click the Data Folder This folder contains your Parsec data. CharacterSettings.xml contains each characters settings raid_combat .txt files are archived raid data TimerDefinitions.xml contains all of your timer definitions You can copy this data and store it as a backup. Then after you reinstall Parsec you can simply open the folder via the same 3 steps above, copy the data in and then restart Parsec.

The time stamps reported in the log are swtor server time. Two things can cause timers appearing to be off like this: 1) SWTOR server clock and your computer clock are not in sync. It is not possible to sync directly with swtor server clock so the best we can do is sync with an internet time server and hope that swtors clocks are synced regularly also. 2) SWTOR game lag. It is possible that the game may be delaying the visual notifications of buffs because of server server lag or game video lag. Unfortunately both of these cases are outside the control of parsec and all we can try to do is mitigate them.

I call shenanigans. There is no way this guy deleted level 55 characters, let alone dozens of them. He is full of so much S% its not even funny.

Something along these lines is on my list. However in the mean time I have tried to make it easy on those of us with lots of alts. One cool feature is the clone button. This button copies the current timer , then all you need to do is change the name and ability.

The cut scene problem is easy to fix... You cant customize your ship until you reach 55 and finish your missions. Then you can purchase a ship upgrade that has a new bigger layout that is customizable.

I have been toying with ideas to make the threat tab more useful so I will take a look. As for your second request, the timers pop out with count downs already exists

This is the top feature on my wishlist. There is no nice way to say this but people who dont want this are stupid. I was spending alot on cartel stuff but then i got tired of spending 1 million credits per character eveytime i want to switch gear sets. The system that is in place is an evolution of a poorly designed customization system into a system that offers everything that people want except that it is now cost prohibitive to change gear sets. It has worked well getting to this point but if they want to continue selling outfits on the cm they need to redesign the system.

First I will address the so called "lag" issue... Assuming your computer clock is synced with an internet time server, a Parsec Timer with a duration greater than 3 seconds should not experience any "lag". For example, Vital Shot has a 15 second duration if not specd into the longer version. You would set your timer to have a duration of 15 seconds and since the duration is longer than 3 seconds you will not have lag. Where you will see lag is when you are using durations less than 3 seconds. Such as when something procs or you lose an effect. In both of these examples you would use a duration of 0 on your timer so you would be notified as soon as possible. However, since the log is written by SWTOR every 3 seconds you run the risk of being notified UP TO 3 seconds late. Ok now that we have that understood I will address the suggestion to use a key logger... No. Not even a remote chance. This is against the TOS and you can all rest assured that I will never be implementing any such thing.

There is a nerf herder achievement on alderraan

If you like your pvp you can keep it.

Wow that sounds awesome!

You can use them to detect a proc but an alarm that sounds based on two procs is not possible in the current Parsec. Unfortunately, Parsec does not support multiple conditions for an alarm. This is something that may be in a future update but for now timers can only be triggered by one condition.