search

opengamedata / opengamedata-core

Python framework for extracting features from OpenGameData event datasets.
https://opengamedata.fielddaylab.wisc.edu/
MIT License
1 stars 3 forks source link

Journalism: QuitType #81

Closed LswaN58 closed 1 year ago

LswaN58 commented 1 year ago

Feature whose value is a string, one of "BetweenLevels", "OnFail", or "Other". For convenience, there are three subfeatures: 1) BetweenLevels: a bool that true if the quit was between levels, else false. 2) OnFail: a bool that true if the quit was on a failure, else false. 3) Other: a bool that true if the other two are false, otherwise true.

zstud04 commented 1 year ago

1f837a1e948d4f7562ee1359a97d65a42e803c99

zstud04 commented 1 year ago

QuitType logic: -"complete_level", "display_feedback", "resumed_checkpoint", "level_fail" all denote certain breakpoints in quit types -"Buffer_Limit" sets the number of events after a key breakpoint event that the event stays "on" -every BUFFER_LIMIT events, the stored_event is reset -a breakpoint event resets the counter -time between "display_feedback" event and "complete_level" is considered Quit BetweenLevel -counter is set to -1 and does not begin incrementing again until after complete_level -time between "level_fail" and "resumed_checkpoint"(when origin="LevelFail") is considered Quit OnFail -counter is set to -1 and does not begin incrementing again until after resumed_checkpoint

zstud04 commented 1 year ago

Updated to include for OnCheckpoint. also excluded system feedback "display_..." events from incrementing event counter.

5df837448207e7fd6a233bf40951f9275d04fba3