The Duskbloods Closed Network Test Guide

Official test snapshot

The official FromSoftware and Nintendo notice describes a pre-release network test for The Duskbloods. It supports Nintendo Switch 2 and allows up to eight players in each multiplayer match while the game is still in development.

The application period ran from July 22, 2026 at 7:00 a.m. PDT through July 28, 2026 at 6:59 a.m. PDT. The notice says participants were selected in application order, with the selection result available from August 7 at 6:00 a.m. PDT. At the time checked, the official page marks the application period ended.

• Nintendo Switch 2 system required.
• An active Nintendo Switch Online membership is required for participation.
• Selected players receive a download code; the official download window begins August 18, 2026 at 6:00 a.m. PDT.
• The official page warns that session times can change or be cancelled without notice.

Network test schedule (PDT)

The official campaign notice lists five four-hour sessions. The Nintendo store teaser uses the shorter “Aug. 21-24” window, while the detailed campaign page lists the individual sessions below through Aug. 23. Use the campaign page for session-level timing and recheck it before playing.

• Aug. 21, 2026, 3:00 a.m. to 7:00 a.m. PDT.
• Aug. 21, 2026, 7:00 p.m. to 11:00 p.m. PDT.
• Aug. 22, 2026, 11:00 a.m. to 3:00 p.m. PDT.
• Aug. 23, 2026, 3:00 a.m. to 7:00 a.m. PDT.
• Aug. 23, 2026, 7:00 p.m. to 11:00 p.m. PDT.

What the test is measuring

The purpose is technical and balance feedback, not a promise that every visible feature is final. The official overview names three goals.

• Game server load test: connect many players at once and verify gameplay under load.
• Multiplayer test: identify issues across different network environments and large groups.
• Game balance test: collect data from real players competing in the same online ruleset.

How to use a test build as a guide reader

The network test is evidence about that test version. It can answer questions about controls, matchmaking flow, visible objectives, and stability on the day, but it cannot establish final launch balance, a permanent roster, or a complete story route.

Record the session date, region, build label, and whether a result came from an official notice, first-hand play, or a community report. That provenance is more useful than a screenshot without context.

• Treat bugs as expected in a pre-release build.
• Do not turn a test-only weapon name, map layout, or damage value into a launch database entry without a later confirmation.
• Check the official account page and FAQ for access questions; do not submit repeated applications.

What Fextralife adds (and what it does not prove)

The referenced Fextralife network-test page mirrors the official application window, five PDT sessions, eight-player limit, and three test goals. It also lists pre-set characters, limited locations, and featured bosses as things readers may expect from a closed test.

Those last items are expectations, not a confirmed content list. This guide therefore links the community page for discovery but uses the official network-test notice for dates, eligibility, and test scope.