Hi, I've just discovered this app (via cube cobra) and it's great! One thing it's missing that I was hoping for is the ability to do asynchronous drafts. I would like to be able to draft with my friends over the course of a week so we've already got our card/deck lists ready when we show up for game night. This seems quasi-possible as pick timer can be turned off, which is great. However, if a player disconnects/times out then the whole draft is stopped until they rejoin or the owner replaces them with a bot. Consequently, all players are required to be (some estimation of) present for the duration of the draft. On PC (windows), it seems like leaving the tab open will suffice. But putting the tab to sleep, closing it, or the whole browser will cause disconnect. On mobile (android), jumping to another app or browser tab for more than a min or two causes disconnect.
Supporting async I think would be pretty straight-forward. On player disconnect, simply allow the draft to proceed as far as possible rather than freezing it. Instead of a disconnect pop-up, you could add a player connection symbol by their name or something. You could also still give owners the ability to replace players with a bot by clicking on their name or the disconnect symbol or whatever. Packs may accumulate on the disconnected player but that's fine, they can resolve them on reconnect (or bot replacement). As a bonus, a nice to have would be a notification when a pack has been passed to you. Ideally only when draftmancer isn't the active tab and/or app. Or perhaps only when your pack queue is empty and you're waiting on the next pack. But if that's complicated manual checking wouldn't be the end of the world.
I think these changes would also help real-time drafts run more smoothly, so there's really no downside. Would definitely help for mobile users. I'm not sure if there would be state propagation/persistence issues, but even if there are I think that would be acceptable. And if async becomes more common then I'm sure it's solvable. Seems to work just fine after brief disconnects when testing. I've noticed there's no account login for this app? That could help but prob not necessary.
Hi, I've just discovered this app (via cube cobra) and it's great! One thing it's missing that I was hoping for is the ability to do asynchronous drafts. I would like to be able to draft with my friends over the course of a week so we've already got our card/deck lists ready when we show up for game night. This seems quasi-possible as pick timer can be turned off, which is great. However, if a player disconnects/times out then the whole draft is stopped until they rejoin or the owner replaces them with a bot. Consequently, all players are required to be (some estimation of) present for the duration of the draft. On PC (windows), it seems like leaving the tab open will suffice. But putting the tab to sleep, closing it, or the whole browser will cause disconnect. On mobile (android), jumping to another app or browser tab for more than a min or two causes disconnect.
Supporting async I think would be pretty straight-forward. On player disconnect, simply allow the draft to proceed as far as possible rather than freezing it. Instead of a disconnect pop-up, you could add a player connection symbol by their name or something. You could also still give owners the ability to replace players with a bot by clicking on their name or the disconnect symbol or whatever. Packs may accumulate on the disconnected player but that's fine, they can resolve them on reconnect (or bot replacement). As a bonus, a nice to have would be a notification when a pack has been passed to you. Ideally only when draftmancer isn't the active tab and/or app. Or perhaps only when your pack queue is empty and you're waiting on the next pack. But if that's complicated manual checking wouldn't be the end of the world.
I think these changes would also help real-time drafts run more smoothly, so there's really no downside. Would definitely help for mobile users. I'm not sure if there would be state propagation/persistence issues, but even if there are I think that would be acceptable. And if async becomes more common then I'm sure it's solvable. Seems to work just fine after brief disconnects when testing. I've noticed there's no account login for this app? That could help but prob not necessary.