Three mails, and three separate 24-hour windows
The announcement totals the weekend as “2 Pro Combat Bags and 1 Elite Combat Bag each weekend”, which reads as one bundle and is not one. Three mails are sent on three consecutive nights and each carries its own 24-hour clock, so a player who logs in once on Sunday collects the Elite bag and has already lost both Pro bags. That is the practical difference between this event and the milestone grants that came before it: those had a single deadline and this has one per night.
- Logging in is the whole requirement. No level gate is published for this event, unlike the one-month anniversary mail, which needs Lv.5.
- Nothing carries over. An unclaimed mail expires where it sits, and no reissue or support route has ever been published for a lapsed grant in this game.
| Sent | Reward | Claim closes |
|---|---|---|
| Friday 00:00, server time | Pro Combat Bag ×1 | 24 hours later — Saturday 00:00 |
| Saturday 00:00, server time | Pro Combat Bag ×1 | 24 hours later — Sunday 00:00 |
| Sunday 00:00, server time | Elite Combat Bag ×1 | 24 hours later — Monday 00:00 |
Friday 00:00, server time
- Reward
- Pro Combat Bag ×1
- Claim closes
- 24 hours later — Saturday 00:00
Saturday 00:00, server time
- Reward
- Pro Combat Bag ×1
- Claim closes
- 24 hours later — Sunday 00:00
Sunday 00:00, server time
- Reward
- Elite Combat Bag ×1
- Claim closes
- 24 hours later — Monday 00:00
Your server’s midnight, not UTC — and Oceania gets it on a Thursday
The post lists three server time zones and then gives the schedule in local time, which is the sentence most likely to be dropped when this is repeated elsewhere. Converted to UTC the three servers do not share a day: an Oceania player whose mail arrives at 00:00 UTC+10 on Friday is being sent it at 14:00 UTC on Thursday, and a schedule written in UTC would have them looking a day late for something that had already been sitting there for ten hours.
- The Oceania server is itself new — it opened with the 28 August maintenance update, so this is the first reward event it has ever been listed in.
- Saturday and Sunday shift by the same offsets. The pattern holds for all three nights; only the weekday label moves.
| Server | Server clock | Friday mail, in UTC | That mail closes, in UTC |
|---|---|---|---|
| International | UTC+0 | Friday 00:00 | Saturday 00:00 |
| Oceania | UTC+10 | Thursday 14:00 | Friday 14:00 |
| North America | UTC-8 | Friday 08:00 | Saturday 08:00 |
International
- Server clock
- UTC+0
- Friday mail, in UTC
- Friday 00:00
- That mail closes, in UTC
- Saturday 00:00
Oceania
- Server clock
- UTC+10
- Friday mail, in UTC
- Thursday 14:00
- That mail closes, in UTC
- Friday 14:00
North America
- Server clock
- UTC-8
- Friday mail, in UTC
- Friday 08:00
- That mail closes, in UTC
- Saturday 08:00
The dynamic player cap, at the bottom of a rewards post
The last paragraph of this announcement is not about rewards at all. Bellring says that “through today’s server-side update, we implemented a dynamic player cap feature for matchmaking”, and that “all game modes may now start matches with fewer players”. It is framed as an evaluation rather than a fix — the stated aim is to find out whether lower-density, lower-intensity matches are more satisfying — and feedback is asked for. This is the only place it has been published: it is in no patch note, and there is no client version to check it against.
- Every game mode, not one queue, and no figures. Neither the nominal lobby size per mode nor the new floor has ever been published, so nobody outside Bellring can say how much emptier a match may now start.
- Server-side, so there is nothing to download and no way to opt out. If your matches have felt thin since 9 September, this is a published cause rather than a coincidence.
- It lands six days after Brandrgarde Solo Mode opened two more queues — and the 5 August announcement said in advance that new modes “will inevitably split the matchmaking queue”. A thinner match is what a split queue produces. Bellring does not connect the two, and neither post mentions the other; that is this site reading between them, not a line anyone published.
How long it runs, and the date nobody has published
The event starts on the weekend of 11–13 September 2026 and runs “until the end of Season 1”. No end date for Season 1 has ever been published — this site tracks it as an open question rather than estimating it, because a season length converted into a calendar date is exactly the kind of figure that gets copied onward as though someone announced it. Treat any specific end date you see for this event as invented until Bellring prints one.
- First mail: Friday 11 September 2026 at 00:00 on your server’s clock.
- The Sunday of that first weekend, 13 September, is also the last day of the one-month anniversary claim window, which closes at 16:00 UTC+0 and needs Lv.5. Two unrelated clocks, one morning.
- DevNote #8 published the seasonal-reset framework without dating it, and the roadmap has carried no Season 1 end date at any point.