THE SHORT ANSWER
Roblox is releasing a reworked fix for incorrect collision geometry on wedge parts. The bug caused two side effects — wedge glides and wedge flings — that will no longer occur after the fix. Advanced obby techniques relying on wedges should remain unaffected, though users who depend on old collision behavior can request help.
- Fix targets incorrect collision geometry on wedge parts, addressing long-standing bugs creators have reported
- Wedge glides and wedge flings were side effects of the collision bug and will no longer happen on their own after this fix
- The initial September release broke several advanced obby techniques, prompting a rework that should only affect wedge-related methods
- Emote corner clips and uplodges remain unaffected by the reworked fix
- Creators whose games rely on the old collision behavior are encouraged to reach out for next steps
Roblox is rolling out a new fix for incorrect collision geometry on wedge parts. The announcement explains that the bug created two side effects: wedge glides and wedge flings. Both behaviors resulted from the underlying collision issue and will no longer happen independently after this fix lands.
The core problem was that the flat edge of a wedge could sink into the edge of a box instead of colliding with it. Additionally, WorldRoot:GetPartsInPart() could miss parts that were overlapping a wedge. These issues had been reported repeatedly by creators, and Roblox first shipped fixes in September. However, some of those changes broke advanced obby techniques that creators rely on. The team rolled the change back and has since reworked the fix.
The updated fix is expected to affect only techniques involving Wedge parts. Wedge glides and wedge flings — both side effects of the collision bug — will no longer occur on their own, which matches the September release behavior. Techniques that were unintentionally broken by the initial September release, such as emote corner clips and uplodges, remain unaffected and work as they did before.
Creators who built games around the old collision behavior and cannot recreate it in Luau are encouraged to reach out. The team will work with them on next steps. Some community members have noted that the transparency of publishing breaking change details is a positive step, even if the scope of an announcement feels narrow for something so technical. Others have raised the possibility of making similar toggles for other engine quirks, though some argue that would complicate the codebase unnecessarily.
The announcement credits @Delukes51 for reporting and testing the issue. Developers interested in discussing the fix or providing feedback can do so through the developer forum thread.