evtclib/src/analyzers, branch v0.4.2 arcdps EVTC reading/parsing library for Rust remove leftover debug output 2020-08-28T13:52:30+00:00 Daniel Schadt kingdread@gmx.de 2020-08-28T13:52:30+00:00 7561a928912b62e0fea384840ebaec1d3c4d291c Since downstream applications will also print this, we should remove it. 
Since downstream applications will also print this, we should remove it.
more documentation 2020-07-24T12:09:51+00:00 Daniel Schadt kingdread@gmx.de 2020-07-24T12:09:51+00:00 f6717fc45188870341e9b6185ef5f3102f5a96ae 






more documentation & adjustments
2020-07-23T15:57:59+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-23T15:57:59+00:00

75f5ce065efb6a186570b365c88e564871915d76












remove default implementation of Analyzer::outcome
2020-07-23T15:41:52+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-23T15:41:52+00:00

6a4e302e49bea67cfd2ce240bc0de284967540c1

This was only there to make it easier to gradually implement the outcome
method for the individual bosses. Now that each boss has a proper
outcome, we no longer need the default method - in fact, I'd rather make
sure the compiler tells us if we forget to implement this method in a
new analyzer.





This was only there to make it easier to gradually implement the outcome
method for the individual bosses. Now that each boss has a proper
outcome, we no longer need the default method - in fact, I'd rather make
sure the compiler tells us if we forget to implement this method in a
new analyzer.







implement strike Analyzers
2020-07-23T15:40:42+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-23T15:40:42+00:00

d2a3a49dc4759ede6cc9f553955eb289477a9d74












implement Analyzer::outcome for fractals
2020-07-23T15:33:15+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-23T15:33:15+00:00

d64ead757122e713d2cbb133d5fe683537cfcf6c












implement Analyzer::outcome for wing 7
2020-07-23T15:23:03+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-23T15:23:03+00:00

d290abac857fd88008afcde1d76fc70fe33ca605












implement Analyzer::outcome for wing 6
2020-07-23T15:18:56+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-23T15:18:56+00:00

dcf1b948b953fb17db16eafcdd30f0a25301171f












implement Analyzer::outcome for wing 5
2020-07-23T01:00:53+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-23T01:00:53+00:00

4c02181067e789e41eb95c6f6e954e4de6277dc1












implement proper outcome for w1-w4
2020-07-23T00:47:52+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-23T00:47:52+00:00

962e2b9f8e17a50c7d7d37a424591b0df62f265c

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.





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.