You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no notification send when your sealed pod starts and your pool is distributed. Same for Jumpstart.
The idea is basically the same for non-draft games. People queue up and don't want to check the page all the time to realize when the game actually started.
Notifications are only send for a starting draft (also the special variants like Glimpse and Rochester) and when a new pick is waiting for you.
Other suggestions:
There is no notification once the draft portion is done and everybody finished picking their cards and the official deck building is starting with the additional access to adding lands, sharing and exporting a deck...
There is no notification when a draft is stopped or paused
Ideally, only send notifications when the page is not in focus and your attention/action is needed (e.g. browser minimized, reading other tab, using other programm...)
The text was updated successfully, but these errors were encountered:
There is no notification send when your sealed pod starts and your pool is distributed. Same for Jumpstart.
The idea is basically the same for non-draft games. People queue up and don't want to check the page all the time to realize when the game actually started.
Notifications are only send for a starting draft (also the special variants like Glimpse and Rochester) and when a new pick is waiting for you.
Other suggestions:
There is no notification once the draft portion is done and everybody finished picking their cards and the official deck building is starting with the additional access to adding lands, sharing and exporting a deck...
There is no notification when a draft is stopped or paused
Ideally, only send notifications when the page is not in focus and your attention/action is needed (e.g. browser minimized, reading other tab, using other programm...)
The text was updated successfully, but these errors were encountered: