Please send me this log file at and i can find out what is up.īased on the responses from this thread, it is clear that the healing from Force Armor/Static Barrier cannot be calculated through the parser. It sounds like parsec should be stringing these fights together and this is a bug. This has proven to be difficult for many reasons that I wont go into. However, I have worked hard to detect combat rez and combat stealth in parsec and combine the fights appropriately. Technically, according to the log, you have left and resumed combat thus being in multiple fights.
I haven't noticed this on my Scoundrel, however, if that happened to make a difference. The three fights were about 4 minutes long in total, so about two minutes were lost somewhere.ĭo you think this is a problem in the game's log system itself, or something in PARSEC? In-game I guess the only work around is to try to get back to the fight as quick as possible (though in the fight mentioned I'd wager my stealths only lasted for ~0.1 seconds or so). When I checked the parse, there actually were logs for three fights instead of one, and the lengths did not add up. Just now I had dummy fight of about 6 minutes, and I used my combat stealth pretty much on cooldown.
I've parsed on my Shadow and Assassin a few times, and there have been times when the logs have become messy when stealthing out and then getting back to the fight. I believe this is because of server latency on certain actions. For some reason events in the log can be slightly out of order. Timestamps are server time and are adjusted to local timezone. The parser portion of parsec is in a stand alone library and can be used outside of the parsec client easily. Bioware did not provide any resources but in the beginning i used a post that detailed the log format.
Parsec swtor parser code#
Parsec is open source so you can download the code and use it or reverse engineer it if you would like. for your statement about absorb above, how did you figure that out? Does BW tell us anywhere or did you have to tediously reverse engineer it?įYI: I'm particularly interested in PvP tanking and trying to get numbers on shield mitigation.Īnother question: if I merge my log with someone else, are the timestamps in each of our logs client time or server time? If they are local then it is possible that merging and sorting via timestamp gives an inaccurate view of the sequence of events.Īnything I can do to avoid repeating someone else's reverse engineering work would be good. How can I figure out exactly what the combat log is telling me? I've seen the post with the combat-log-key.jpg and that helps a lot but leaves a lot of questions unanswered.Į.g. Tangent : I'm writing my own combat log parser for fun (not real-time, crappy ascii reports) and have the following question: The best I could offer on the heal tab would be a count of force armors that you cast. The "absorbed" stat on the Damage taken tab indicates damage that was absorbed via these abilities. IE: All of the Kolto Probe timers could be assigned to one timer window, then boss fight event timers could go in another one somewhere else on the screen, etc.Unfortunately there is no way to differentiate damage absorbed by force armor from any other absorbing effect such as Blade Barrier.
Parsec swtor parser windows#
Anyway, something like that would be amazing for Kolto Probe, etc.Īlso, I could eventually see the timer window getting pretty huge if a person were to use that above feature as an operative/scoundrel and then try to time a few more things, so it might also be cool to have multiple timer windows down the line. Maybe have a reserved string in the timer name that would get replaced with the target's name when displayed in the timer window. Probably would also need to include the target's name in the timer name automatically to help differentiate them. Then, if Parsec detects another trigger for that timer, and the target matches an existing timer's target, it updates that timer. IE: You'd setup the timer as normal, then for Multi Timer Mode you could select something like "Target Dependent".
Nice job, but one thing I think would be a huge improvement is an option to have timers duplicate based on target.
0 kommentar(er)
