Roblox’s Build A Boat For Treasure has an official experience page, and its public server list shows players in active servers. The deletion rumor began with a 48-hour notice to make changes that the developers shared. The first feature they adjusted in response was the sign block, which lets players add text to their boats.
Several updates circulated at once: a notice that signs had been temporarily disabled, reports that signs came back with a 60-second cooldown, and word that the experience could be taken down. Those details were easy to conflate, but each means something different. If you’re wondering whether you can build a boat right now, the official server status is the first place to look. Roblox’s chat policies help explain why signs might have a cooldown. The specific violation and the notice’s final outcome are separate questions, and the publicly available information doesn’t establish both.
Where did the Build A Boat For Treasure deletion rumor start?
According to the developers’ notice, Roblox said Build A Boat For Treasure was violating policy and could be taken down if the issue wasn’t fixed within 48 hours. The developers said they hadn’t received a specific explanation of what in the experience was causing the problem when they posted their update. While waiting for more information, they temporarily disabled the sign block as a precaution.
The 48 hours were a deadline to make changes, as the developers described it—not evidence of a scheduled shutdown at a particular time. Servers can remain online while developers work on a fix, and whether the sign feature was actually the reason for the notice is a separate issue. The public information doesn’t confirm a final decision from Roblox or a shutdown time that applies to everyone.
For signs, the initial update said they were disabled temporarily; a later report said they were re-enabled with a 60-second wait between text submissions. That follow-up is described in the source material, but no publicly available official patch record confirms exactly when or on which servers it took effect. So it’s most accurate to treat the 60-second cooldown as a reported change, rather than conclude that signs were the confirmed policy violation.
Why would signs on boats need a 60-second cooldown?

Signs are a natural fit for a building game. You can name your boat or show other players where to sit when they first board. A label like “Helm” or “Launch here” can stay in place, so you only need to write it once. But if several players can keep changing the same sign, it can also function like a chat window. The key difference isn’t where the text appears; it’s how people use it to communicate.
Roblox’s developer documentation says chat should use TextChatService, its official text-chat system. That system applies text filtering as well as age-based restrictions and players’ chat privacy settings. For features where players enter text for others to see—such as signs or bulletin boards that aren’t intended for chat—the guidance calls for a minimum one-minute interval between submissions by each user. Players can still read a message, but they can’t rapidly edit it back and forth as a way to chat.
Filtering and cooldowns do different jobs. Filtering controls what text others can see; a cooldown limits how often that text can change. For example, even if every offensive phrase is filtered out, two players could still rapidly swap messages using a sign. Conversely, limiting updates to once a minute doesn’t by itself block inappropriate text. The 60-second figure addresses the first issue: slowing down the pace of the exchange.
The rules can also depend on who’s allowed to change the text, even when the object looks like the same kind of sign. A fixed “Launch Area” label written by the developer and visible to everyone is different from a sign where players can enter their own text for others to read. Fixed messages that players can’t edit, like the first example, aren’t subject to the same submission-interval requirement. Reading the policy as a blanket ban on sign blocks would miss that distinction.
That policy offers a plausible reason for the developers to check the sign feature first. But general platform guidance and a notice sent to a specific experience are different kinds of evidence. The official documentation confirms the guidelines for features like signs. The developers’ public explanation confirms that they considered signs a possible cause and made changes to them—that’s all it establishes.
What changes for players if signs are limited?
In Build A Boat For Treasure, you make a boat out of blocks, launch it down a waterway, and navigate obstacles to reach the treasure. Naming a boat and building and sailing it are separate activities in the core gameplay. News of a limit on sign input isn’t evidence that building or launching boats is restricted too.
Still, the same sign limit can affect players differently depending on how they use it. If you add a name to a finished boat once, you may only notice a brief wait when submitting the text. If you’re testing a build with friends—especially one with multiple seats and controls—and frequently updating instructions, the cooldown can interrupt your workflow. You can still sail without entering text on signs, but one way of explaining an unfamiliar build to other players becomes slower.
For example, if your boat has several seats, you can use different colors to distinguish the helm from regular seating and reserve signs for labels that are unlikely to change. That keeps the build looking organized and helps first-time passengers find a seat without having to read every sign. Rather than asking whether signs are valuable at all, it helps to consider which instructions are built into the structure and which depend on editable text.
What the official server list shows

The official Roblox experience page lists Build A Boat For Treasure, and its public server list shows player counts. The game information records a creation date of November 2016 and more than 5.2 billion visits. Visits can include multiple sessions by the same player. For evidence that people are playing now, the current player count in public servers is more relevant than the cumulative visit total.
Seeing players in public servers doesn’t show that sign input works the same way in every server. The official server list shows servers and player counts, while the experience information displays its last-updated time. That timestamp alone can’t tell you how signs changed, whether Roblox accepted the developers’ fix, or what happened to existing builds or saved slots.
If you’re worried about a boat or build you’ve spent a long time on, it helps to consider access, features, and saves separately. Players in official servers answer the question of whether the experience is accessible. Being able to enter text on a sign—or seeing a cooldown—shows the status of that feature. Save slots determine whether you can reopen your creations in-game. A report about one feature being unavailable doesn’t, by itself, establish the status of saved builds; assuming it does can make the concern bigger than the confirmed change.
Why a notice needs a specific explanation
When the change needed is clear, as with a sign limit, developers can adjust part of a feature while keeping building and sailing intact. But if they receive a short deadline without knowing which screen or action caused the problem, they may disable whichever feature seems most likely. A notice that identifies the feature, the applicable policy, and how to submit a fix would help developers narrow the impact—and help players understand why something they used has changed.
The best way to follow the situation is to look to different sources for different answers: public servers show whether the experience is running; developer updates explain which features changed; and a final update from Roblox or the developers would clarify how the notice was resolved. Build A Boat For Treasure remained playable in public servers, and signs were the first feature the developers adjusted. Taken together, those facts give a clearer picture of how the 48-hour notice affected actual play.
