monk ratios, primary and offhand choices

[Crede]

I looted an addy club on my monk and I have been rocking that in my primary. The ratio is slightly better than the epic fist and the stun proc is great.

Epic fist in primary is the clear winner since it applies damage bonus more often, but Ada is good if you’re trying to hold aggro.

Epic fist: (9 x 2 + 11) / 16 = 1.81
Ada: (15 x 2 + 11) / 25 = 1.64

[Crede]

Incorrect again.

He provided 2 parses without logs in this thread, and couldn't even tell us the weapons the other players were using. I asked him multiple times too.

With parses alone we also lose context, so we don't know if any factors were affecting DPS.

It would be great if he actually provided a few parses with both Cek Sword and his BiS 1h setup. If he gave us the logs, I could plugin in his data to my formula provided below, and we can see if it holds up. Other posters could provide data too!

https://www.project1999.com/forums/showpost.php?p=3708955&postcount=440

It would be great if you could actually provide evidence of a shaman doing more than 20 dps in a group by mass root rotting adds while the rest of the group is off killing mobs. But we both know that’ll never happen

[DeathsSilkyMist]

It would be great if you could actually provide evidence of a shaman doing more than 20 dps in a group by mass root rotting adds while the rest of the group is off killing mobs. But we both know that’ll never happen

Crede comes in with random off topic questions from a past thread, because he can't contribute to the discussion.

You can root rot while your group kills other things. It works the same way as root rotting solo. I am sure you have been in a group where adds were rooted off to the side. Applying a DoT to them isn't a leap.

I am suprised you need evidence for how root rotting works, but this is what it would look like in both a group and solo:

https://youtu.be/1gdAIheodtY?feature=shared

I am doing well above 20 DPS here, you can check it if you want.

Hopefully Crede and Troxx do not derail the thread by pretending root rotting works differently in a group. It's a silly idea.

[Troxx]

R

O

F

L

[Snaggles]

so you refuse to parse on raid targets or provide data logs? im not sure why you are against it and thus we will always butt heads good luck in kittens

Hey I’m in Kittens. I was 5th on King Tormax last quake at just over 24k
It was a bad parse at only 70dps.
Or I’m making it up.
Or worse it’s what Gameparse told me and I’m just a sheep.

I don’t care. It’s a game. I’ll try to be civil people who want to be civil. Or as much as it can be on p99: :)

[DeathsSilkyMist]

Hey I’m in Kittens. I was 5th on King Tormax last quake at just over 24k
It was a bad parse at only 70dps.
Or I’m making it up.
Or worse it’s what Gameparse told me and I’m just a sheep.

I don’t care. It’s a game. I’ll try to be civil people who want to be civil. Or as much as it can be on p99: :)

If you are respectful to me, I respond in kind. If I am attacked, I defend myself. Pretty simple.

I don't know why people are so offended when asked for logs. It's a civil request.

I am not sure why I should be forced to believe Gamparse is accurate after yourself and Troxx said it has issues. That's not very civil.

You can easily provide both a Gamparse and the Logs as well. So much drama because of logs, and I cannot fathom why.

Nobody is claiming you are making things up when you are asked for logs. Logs provide context for the fight, and ensure there wasn't an error with your parsing program.

[Snaggles]

I am just showing people that 2h doesn't always beat 1h. I think he just didn't read.

I hate to break it to you but nobody’s arguing this. Throwing around absolutes like Always is a quick way to not be taken seriously.

DW sometimes wins. Even much worse ratios. 2H tends to win more often.
It’s about averages. I can find a lot of examples where a basic rogue with ragebringer has outdamaged another rogue with a Tunare dagger. Four delay is a handicap but it’s not a guarantee in a world of fast electronic dice rolls.

I’ll presume you misunderstood our opinion of 2h and that was not an intentional Strawman.

[bcbrown]

I am not sure why I should be forced to believe Gamparse is accurate after yourself and Troxx said it has issues. That's not very civil.

