diff options
| author | Daniel Schadt <kingdread@gmx.de> | 2020-06-28 17:22:43 +0200 |
|---|---|---|
| committer | Daniel Schadt <kingdread@gmx.de> | 2020-06-28 17:22:43 +0200 |
| commit | 0978345648cf9cdad6222f583dd21497b409d07e (patch) | |
| tree | 9470f87a879e36c68104ef067c6657eb94cd98e5 /tests/logs/analyzers | |
| parent | acdc4d977e573d54c73530f77ba210efd2184cf0 (diff) | |
| download | evtclib-0978345648cf9cdad6222f583dd21497b409d07e.tar.gz evtclib-0978345648cf9cdad6222f583dd21497b409d07e.tar.bz2 evtclib-0978345648cf9cdad6222f583dd21497b409d07e.zip | |
start implementing analyzers
It turns out that the different encounters do require quite some
encounter-specific logic, not only to determine whether the CM was
activated, but also to determine whether the fight was successful, the
duration of the fight, later the phases, ...
Wrapping all of this in pre-defined "triggers" (like CmTrigger) feels
like it will be a bit unfitting, so with this patch we have introduced
the evtclib::Analyzer, which can be used to analyze the fights.
Currently, the whole CM detection logic has been moved to this new
interface, and soon we also want the success-detection logic in there.
The tests pass and the interface of Log::is_cm is unchanged.
Diffstat (limited to 'tests/logs/analyzers')
0 files changed, 0 insertions, 0 deletions