Blueprint Company How to Become a Blueprint Tester

Blueprint is not a click-to-play public Roblox experience yet. As of November 2026, the live path into the build is private testing. Public testing applications are not open right now — they open when a wave or release window starts, and applicants are accepted in waves with light device and anti-troll checks. This guide explains how to apply for private seats, what the NDA means, how to behave in closed builds, and how public waves will differ. Pair it with Getting Started and Public Testing.

Official channels: Discord invite https://discord.gg/U8f3Tynr99, Carrd https://rillcore.carrd.co/, and the Rillcore Studios Roblox group (community id 8133941). The Links Hub mirrors these destinations. Always prefer Discord announcements over random social screenshots.

Private testing overview

Private testing is the closed environment where Riley ships unfinished tools, UI experiments, and plot features to a limited audience. Access is application-based, not “follow and auto-join.” Private testing is 18+ and covered by an NDA. That means you agree not to leak builds, place IDs, or private footage in ways that break tester rules. If you cannot keep closed content closed, wait for public testing instead.

Why the gate exists: Blueprint is a solo passion project. Early builds need honest bug reports without spoiler storms or exploit tourism. A smaller, older tester pool keeps feedback usable.

Step-by-step: apply on Discord (private seats)

1. Join the official Discord using the invite above.
2. Read welcome, rules, and announcement channels before you type anywhere.
3. Find the application instructions — private testers use /apply (slash command / apply flow as documented in-server). Do not invent alternate DMs to staff.
4. Answer prompts honestly: age confirmation, platform (PC-first), building experience, and why you want to test.
5. Wait for review. Acceptance is not guaranteed; capacity and fit matter.
6. If accepted, follow the onboarding messages for roles, NDA acknowledgment, and how to launch the private place.
7. Join the Rillcore Studios group if instructed — group membership often pairs with studio projects.

Carrd also points applicants toward Discord applications. If Carrd and Discord ever disagree on a temporary process, Discord wins for live access steps.

What private testers should do in-game

• Create a small plot first; learn tools before city-scale spam. See Building Basics.
• File bugs with repro steps: plot settings, permissions, floor count, and whether pools, roofs, scaling, or landscaping were involved (Roofs, Floors & Pools, Scaling & Transform, Landscaping).
• Test permission edge cases from Plot System — public view-only vs friends builders vs everyone edit.
• Respect other testers’ plots. Griefing closed builds wastes limited seats.
• Keep NDA content off TikTok, YouTube, and public Discord servers unless Riley explicitly allows a showcase wave.

What private testers should not do

• Share invite links, place IDs, or “how I bypassed apply” guides.
• Demand paid perks — Blueprint has no gamepasses and no money system; testing is not a VIP shop.
• Expect mobile parity yet — Blueprint is PC-first; mobile comes after PC features mature (Controls).
• Claim public apps are open when Discord still says waiting for a wave.
• Harass the developer over missing Bloxburg-like jobs. Different design goals are covered in Blueprint vs Bloxburg.

Public testing (apps when open — waves)

Public testing means broader Roblox access without the same closed NDA circle. Critical timing rules as of November 2026:

• Applications open on release / when the wave starts, not now
• Applicants are accepted in waves so capacity and moderation can scale
• Expect comparatively light checks (device readiness + anti-troll), not a private-style forever gate
• Watch Discord #announcements and Public Testing for the live open signal

Until staff explicitly open a public wave, assume no public place ID exists — anyone selling “early Blueprint access” outside official Discord is not a legitimate source.

Public testers should still:

• Expect bugs and resets.
• Avoid exploit scripts — none are endorsed; Blueprint building does not need them.
• Ignore fake codes; there is no economy to redeem into.

Feedback that helps a solo developer

Useful reports are specific: “Pool swim detection fails after basement under 3-floor hip roof on friends-only plot” beats “game broken.” Attach short clips only if NDA allows. Feature ideas belong in official suggestion forms / Discord suggestion channels linked from Carrd — Riley has stated those are checked regularly. Track larger themes on the Feature Roadmap page so you do not re-ask shipped items.

After you are accepted

1. Finish Getting Started and set plot permissions deliberately.
2. Practice with the dorm-scale workflow in Building Basics.
3. Learn stack rules in Roofs, Floors & Pools, then creative multipliers in Scaling & Transform, Landscaping, and Furniture & Decals.
4. Bookmark Updates for patch notes during testing.
5. Invite trusted builders only after you understand visibility vs build rights.

Related community pages

Builder identity and collaboration notes will expand under Players. Curated inspiration may appear on Tier List. For studio identity and socials, stay on Official Links.

Becoming a tester is a responsibility seat, not a flex badge. Apply cleanly for private seats now, wait for staff to open public waves later, protect NDA content, file actionable bugs, and use Blueprint’s free sandbox the way it was meant to be used: build first, monetization never.