I don't want to force you to believe anything, but are you willing to listen to an explanation of why Gamparse is generally completely accurate but in one scenario produces accurate damage numbers but inaccurately low dps numbers?

[DeathsSilkyMist]

I hate to break it to you but nobody’s arguing this. Throwing around absolutes like Always is a quick way to not be taken seriously.

DW sometimes wins. Even much worse ratios. 2H tends to win more often.
It’s about averages. I can find a lot of examples where a basic rogue with ragebringer has outdamaged another rogue with a Tunare dagger. Four delay is a handicap but it’s not a guarantee in a world of fast electronic dice rolls.

I’ll presume you misunderstood our opinion of 2h and that was not an intentional Strawman.

I don't know why you assumed I was strawmanning anyone. When people say "doesn't always", that isn't an absolute. I am not sure why you think I am talking about absolutes when I literally said the equivalent of "it isn't absolute".

if you aren't gonna raid, then 2h all the way - forget about dual wield

All OP needs to know is just use a 2 hander.

There are people who voice strong opinions for 2h, even if they didn't mean it that way. People don't always have the nuanced understanding of your opinion when terse statements like this are made.

I am showing people the nuance of how it works, so they don't take generic advice without thinking. This is especially true when a lot of posters in this thread are assuming "BiS 2h at level 60" without actually specifying that. Not everybody will know that unless you are explicit. Not everybody gets their best 2h before their best 1h's either.

You can figure out when 2h beats 1h or vice versa if you have the damage formula. The damage formula is a good thing to have, since most people are not going to get every weapon in the game and parse each of them on every mob in the game. That isn't necessary.

For people interested in my current understanding of the damage formula:

https://www.project1999.com/forums/showpost.php?p=3708955&postcount=440

[DeathsSilkyMist]

I don't want to force you to believe anything, but are you willing to listen to an explanation of why Gamparse is generally completely accurate but in one scenario produces accurate damage numbers but inaccurately low dps numbers?

I understand the argument for Gamparse being accurate in the simplest of scenarios, like a solo parse.

The troubling thing is Troxx decided to post a composite parse from Gamparse that he supposedly knew was completely wrong and unuseable.

That by itself is quite concerning. It makes me wonder how many Gamparse users are doing the same thing, and how many don't know that composite parses are innacurate. It will skew their understanding of what they are parsing if they do not strictly avoid the features of Gamparse known to be inaccurate.

Everybody is also assuming Gamparse is bug free of course. I doubt anyone could confidently say it is bug free, unless they want to claim a deep understanding of the source code.

Logs don't have these issues. As long as you post the log data, everybody can check it too. You'll get more context from logs compared to a parse, and you aren't dependant on the assumption Gamparse worked. I still don't know why people are so resistant to posting logs.

[Troxx]

That by itself is quite concerning. It makes me wonder how many Gamparse users are doing the same thing, and how many don't know that….

Oh Jesus … are we transitioning to full blown conspiracy theorist?

[DeathsSilkyMist]

Oh Jesus … are we transitioning to full blown conspiracy theorist?

You posted a parse you claimed you knew was incorrect due to a flaw with Gamparse. That isn't a conspiracy theory. That is a fact, and a point of data.

If you are trying to claim I said there's a shadowy cabal of Gamparse users who have a coordinated effort to post fake data, that is obviously nonsense. I never said that. This would just be another example of Troxx being a troll, or being bad at reading.

I was simply pointing out that if Troxx is posting and studying incorrect Gamparse data for whatever reason, other posters may be doing that too. It doesn't mean they are doing it on purpose, they simply may not know this flaw with Gamparse.

Why did you post a parse you supposedly knew to be inaccurate and unuseable due to a known Gamparse flaw?

[bcbrown]

You understand what the one specific limitation with gamparse is, right?

It accurately counts total damage for everyone. If you select a single fight it accurately calculates DPS. If you have multiple fights it includes all the downtime between those fights in the time elapsed, so the denominator is wrong.

