New servers unable to be created, unable to join

Reproduction Steps

  • Join a new empty server

  • Wait to see if you are able to join, see Join Error

(This affects anybody trying to join)

Expected Behavior

  • Normal game join, able to play without error

Actual Behavior
We’re having issues with accessing the game, no one is able to join.

When joining and creating new servers on our game here: Pinewood Computer Core everyone has been getting disconnected with the error "There was a problem receiving data, please reconnect. (error Code: 260) or "this experience is currently unavailable, Please try again later (error Code: 517) the game is now completely down with no one able to join. The game hasn’t been updated since 11/11/2021 so it is strange to now be having issues with joining brand new servers.

Client error, network related
Errorwhileprocessingpacket

Error message
Error

Issue Area: Engine
Issue Type: Connectivity
Impact: Very High
Frequency: Constantly
Date First Experienced: 2021-11-16 13:11:00 (+00:00)

23 Likes

I first experienced this problem at 12:00 PM PST (UTC -8:00) when I made a private server for PBCC. Here is an image of the join error.

2 Likes

Update: We have rolled back to a previous version to where the game is functional again. A Roblox update today caused issues with something we’ve added recently (Where prior to today’s Roblox patch it worked fine) and we’re just figuring out where the conflict is, if we can find it I will let you know exactly what we found.

2 Likes

Update 2: FloatCurve is now broken and was the cause of the issue, as of today’s Roblox patch, parenting this property to a surfacegui crashes the server, causing the network error.

Here’s an uncopylocked game we’ve made that recreates exactly what happened: FloatCurve Test

See new thread here: FloatCurve property now causes severe game crash

5 Likes

Hi, you are correct. A recent change to FloatCurve instances has mistakenly introduced an incompatibility between different releases of Roblox. The new server version released yesterday introduces issues when replicating FloatCurve instances with non up-to-date clients. We are preparing a fix for this. In the meantime, you should refrain from using the FloatCurve functionality. We apologize for the inconvenience.

9 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.