![]() |
#1361
|
|||
|
![]() I challenge you to put in the sweat equity. Join a fast moving high dps group. Play pure offense and show us the numbers you can manage fight after fight after fight. Aggregate or break separately all you want. I recommend using a parser. Do the thing you claim you can do.
[You must be logged in to view images. Log in or Register.] But I know you won’t. If you did, I already know what the numbers would show. Maybe you do too which is why you are unwilling. Until you grow some balls (and preferably a few more brain cells to rub together), you have effectively conceded that you are wrong. And since you’re wrong … back to amusing GIFs!
__________________
| ||
#1362
|
|||
|
![]() [You must be logged in to view images. Log in or Register.]
__________________
| ||
#1363
|
||||
|
![]() Quote:
My video/log evidence trumps your parse data you claim is wrong. I see you didn't respond to what I said, and are instead going back to copy/paste.
__________________
| |||
Last edited by DeathsSilkyMist; 08-31-2022 at 05:14 PM..
|
#1364
|
||||||||
|
![]() Quote:
All I can do is re-state the facts in continued effort to attempt to continue the discussion(s) in a civil manner. The ball is in DSM's court. Quote:
Quote:
Quote:
Quote:
| |||||||
#1365
|
||||
|
![]() Quote:
I ask because in the parser I whipped up while babying this big ass data migration at work...that was a standout issue that had to be addressed in the data. I used the first attack after a "so and so has been slain" line to capture the fight start time, then the slain message to capture the end time, but a few of those fights I had to run for whatever reason so it thought the fight was very long skewing the DPS for that "fight" to be extremely low which fucked with the averages. On one hand the logs in EQ are pretty solid for parsing since the messaging is super uniform, on the other, its easy for shit like that to fuck with the data because it can be difficult to adequately identify when combat "starts" and "ends". For instance, if you have multiple mobs, you have multiple kill messages, knowing when to start capturing data is easy but knowing when to stop can be difficult (i.e. how long you should wait until your parser decides combat is officially "over" and you aren't just waiting for the tank to get aggro on the second mob kind of thing). | |||
#1366
|
|||
|
![]() Yeah parser is great for individual fights but it gets weird with aggregate. I almost regret posting the aggregate with the explanation. It was a mistake because DSM is apparently unintelligent and basic reading comprehension and abstract reasoning is beyond him.
__________________
| ||
#1367
|
||||
|
![]() Quote:
Troxx hasn't provided logs, so we don't know if he lost data, or how his parser is handling the data.
__________________
| |||
#1368
|
||||
|
![]() Quote:
__________________
| |||
Last edited by DeathsSilkyMist; 08-31-2022 at 05:25 PM..
|
#1369
|
|||||||||
|
![]() Quote:
Quote:
All I can do is re-state the facts in continued effort to attempt to continue the discussion(s) in a civil manner. The ball is in DSM's court. Quote:
Quote:
Quote:
Quote:
| ||||||||
#1370
|
|||
|
![]() Imagine living with this guy, yikes.
| ||
![]() |
|
|