Age | Commit message (Collapse) | Author | |
---|---|---|---|
2021-11-22 | add Twisted Castle | Daniel Schadt | |
There's not many useful things we can do with this log, other than providing a way for downstream applications to identify those logs. | |||
2020-09-29 | return Outcome::Success if a raid was rewarded | Daniel Schadt | |
If the reward has been given out, we can be 99.9% sure that the fight succeeded, in which case we don't need to do any other convuluted checking. This has the benefit of catching some false-negatives (edge cases in success detection), at the cost of making the detection a bit ... weirder, in the sense that a log's success might now depend on whether it was the first kill in the week or not. However, given that our sucess detection works pretty well overall, I'd say it's worth to catch a few more false-negatives and try to classify as many logs correctly as possible. At least, this does not introduce any false-positives. | |||
2020-07-24 | more documentation | Daniel Schadt | |
2020-07-23 | implement proper outcome for w1-w4 | Daniel Schadt | |
It turns out that `was_rewarded` is a pretty bad heuristic if you ever kill a boss a second time per week (basically, was_rewarded=false does not imply that the boss was unsuccessful). Therefore, we need a proper detection of when a fight failed and when a fight succeeded. This is the first batch that implements this as part of the Analyzer trait for bosses of wings 1 to 4. |