The E-Day Multiplayer Beta uses Steam AppID 4059240, while launch rewards appear in the base game, AppID 3010850. Progress carries from the August 6–10 early-access weekend into the August 13–17 open weekend. At launch, the Beta Player Title, Beta Medal, and any unlocked Beta Challenge rewards remain; Class progression, Player Level, and other Medal progress reset.
That means the reward item can survive even when the level or progress bar used to earn it does not. Treat the Beta as a limited test and reward event, not an early start on the permanent class grind.
Check the two Beta windows
Early Access runs from August 6 at 12:00 p.m. PT to August 10 at 10:00 a.m. PT for eligible pre-orders and memberships. The open weekend runs from August 13 at 12:00 p.m. PT to August 17 at 10:00 a.m. PT and is open to players on eligible platforms without a pre-order. The official FAQ says the content is the same across both weekends.
Convert Pacific Time for your own region and leave completion margin before the closing time. A match that starts near closure may not finish, sync, or register before service shutdown. The page date and a player’s local clock are not substitutes for the official window.
Official Beta challenge rewards
The official Open Beta Details page lists six reward goals:
- Epic Blast Damage Mags Character Skin: reach Player Level 20.
- Rare Crush the Bug Weapon Skin Set: extract from Horde Siege eight times on Infantry difficulty or higher.
- Crush the Bug Banner: get 25 headshots.
- Crush the Bug Emblem: perform 10 revives.
- Crush the Bug Icon: perform five Prototype Lancer chainsaw executions.
- Open Beta Medal and First in the Fight Title: launch the Multiplayer Beta.
These requirements are Beta-specific official values checked August 8, 2026. Read the live challenge panel for tracking and claim state. Do not assume a headshot, revive, extraction, or execution counted until the corresponding progress updates.
Prioritize by dependency, not just quantity
Launching the client is the simplest entitlement check. Next, inspect all six challenges and verify that progress is visible. The Mags skin depends on Player Level, so normal play across both modes can advance it. The extraction reward is more constrained: it requires Horde Siege, eight successful exits, and Infantry or higher.
Revives and headshots can be pursued during ordinary team play without abandoning the objective. The Prototype Lancer execution goal needs the named weapon and the correct chainsaw finish. Do not throw a mission by forcing an execution in unsafe conditions; five registered results across the event are better than repeated squad wipes.
For limited play time, complete goals with the most specific mode dependency first. General Player XP can continue in more activities, while successful Horde extractions need a full mission and a safe exit.
What carries between Beta weekends
The official FAQ says challenge and Medal progress, rewards, Class progression, and Player Level carry from the early-access weekend into the open weekend. Players do not need to restart the Beta grind on August 13 if the same account and entitlement load correctly.
If progress appears missing, do not immediately repeat a long challenge. Confirm the same Steam account, restart the client, check official known issues, and preserve a screenshot of the challenge panel. Account or service mismatches are more useful to support than an estimate of what the bar “should” show.
What carries to launch
At launch, unlocked Beta Challenge rewards remain available, along with the Beta Player Title and Beta Medal. The Beta’s Class progression, Player Level, and other Medal progress do not carry and are reset.
Use this as a ledger:
- Keep: eligible reward items already unlocked through Beta challenges.
- Keep: Beta Medal and Beta Player Title.
- Reset: Assault, Breacher, Marksman, and Medic class progress earned in the Beta.
- Reset: Beta Player Level.
- Reset: Medal progress other than the preserved Beta Medal.
The FAQ does not support transferring Beta XP into an equivalent number of launch levels. A retained skin or title is not evidence that the underlying progression survived.
Confirm a reward without risky account changes
Open the Beta challenge screen, record the task text and current value, complete one qualifying action, then check the same panel after the match. For an extraction challenge, wait for the mission completion and reward flow rather than leaving as soon as the Raven animation begins.
Avoid unlinking accounts, deleting saves, reinstalling repeatedly, or switching identities while troubleshooting a server-tracked reward. Steam Beta play does not require a Microsoft account for normal access; the FAQ says linking is needed to send cross-platform squad invites. The final base-game account rule may differ and must be rechecked near launch.
If a challenge fails to update
First verify the exact qualifier: difficulty, named weapon, execution type, successful extraction, or target count. Then restart the Beta and check the official Known Issues announcement. Capture the Steam account context, AppID 4059240, date, platform, match type, and a before-and-after image of the progress panel.
Submit reproducible problems through official Gears support. Do not use a trainer, edited save, third-party unlocker, or another game’s configuration file to force a server reward. The Beta is not final software, and service delay can look like a failed local trigger.
Beta reward FAQ
Do levels carry from the first weekend to the second?
Yes. Player Level, Class progression, challenge progress, Medal progress, and rewards are announced to carry into the open weekend.
Do those levels carry into the October launch?
No. Class progression and Player Level reset for launch. Only the specified Beta title, medal, and unlocked challenge rewards remain.
Must I pre-order for the second weekend?
No. The August 13–17 window is open to players on eligible platforms without a pre-order.
Is the Beta client the base game?
No. On Steam it is a separate product, AppID 4059240, from base-game AppID 3010850.