Chronogami Displacer console and community run parsers (SCM, CLR)

xgamefreakz

Hi, this is regarding the recent event universal console, Chronogami Displacer.
This is technically not a bug so its not being placed in the bug section.



The recent patches to fix the console has made the active of the console very appealing in terms of performance.
However, when being parsed by the 2 most used community run parses, SCM or CLR, at the moment the damage done by the console does not count under player damage, it is being counted as Core Breach damage, which is separate from player damage.

This is because the way the 2 parses work at the moment, it categorizes any damage line with the word "Core Breach" (Case-sensitive) as such.
It therefore does not count towards the overall player DPS.

Damage lines between the Chronogami active ability and an actual player warp core breach:

23:05:18:12:06:17.5::Fletcher,P[7960137@12982536 Fletcher@xGamefreakz],,,Cube,C[15 Space_Borg_Battleship_Raidisode],Chronogami Displacement Core Breach,Pn.7myc941,Kinetic,,8301.51,83015
23:05:18:12:11:11.3::Fletcher,P[7960137@12982536 Fletcher@xGamefreakz],,,Cube,C[15 Space_Borg_Battleship_Raidisode],Warp Core Breach,Pn.X9p5ua,Kinetic,,1626.71,16267.1

If the damage line the console produces could be changed in the slightest way, that would be nice.

legendarylycan

50K doesn't seem very appealing.

And I'd still like to know what that 2-piece is supposed to be - of course, it would help if the game actually REPORTED all set effects in the details menu 100% of the time.​​

baddmoonrizin

Sounds like you're talking about third party programs, which Cryptic has no control over. You might want to talk to whoever maintains those programs.

phoenixc

baddmoonrizin wrote: »

Sounds like you're talking about third party programs, which Cryptic has no control over. You might want to talk to whoever maintains those programs.

It could be fixed on either side, on the game side by renaming the damage so that it is formatted as weapon damage and lists the Chronogami as the weapon without the keyword spelling of "Core Breach", or it could be done on the third-party side by checking all lines of core breach damage for the word "Chronogami".

The former would be the best for parsing performance most likely, and it should also help with the Cryptic-made parser too if it is listening to the same damage stream.

leemwatson

phoenixc#0738 wrote: »

baddmoonrizin wrote: »

Sounds like you're talking about third party programs, which Cryptic has no control over. You might want to talk to whoever maintains those programs.

It could be fixed on either side, on the game side by renaming the damage so that it is formatted as weapon damage and lists the Chronogami as the weapon without the keyword spelling of "Core Breach", or it could be done on the third-party side by checking all lines of core breach damage for the word "Chronogami".

The former would be the best for parsing performance most likely, and it should also help with the Cryptic-made parser too if it is listening to the same damage stream.

This shouldn't be touched because the argument than would be why Core Breaches aren't being allocated to players from ANY source. The console creates a core breach from another ship, not your own, so it does not count towards your DPS.

xgamefreakz

leemwatson wrote: »

This shouldn't be touched because the argument than would be why Core Breaches aren't being allocated to players from ANY source. The console creates a core breach from another ship, not your own, so it does not count towards your DPS.

The code for those parsers were made a long time ago. Core breach damage are separated and do not count because its free damage done from dead things. Somebody flying right into a pack of enemy and getting themselves killed should not count doing a portion of DPS, back then when whatever DPS it would have done was a bigger portion. Neither should warp core breaches from dead NPC count towards NPC DPS either. This principal does not apply to the chronogami console.

Some of the parsers have a better way of categorizing warp core breaches, and as tested at the moment, have no issues counting the chronogami console as player damage while still separating warp core breach damage. Just bad luck the parsers we mostly use looks for "Core Breach" in the damage line.


I had low hopes for this but had to try anyway, after multiple patches, this console does obscene damage now, also recharges to 12s upon killing a battleship or above .

Should easily be best in slot on an epg RATFO build. For parsed runs however, zero damage.