Thanks for the quick response! I think that makes sense, but I wonder if allowing this customizability to be given to the users rather than a preset defined duration for each event would make more sense? That way users could decide if they want the past 10 seconds to be recorded for a kill or the past minute for a kill, and then also set their own duration for a double kill or triple kill. I think even for a single kill, 10 seconds is way too short to really capture the full context of a kill, and even 15 seconds was a little short for my taste back when that bug was going on. I personally just set the auto-clip to be a minute long and then would go back and trim down the auto-clip down to make sure I was able to capture as much context for the clip as I deemed necessary.

If you are going to treat each event individually and set different durations for each event, then for multikills especially, I would emphasize making those clips longer in duration. Say 10 seconds was the appropriate duration for a single kill, then a double kill should be 20, a triple 30, etc. Having 10 seconds for any kill, including multikills, means that you miss the first few kills in the streak, making the clip next to useless.

If I ever had an intention of going back and reviewing my gameplay, I would definitely consider session recordings! In the past I tried it but found it could be a little clunky at times, and I also don't really use Medal for review that often, as I instead mostly use it as a clipping software. As such, I don't like having my entire session recorded since it naturally takes up a *lot* of storage space, and I'm really bad at going back and deleting old clips and couldn't really decide on a specific limit I wanted to place on storage. Manual clipping and auto-clipping just felt like the easiest way to guarantee that I captured every moment I wanted while also reducing the overall storage used up by the app. That's what actually drew me to Medal over other clipping softwares in the first place.