return Outcome::Success if a raid was rewarded

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.

1 files changed, 4 insertions, 0 deletions

diff --git a/src/analyzers/raids/w4.rs b/src/analyzers/raids/w4.rs
index adeb2ea..9294e3c 100644
--- a/src/analyzers/raids/w4.rs
+++ b/src/analyzers/raids/w4.rs
@@ -35,6 +35,7 @@ impl<'log> Analyzer for Cairn<'log> {
     }
 
     fn outcome(&self) -> Option<Outcome> {
+        check_reward!(self.log);
         Outcome::from_bool(helpers::boss_is_dead(self.log))
     }
 }
@@ -71,6 +72,7 @@ impl<'log> Analyzer for MursaatOverseer<'log> {
     }
 
     fn outcome(&self) -> Option<Outcome> {
+        check_reward!(self.log);
         Outcome::from_bool(helpers::boss_is_dead(self.log))
     }
 }
@@ -107,6 +109,7 @@ impl<'log> Analyzer for Samarog<'log> {
     }
 
     fn outcome(&self) -> Option<Outcome> {
+        check_reward!(self.log);
         Outcome::from_bool(helpers::boss_is_dead(self.log))
     }
 }
@@ -143,6 +146,7 @@ impl<'log> Analyzer for Deimos<'log> {
     }
 
     fn outcome(&self) -> Option<Outcome> {
+        check_reward!(self.log);
         // The idea for Deimos is that we first need to figure out when the 10% split happens (if
         // it even happens), then we can find the time when 10%-Deimos becomes untargetable and
         // then we can compare this time to the player exit time.