That's it. That's the only limitation.

[DeathsSilkyMist]

You understand what the one specific limitation with gamparse is, right?

It accurately counts total damage for everyone. If you select a single fight it accurately calculates DPS. If you have multiple fights it includes all the downtime between those fights in the time elapsed, so the denominator is wrong.

That's it. That's the only limitation.

And yet Troxx posted the flawed parse first, and not the supposedly accurate parses.

That is clearly a problem, as Troxx should know to never use the inaccurate parse.

I am not sure why you think this isn't an issue. If someone doesn't know about this flaw with Gamparse, they would assume Troxx's first parse was accurate when it wasn't.

Why do you think it was a good idea for Troxx to do that?

[Troxx]

https://media.tenor.com/1D5S8Qcl668AAAAM/thumbs-up-conspiracy.gif

[Snaggles]

People use tools to test other tools and results all the time. I would think running Gameparse and then your own formula would be a great way to confirm that your approach is valid, or that Gameparse is broken. Two things you appear desperately trying to confirm.

I suspect you won’t. Belief is sometimes more powerful than truth. Additionally without ever trying to parse on red cons I’m not sure anyone should just trust your proposals. A lot (but certainly not all) of well intentioned science has fallen apart when the rubber meets the road.

[DeathsSilkyMist]

People use tools to test other tools and results all the time. I would think running Gameparse and then your own formula would be a great way to confirm that your approach is valid, or that Gameparse is broken. Two things you appear desperately trying to confirm.

I suspect you won’t. Belief is sometimes more powerful than truth. Additionally without ever trying to parse on red cons I’m not sure anyone should just trust your proposals. A lot (but certainly not all) of well intentioned science has fallen apart when the rubber meets the road.

Belief is more powerful than truth at times. Troxx factually posted inaccurate Gamparse data. Yet you cling to the idea Gamparse is always accurate, and nobody has ever posted inaccurate Gamparse data.

My parses have been confirmed by other posters. I post my logs too, so everybody can double check my work! You can't double check Gamparse unless people post logs, and they usually don't. Parsing is quite simple, everybody can do it.

At the end of the day readers have two choices:

1. Read my current theory on how the damage formula works using real P99 data, EQEMU code, logic, and math. I have included logs so you can double check my work. It supports all of the oppositions current theories on how damage should work, including on raid targets, so I am not sure what they are arguing:

https://www.project1999.com/forums/showpost.php?p=3708955&postcount=440

2. Listen to posters who post inaccurate Gamparse data, or posters who deny Gamparse can be inaccurate, and have no data-backed damage formula of their own. The opposition has no equivalent post to the one I posted above. They can't even post logs so other people can confirm their parses are accurate.

[DeathsSilkyMist]

I won't be posting over the holidays. I'll leave you with my latest theory on the damage formula, and a few predictions!

Damage formula:

https://www.project1999.com/forums/showpost.php?p=3708955&postcount=440

Predictions:

1. Posters will try to argue that the damage formula posted above is incorrect. I am not sure why at this point. It supports their ideas about how 1h and 2h weapons will parse on raid targets like vindi. They are basically arguing against their own ideas at this point. It is strange. If someome thinks the damage formula can be refined, I am all ears!

2. Posters like Troxx will post more nonsense.

3. Posters will not supply their own parses AND logs to support their own theories. They will not tell us what they think the damage formula is. They could bring some of their own vindi logs + parses, and gets some logs + parses from Corudoth. They just need to tell us what weapons were used, and use the same weapons on Corudoth. They could use my damage formula with the Vindi and Corudoth datasets to figure out if my damage formula works or not.

Happy Thanksgiving!

[Troxx]

Troxx factually posted inaccurate Gamparse data. Yet you cling to the idea Gamparse is always accurate, and nobody has ever posted inaccurate Gamparse data.

Your words might carry more weight had I not been exceptionally honest (from the very first post) about the one area GamParse gets less than accurate.

https://images4.imagebam.com/94/02/9b/MECCRK4_o.png

