tidge Posted February 14 Posted February 14 I meant in "separate" in the subtle, memory-resource way, not in the "how it is coded" way.
macskull Posted February 15 Posted February 15 (edited) Did some more overnight testing that was ended by today's surprise maintenance - apparently weekly restarts also affect the beta shards. Up to 1614 misses out of 33732 attacks, for an overall hit rate of 95.22%. I think we can put this one to bed. Edited February 15 by macskull accidentally a word "If you can read this, I've failed as a developer." -- Caretaker Proc information and chance calculator spreadsheet (last updated 15APR24) Player numbers graph (updated every 15 minutes) Graph readme (now with Victory support!) @macskull/@Not Mac | Twitch | Youtube
tidge Posted February 15 Posted February 15 Any chance of testing with an AoE attack, like Fire Ball instead of a single target attack like Fire Blast?
macskull Posted February 16 Posted February 16 (edited) On 2/14/2025 at 5:08 PM, tidge said: Any chance of testing with an AoE attack, like Fire Ball instead of a single target attack like Fire Blast? 43434 hits out of 45560 attempts, for an overall hit rate of 95.33%. Unfortunately log file sizes start to get really big with that many entries (this file was over 30MB for just 6 hours of data) and my normal means of analyzing the results slow down a lot when working with files that size. Edited February 16 by macskull 1 "If you can read this, I've failed as a developer." -- Caretaker Proc information and chance calculator spreadsheet (last updated 15APR24) Player numbers graph (updated every 15 minutes) Graph readme (now with Victory support!) @macskull/@Not Mac | Twitch | Youtube
macskull Posted Sunday at 05:52 AM Posted Sunday at 05:52 AM (edited) Hey, turns out a little bit of playing around with Python makes this whole thing a lot easier and I can just run it on an entire folder of logs at once! Still relies on manually inputting the strings to search for, but hey it's virtually instant compared with trying to Ctrl-F a 5000-page Word document. Edited Sunday at 05:56 AM by macskull 1 "If you can read this, I've failed as a developer." -- Caretaker Proc information and chance calculator spreadsheet (last updated 15APR24) Player numbers graph (updated every 15 minutes) Graph readme (now with Victory support!) @macskull/@Not Mac | Twitch | Youtube
macskull Posted Monday at 01:14 AM Posted Monday at 01:14 AM (edited) Last one, this is with everything together including another run from today. While this doesn't prove that the actual miss rate with streakbreaker factored in is 4.76% as some quick math would suggest, it does reveal that it is almost a statistical certainty that the true miss rate is less than 5%. Given that, there's not really any reason to doubt the overall hit rate to be the previously-calculated 95.24%. (Also, I should've been using Fireball from the very beginning. Considering how quickly it lets you get large amounts of hit rolls, I probably could have had close to a million attacks if I'd done it that way from the start.) Oh, and here's the distribution of hit rolls from all those attacks. Edited Monday at 01:27 AM by macskull "If you can read this, I've failed as a developer." -- Caretaker Proc information and chance calculator spreadsheet (last updated 15APR24) Player numbers graph (updated every 15 minutes) Graph readme (now with Victory support!) @macskull/@Not Mac | Twitch | Youtube
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now