Fever States #3
Description
By "fever" states I mean when the volume rises up to max and stays there consistently. When you detect the end of a "fever," i.e the coder slowed down (and maybe went over to the Explorer to make a file), add a buffer between the end of this "fever" and the start of the volume decreasing. This gives the coder some time to create a file in the Explorer, run a command, etc., without it seeming like they broke their flow. If the time buffer hits, then logic would state that the coder actually did break their flow.
Perhaps this could also be a setting, both whether the buffer's enabled and how long it is.
(Taken from the advice of: @alkalinethunder)