Bear in mind that things get weird when you combine fights. Actual dps levels for everyone involved (scaled or otherwise) are below actual real time values parsed.

I have highlighted myself and my 60 water pet unfocused.

Xeff: high level sk well geared; engaged first always
Grandmaster: 60 monk with tunare's fist of tunare and priceless velium wraps 15/20
Konober and Kekab: epic mage pet from another epic. I can only guess he didn't mask it or keep it hasted like it should have been.

Comparatively Ailowen + unfocused 60 water pet is the highlighted above.

See the monk's time engaged and you can see why he was below the SK and lower than me to such a degree; he spent a lot of time not engaged. What you can see is that mage dps is very good. This parse undervalues on the combine by a good 30% as my parse system is not perfect.

https://www.project1999.com/forums/showpost.php?p=3495244&postcount=181

I mean it’s right there for all to read. I followed on with individual breakout fights. Lord Jesus this was from 27 months ago …. quite a long time before most of the people on this forum were aware just how insane you are lol.


You keep demanding people post their private logs. Want our social security cards, text messages, call logs, and mother’s maiden name too? My private logs are my private information. What is said in my group/guild or in tells is one of your business. You think there is legitimacy in raw log files? You can go in there with a basic text program and alter it with simple keystrokes. "Cooking the book" if you want to lie is pretty easy with p99 log files.

Lol @ this muppet getting pissy people don’t deliver him exactly the way he wants it. Remember when he wanted us to FRAPS and upload videos to YouTube? Piss off.

[Jimjam]

DSM can you post the code of the script or tool you are using to cleanse / count log file data? I'm very interested in taking a look and trying it out.

[Troxx]

DSM can you post the code of the script or tool you are using to cleanse / count log file data? I'm very interested in taking a look and trying it out.

I'm going to go out on a limb and say that it is probably (hopefully) accurate but a lot less snazzy (and no more or less accurate) than GamParse. I would be shocked if it has any bells and whistles or even the ability to attempt to highlighted multiple fights and compile them with accuracy.

GamParse is like the BMI charts. Great tool as long as you understand and acknowledge its shortcomings and break points.

As an example, BMI breakpoints medically are when:

-you are using on kids >2 and <18 who are exceptionally tall
-Women of above average height (the taller vs average the worse)
-Men of exceedingly way way above average height
-Men (and to a much lesser degree women) who spend time lifting weights

For most people it is pretty dang accurate.

GamParse breaking points:

- Can't parse other's Dmg shields, dots or DDs
- Gets weird when you try to compile fights

[Jimjam]

There is also the general breaking points for logging, which is the range to actually receive hits from other players is shockingly small. The log also seems pretty decent at receiving information when there is lost connection too, but dareisay it may not be perfect in that instance either.

Obviously these issues should be farely consistent whichever method you are using to analyse the log, so could be considered accounted for?

[DeathsSilkyMist]

Your words might carry more weight had I not been exceptionally honest (from the very first post) about the one area GamParse gets less than accurate.



https://www.project1999.com/forums/showpost.php?p=3495244&postcount=181

I mean it’s right there for all to read. I followed on with individual breakout fights. Lord Jesus this was from 27 months ago …. quite a long time before most of the people on this forum were aware just how insane you are lol.


You keep demanding people post their private logs. Want our social security cards, text messages, call logs, and mother’s maiden name too? My private logs are my private information. What is said in my group/guild or in tells is one of your business. You think there is legitimacy in raw log files? You can go in there with a basic text program and alter it with simple keystrokes. "Cooking the book" if you want to lie is pretty easy with p99 log files.

Lol @ this muppet getting pissy people don’t deliver him exactly the way he wants it. Remember when he wanted us to FRAPS and upload videos to YouTube? Piss off.

I'll just say one more quick thing before the holiday. I never claimed Troxx didn't admit the data was inaccurate. I said he admitted it was inaccurate multiple times in this thread in fact.

