evtclib, branch v0.4.0 arcdps EVTC reading/parsing library for Rust bump version to 0.4.0 2020-07-24T13:13:39+00:00 Daniel Schadt kingdread@gmx.de 2020-07-24T13:13:39+00:00 1eb04b8496dcdf626f8d4651f66955a0ea7c1102 






include analyzer output in loginfo example
2020-07-24T12:34:57+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-24T12:34:57+00:00

df83dba4e5481fc1f5d6276867d09ef729fcfc25












Merge branch 'analyzers'
2020-07-24T12:23:53+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-24T12:23:53+00:00

71528905ed228750559a41144a2e0a95db3e6805

This brings in proper fight outcome detection, which is nice and needed
for downstream applications (raidgrep/ezau).

Furthermore, this cleans up the CM detection a bit by moving away from
the "descriptive" trigger way to just having dynamically dispatched
methods for every log.





This brings in proper fight outcome detection, which is nice and needed
for downstream applications (raidgrep/ezau).

Furthermore, this cleans up the CM detection a bit by moving away from
the "descriptive" trigger way to just having dynamically dispatched
methods for every log.







mention loginfo example in README
2020-07-24T12:23:43+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-24T12:23:43+00:00

01354b0934409c355831bb4202f998fe5dbdc335












add some testing for analyzers
2020-07-24T12:11:51+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-24T12:11:51+00:00

9d27ec7034f9ad07d8a1d74ab30fdc470de4e02d












more documentation
2020-07-24T12:09:51+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-24T12:09:51+00:00

f6717fc45188870341e9b6185ef5f3102f5a96ae












re-export Outcome as well
2020-07-24T11:49:49+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-24T11:49:49+00:00

06590a174a4b3707b9048f3669ad17702902b601












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

Daniel Schadt
kingdread@gmx.de

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

75f5ce065efb6a186570b365c88e564871915d76












update changelog
2020-07-23T15:45:16+00:00

Daniel Schadt
kingdread@gmx.de

2020-07-23T15:45:16+00:00

30b3c2cfbb88d0a8e8e6b209c11fd0efacb66aff












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.