Carry the Glass Together Early Beta Notes

Ritronics Studios describes Carry the Glass Together as an early beta and a first Roblox game. That is not marketing fog. It tells you how to spend your patience. This page translates the label into player terms and points at the pages that still work while the place file changes. The parent log is the updates hub.

The experience is released in the sense that anyone can join on Roblox today. It is early in the sense that systems you expect from a year-old obby — codes, badges, a second map — may be absent. Both facts can be true. This wiki treats the title as live and unfinished.

What you should expect in a session

• Physics hitch when both avatars plus a pane plus a hammer share a small platform
• Camera clip on crane arms and the concrete overpass
• Checkpoint volumes that want both feet, not a toe — checkpoints
• UI that may gain a codes tab later — codes
• Servers that swing from busy to empty; use how to find a partner

None of that cancels the design. You still need two players. You still wait on hammers. You still use callouts.

What you should not expect yet

Do not expect a polished anti-cheat blog, a battle pass, or a Steam-style chapter select. Do not expect the Lighthouse map from SlugShot’s Carry The Glass. This is an unofficial fan-made Roblox obby inspired by that game, not a port. If a YouTuber shows ice bridges and a crab boss, they are on PC Steam.

Do not expect every clone server with “Bring the Glass” in the thumbnail to be this place. Use the official links place ID.

How to send feedback that might get read

The listing asks for honest feedback. Keep it specific: “checkpoint after the second hat did not save for the follower” is usable. “Game trash” is not. Send it through the creator’s group or the experience’s native feedback path, not through a random Discord that sells scripts.

If you found a physics exploit that skips the pane, consider not broadcasting it as a guide. This wiki will not host skip routes that delete the co-op.

How this wiki will behave during beta

We will update controls if binds appear on the HUD. We will update the obstacle tier list if a new mill shows up. We will not rewrite every paragraph with “as of this week” stamps; the site already injects a month/year in titles. If a patch contradicts a guide, the guide loses until we fix it.

Word of mouth will claim codes. We will not list them until they redeem. That is an early beta policy as much as a codes policy.

Play recommendation

Treat weeknight sessions as tests of how to protect the glass, not as a promise of a frozen route. If a patch makes a hammer faster, your Wait call still works. If a patch adds a codes button, redeem at a checkpoint. If a patch breaks saves, stop climbing and check this updates hub.

If a friend insists the game is “unreleased” because the word beta is in the listing, send them this page and the play link on official links. You can join tonight. You should still expect the floor to move under the pane.

Early beta is a warning and an invitation. The tower is already worth a duo night. Just do not tattoo last Tuesday’s mallet timing on your brain.