This still shows the simple truth that people are posting inaccurate Gamparse data for their arguments. It is possible some people don't know Gamparse is inaccurate when doing composite fights, and use that data to come to their conclusions.

Troxx doesn't realize you can change the parse numbers from Gamparse too. It's easy to photoshop that spreadsheet you provided with different numbers, or just modify the numbers in the spreadsheet before taking a screenshot. Or just modify the parse text data you copy/paste into the forum.

That is why I post videos + logs. Anybody can check the video and confirm the logs match. Doctoring a video is significantly more difficult than an image. It is honestly a compliment if you think I have the skills to pull that off.

In terms of "private data", it is trivial to remove that from the logs if you are afraid of other people seeing what you say in P99. I doubt you are PMing people your social security info, credit card numbers, etc lol. When doing a parse just move your old logs out of the folder into a backup folder. Then you'll only get the log data from that parsing session. Use a program like Notepad++ to pull out all the parse data with the find all function and put it in a new file.

[Jimjam]

imo not worth the cognitive or emotional load to consider people are tampering their parse outputs. I'm sure some do, in which case good for them for the snreaky hollow flex.

[DeathsSilkyMist]

DSM can you post the code of the script or tool you are using to cleanse / count log file data? I'm very interested in taking a look and trying it out.

Ah I did find the Javascript, I posted it before:



Here is a very simple example that you can code yourself and run in browser using https://playcode.io/javascript (Check the console result) when doing damage aggregation:


