Nuclear Design Bureau Discord and Community Channels

Nuclear Design Bureau Discord is not a side channel for this game; the developer treats it as the main one. The official description states there is an active Discord community and asks players to join to participate in the game's development, then adds that most of the day-to-day happens on Discord. For an Early Access sim whose physics, tools and campaign are described as changing based on what players build and where they get stuck, that makes the server part of the documentation.

The Official Discord Links and Support Channels

Two Discord invites appear in the official record, which is worth knowing before you join anything claiming to be the community server. The Steam store's support link points at one invite, and SteamDB lists another as the official social link, so verify which one the developer is currently promoting rather than trusting a search result.

Channel	Where it is recorded
Discord support link	Listed on the Steam store page as the support contact
Discord official social invite	Recorded by SteamDB in the app's social media field
Support email	A Design Bureau KB-11 address appears in the store support record
Steam Community Hub news	Official hotfix and physics patch notes
Steam discussions	Player-run threads on yields, designs and specific directives

• Use the Steam store page's own support link first, because that is the developer-controlled field.
• Expect the community server to be the place where build feedback is collected, not a general chat room.
• Community and meta features such as a public leaderboard and per-directive statistics are planned rather than present.
• The developer's Early Access framing is that player feedback decides what gets worked on next, so a clear report has a real chance of being acted on.

What the Community Is Used For

Three distinct activities show up in the recorded material, and they are all more useful than general chatter. The first is design sharing: Steam threads contain detailed multi-stage layouts, casing thicknesses and reported yields, and the developer's own description says players share designs and discuss mechanics. The second is bug reporting, with specific threads about directives and simulation behaviour that have fed into patches. The third is learning the physics, because the game ships without a published build recipe.

Activity	Documented example
Sharing designs	Threads describing layered ellipse layouts, casing widths and reported yields
Reporting bugs	Directive-specific threads, including one about a device that would not work
Discussing mechanics	Neutron activity and ignition thresholds discussed between players
Following patches	Official notes covering simulation fixes, crash fixes and burn speed
Comparing results	Planned leaderboard and per-directive statistics on the roadmap

• Treat community numbers as to confirm until you reproduce them, because physics patches have changed yields and compression behaviour.
• Search the server and the Steam discussions before posting, since directive naming makes older threads easy to find.
• Post your build state alongside the problem, including the directive and the patch version, because the simulation changes between builds.
• Read the changelog before claiming a bug, since several reported failures were fixed as simulation defects rather than design mistakes.

Joining Safely and Where Else to Look

Joining is straightforward, but a few habits keep the community useful. Check that the invite you clicked came from the store page or the app's recorded social links rather than from a random third-party page, and expect that the developer's own communication is patch notes rather than a roadmap blog. Steam remains the authoritative feed for what changed, because every hotfix and physics note is published there with a dated changelog.

• Prefer the official support link or SteamDB's recorded social invite over a link copied from a forum post.
• Keep patch notes and community claims separate in your notes, since one is dated official text and the other is player experience.
• Use the Steam Community Hub news feed as your primary changelog and the server for discussion.
• Avoid sharing account details or installers, and remember that official builds come from the Steam store page only.

If you are new, the most useful first stop is the loop itself rather than the chat: the guide page covers directives, the criticality lab and refining, and the tips page collects the habits that stop you rebuilding from scratch. The community is where those habits get stress-tested against other players' designs.