By the way, if it helps to reduce the effort on your end, I'm happy to have a call and discuss the changes :)

I'm really on the fence with this feature. The code looks good, so I'm not concerned with that, but I'd want feedback on how mobs currently manage their breaks. For reference, I have at least 10 teams at work that manage breaks on their own while still using mobtime, so I'm curious what the value add is.

Also, sorry it took me a while to get back to you on this!

I'm currently running two mobs with this version of the timer (hosted at https://mobtime.herokuapp.com/ ). I know that others asked me for that version as well, but I didn't yet get feedback from them whether they actually use it.
The main reasons for us to use the integrated break timers are:

1. Having only one tool to set up and look at as a mob instead of having to sync on multiple tools.
2. Being reminded of breaks less intrusively as the timer just stops you from starting the next round, but doesn't interrupt your current one (which often lead us to "first finish what we are up to" and then forget the break all together)

Our mob would really appreciate this feature as well. Our concerns are the same as @dbartholomae 's; managing two timers is clunky (especially when the break timer is not shared), and being forced to take breaks is always nice.

So a lot has changed in the code-base since this PR. master is the base again (dev will probably be deleted in the near future), and on top of that, I am thinking of building a bot for break timers rather than a direct integration. With that in mind, I'm going to close this, but maybe there will be an opportunity in the future to revisit this.