var array =
[
"[Sun Aug 21 07:32:14 2022] Wickedsteal pierces froglok bok wizard for 22",
"[Sun Aug 21 07:32:14 2022] Wickedsteal pierces froglok bok wizard for 41",
"[Sun Aug 21 07:32:16 2022] Wickedsteal pierces froglok bok wizard for 23",
"[Sun Aug 21 07:32:17 2022] Wickedsteal pierces froglok bok wizard for 62",
"[Sun Aug 21 07:32:19 2022] Wickedsteal pierces froglok bok wizard for 26",
"[Sun Aug 21 07:32:19 2022] Wickedsteal pierces froglok bok wizard for 16",
"[Sun Aug 21 07:32:19 2022] Wickedsteal pierces froglok bok wizard for 73",
"[Sun Aug 21 07:32:22 2022] Wickedsteal pierces froglok bok wizard for 31",
"[Sun Aug 21 07:32:22 2022] Wickedsteal pierces froglok bok wizard for 88",
"[Sun Aug 21 07:32:23 2022] Wickedsteal pierces froglok bok wizard for 78",
"[Sun Aug 21 07:32:24 2022] Wickedsteal pierces froglok bok wizard for 84",
"[Sun Aug 21 07:32:24 2022] Wickedsteal pierces froglok bok wizard for 26",
"[Sun Aug 21 07:32:26 2022] Wickedsteal pierces froglok bok wizard for 27",
"[Sun Aug 21 07:32:27 2022] Wickedsteal pierces froglok bok wizard for 25",
"[Sun Aug 21 07:32:28 2022] Wickedsteal pierces froglok bok wizard for 68",
"[Sun Aug 21 07:32:29 2022] Wickedsteal pierces froglok bok wizard for 54",
"[Sun Aug 21 07:32:31 2022] Wickedsteal pierces froglok bok wizard for 17",
"[Sun Aug 21 07:32:32 2022] Wickedsteal pierces froglok bok wizard for 70",
"[Sun Aug 21 07:32:34 2022] Wickedsteal pierces froglok bok wizard for 54",
"[Sun Aug 21 07:32:34 2022] Wickedsteal pierces froglok bok wizard for 78",
"[Sun Aug 21 07:32:36 2022] Wickedsteal pierces froglok bok wizard for 40",
"[Sun Aug 21 07:32:36 2022] Wickedsteal pierces froglok bok wizard for 41",
"[Sun Aug 21 07:32:37 2022] Wickedsteal pierces froglok bok wizard for 96",
"[Sun Aug 21 07:32:37 2022] Wickedsteal pierces froglok bok wizard for 70",
"[Sun Aug 21 07:32:38 2022] Wickedsteal pierces froglok bok wizard for 22",
"[Sun Aug 21 07:32:40 2022] Wickedsteal pierces froglok bok wizard for 26",
"[Sun Aug 21 07:32:41 2022] Wickedsteal pierces froglok bok wizard for 41",
"[Sun Aug 21 07:32:41 2022] Wickedsteal pierces froglok bok wizard for 59",
"[Sun Aug 21 07:32:42 2022] Wickedsteal pierces froglok bok wizard for 62",
"[Sun Aug 21 07:32:42 2022] Wickedsteal pierces froglok bok wizard for 41",
"[Sun Aug 21 07:32:43 2022] Wickedsteal pierces froglok bok wizard for 14",
"[Sun Aug 21 07:32:43 2022] Wickedsteal pierces froglok bok wizard for 61",
"[Sun Aug 21 07:32:43 2022] Wickedsteal pierces froglok bok wizard for 25",
"[Sun Aug 21 07:32:44 2022] Wickedsteal pierces froglok bok wizard for 14",
"[Sun Aug 21 07:32:45 2022] Wickedsteal pierces froglok bok wizard for 41",
"[Sun Aug 21 07:32:45 2022] Wickedsteal pierces froglok bok wizard for 64",
"[Sun Aug 21 07:32:45 2022] Wickedsteal pierces froglok bok wizard for 20",
"[Sun Aug 21 07:32:46 2022] Wickedsteal pierces froglok bok wizard for 21",
"[Sun Aug 21 07:32:46 2022] Wickedsteal pierces froglok bok wizard for 41",
"[Sun Aug 21 07:32:46 2022] Wickedsteal pierces froglok bok wizard for 8",
"[Sun Aug 21 07:32:47 2022] Wickedsteal pierces froglok bok wizard for 37",
"[Sun Aug 21 07:32:48 2022] Wickedsteal pierces froglok bok wizard for 9",
"[Sun Aug 21 07:32:48 2022] Wickedsteal pierces froglok bok wizard for 5",
"[Sun Aug 21 07:32:48 2022] Wickedsteal pierces froglok bok wizard for 20",
"[Sun Aug 21 07:32:49 2022] Wickedsteal pierces froglok bok wizard for 28",
"[Sun Aug 21 07:32:50 2022] Wickedsteal pierces froglok bok wizard for 74",
"[Sun Aug 21 07:32:50 2022] Wickedsteal pierces froglok bok wizard for 11",
"[Sun Aug 21 07:32:51 2022] Wickedsteal pierces froglok bok wizard for 55",
"[Sun Aug 21 07:32:51 2022] Wickedsteal pierces froglok bok wizard for 65",
"[Sun Aug 21 07:32:55 2022] Wickedsteal pierces froglok bok wizard for 77",
"[Sun Aug 21 07:32:55 2022] Wickedsteal pierces froglok bok wizard for 49",
"[Sun Aug 21 07:32:56 2022] Wickedsteal pierces froglok bok wizard for 64",
"[Sun Aug 21 07:32:56 2022] Wickedsteal pierces froglok bok wizard for 5",
"[Sun Aug 21 07:32:59 2022] Wickedsteal pierces froglok bok wizard for 20",
"[Sun Aug 21 07:32:59 2022] Wickedsteal pierces froglok bok wizard for 29",
"[Sun Aug 21 07:33:00 2022] Wickedsteal pierces froglok bok wizard for 41",
"[Sun Aug 21 07:33:00 2022] Wickedsteal pierces froglok bok wizard for 23",
"[Sun Aug 21 07:32:12 2022] Wickedsteal crushes froglok bok wizard for 55",
"[Sun Aug 21 07:32:12 2022] Wickedsteal crushes froglok bok wizard for 39",
"[Sun Aug 21 07:32:13 2022] Wickedsteal crushes froglok bok wizard for 18",
"[Sun Aug 21 07:32:16 2022] Wickedsteal crushes froglok bok wizard for 66",
"[Sun Aug 21 07:32:16 2022] Wickedsteal crushes froglok bok wizard for 68",
"[Sun Aug 21 07:32:17 2022] Wickedsteal crushes froglok bok wizard for 54",
"[Sun Aug 21 07:32:17 2022] Wickedsteal crushes froglok bok wizard for 28",
"[Sun Aug 21 07:32:20 2022] Wickedsteal crushes froglok bok wizard for 42",
"[Sun Aug 21 07:32:20 2022] Wickedsteal crushes froglok bok wizard for 6",
"[Sun Aug 21 07:32:21 2022] Wickedsteal crushes froglok bok wizard for 32",
"[Sun Aug 21 07:32:23 2022] Wickedsteal crushes froglok bok wizard for 30",
"[Sun Aug 21 07:32:23 2022] Wickedsteal crushes froglok bok wizard for 67",
"[Sun Aug 21 07:32:27 2022] Wickedsteal crushes froglok bok wizard for 9",
"[Sun Aug 21 07:32:29 2022] Wickedsteal crushes froglok bok wizard for 83",
"[Sun Aug 21 07:32:29 2022] Wickedsteal crushes froglok bok wizard for 62",
"[Sun Aug 21 07:32:30 2022] Wickedsteal crushes froglok bok wizard for 48",
"[Sun Aug 21 07:32:33 2022] Wickedsteal crushes froglok bok wizard for 12",
"[Sun Aug 21 07:32:38 2022] Wickedsteal crushes froglok bok wizard for 36",
"[Sun Aug 21 07:32:25 2022] Wickedsteal backstabs froglok bok wizard for 194",
"[Sun Aug 21 07:32:31 2022] Wickedsteal backstabs froglok bok wizard for 180",
"[Sun Aug 21 07:32:43 2022] Wickedsteal backstabs froglok bok wizard for 369",
"[Sun Aug 21 07:32:43 2022] Wickedsteal backstabs froglok bok wizard for 194",
"[Sun Aug 21 07:32:49 2022] Wickedsteal backstabs froglok bok wizard for 299",
"[Sun Aug 21 07:32:49 2022] Wickedsteal backstabs froglok bok wizard for 194",
"[Sun Aug 21 07:32:55 2022] Wickedsteal backstabs froglok bok wizard for 478",
];

