Roblox Connect, the feature that let friends call each other as their avatars inside a shared 3D space, stopped working on July 15, 2026. Roblox turned off both the consumer-facing feature and the developer APIs behind it on the same day, ending a run that started in November 2023. Company spokesperson Angela Allison confirmed the full shutdown to Next Reality, saying users aged 13 and older were already choosing Party Voice, the platform's voice-only private calling feature, before the switch was flipped.
There was no farewell event and no replacement that does the same thing. Roblox simply pointed everyone at Party Voice.
What Roblox Connect actually did
Connect was more ambitious than a normal video call. Instead of showing your face, it showed your Roblox avatar, which copied your real head and face movements through the camera in real time. Two friends could then walk around a shared virtual location together while they talked.
Per Roblox's own Connect FAQ, the feature had clear limits from the start:
- Callers had to be 13 or older and voice-enabled, meaning phone-verified or ID-verified.
- It ran on mobile (iOS and Android) and desktop.
- Calling only worked in countries where voice chat was already available.
- Only experiences more than a week old could use the calling APIs.
- Friends could teleport between set locations during a call, such as a forest campfire, a dock, a waterfall, or an island beach.
Roblox also open-sourced the Connect experience and its APIs so any creator could build avatar calling into their own game. That openness is exactly why the shutdown reaches further than one feature.
The five calling APIs that stopped working
The developer side of the shutdown was announced a month ahead, on June 15, in a Roblox Developer Forum post from staff member "bopomopho." It named five SocialService APIs (the official set of social functions Roblox gives creators) that would go dark on July 15:
CanSendCallInviteAsyncPromptPhoneBookPhoneBookPromptClosedOnCallInviteInvokedCallInviteStateChanged
After the cutover, the calls do not crash a game, but they do fail. CanSendCallInviteAsync now always returns false. PromptPhoneBook shows players an error dialog instead of opening the phone book. Call invites are marked ineligible, and the callbacks never fire.
Roblox told creators to search their own code for those five names, remove or guard the code, fix any calling menus so players do not hit a dead button, and publish the updated game before the deadline. That deadline has now passed.
A one-month window with no migration guide
One month is a short runway for a breaking change. The forum post did not ship a migration guide to Party Voice's APIs, and it did not give creators a tool to find every affected game at once. It told them to grep their codebases and ship fixes. For a solo developer running several experiences, that is real work with a hard deadline.
Developer reaction in the thread was mostly indifferent, with several creators saying the feature was rarely used and that "nobody asked for it in the first place." But at least one developer pushed back, writing that the community had been waiting for Connect to support more simultaneous callers, the upgrade that would have made avatar calling practical inside a real game, and that the upgrade never came.
That is one person's view, not a measured trend. Still, it raises a fair question Roblox has not answered: was Connect unpopular because players did not want it, or because it was never finished? Roblox's public position is only that Party Voice is where users already were.
Why Party Voice won
Party Voice is not a like-for-like replacement. It is voice only. There is no avatar, no shared space, no camera tracking. If you wanted the thing Connect did, there is no substitute for it today.
But Party Voice is far easier to police. A Roblox staffer described it in the June forum post as handling private voice chat "in a way that's more capable and better suited to how players use Roblox today." It requires a verified age of 13 or older and keeps calls among eligible users, including Trusted Friends. Moderating a voice channel is a much smaller job than moderating live avatar rendering inside a shared virtual room. Given the pressure Roblox is under over child safety, the simpler surface is the safer one to keep.
What this means for Filipino Roblox players
Roblox is free and global, so Connect's shutdown reaches Filipino players the same day it reached everyone else. There is no separate Philippine rollout, price, or timeline attached to this change. What makes it land differently here is the regulatory backdrop.
In March 2026, the Cybercrime Investigation and Coordinating Center (CICC) gave Roblox 30 days to answer concerns that predators and drug traffickers were using the platform to reach underage users, and it threatened a nationwide block. The Department of Information and Communications Technology (DICT) and the CICC then met Roblox on April 7, after which the government said it would not ban the platform and would instead press for stricter monitoring and age-appropriate content controls. Roblox followed with age-based accounts — Roblox Kids for ages 5 to 8 and Roblox Select for ages 9 to 15, rolling out from June, with communication switched off by default for the youngest tier.
Seen against that, retiring an age-verified, camera-driven, avatar-rendered calling product and standing behind a voice-only one fits the direction Roblox has been pushed in — the same age-gating logic now shaping Meta's AI age detection and teen content filters. Roblox has not linked the Connect shutdown to the Philippine talks, and no source says it did, so treat this as context rather than cause.
The practical takeaway for players here is small: if you used Connect to call friends, use Party Voice instead, and expect to be phone- or ID-verified as 13 or older to do it. For Filipino creators with games built on the calling APIs, the fix is not optional — those buttons are already broken for your players.
A pattern worth noticing
Connect joins a growing list of services quietly folded into a simpler sibling, much like Samsung Messages shutting down and pushing users to Google Messages. The lesson for anyone building on a platform is the same each time: an official, open-sourced API is still the platform owner's to withdraw, and the notice period may be shorter than the work it creates.