var result = 0;
for(var i = 0; i < array.length; i++)
{
var last3 = array[i].slice(-3).replace(/\D/g,'');
result += parseInt(last3, 10);
}

console.log(result);


I use Notepad++ to search through the document to find the results that you plug into the array. Doesn't take long at all.

Notepad++ is what I use to go through log data. You can open multiple files and do a search across all open files. You can look for something like "crushes Corudoth for" to get all of your crush hits against Corudoth. It will give you the full text line, so it's easy to copy all those results out of the result window.

Happy Thanksgiving!

[Jimjam]

So you search for text contained in a line, it selects all lines containing that text and you can copy them all to a new document in one foul swoop?


Edit Happy Thanksgiving DSM and all my other elfquest pals <3

[DeathsSilkyMist]

So you search for text contained in a line, it selects all lines containing that text and you can copy them all to a new document in one foul swoop?


Edit Happy Thanksgiving DSM and all my other elfquest pals <3

That's right. If you do a search all across all open documents for "crushes corudoth for", it will put all of the full text lines (the entire sentence including the damage) it finds into a new results window. You can copy all of those lines from the results window into a new document. You can even click on the individual line in the results window, and it will take you to that line in the text document. Notepad++ is great.

The javascript for aggregating damage is here:

https://www.project1999.com/forums/showpost.php?p=3709570&postcount=528

Ok, off to the holdiays now. Happy Thanksgiving!

[Troxx]

I won't be posting over the holidays.

Liar

[Eisai]

I think holidays is until like January?