|
| 11 Nov 2012 04:31 PM |
What if:
Somebody, before WedgeParts existed, joined a server. The server was capable of instancing a wedgepart through a spoken command. After the parts are released, a new player comes on the with new version of Roblox. They say the command and a wedgepart appears.
Does the WedgePart:
Get deleted by the old client saying it doesn't exist, Just not replicate to the client Turn into a part as it is classed as a BasePart Make the physics engine explode due to clients and server saying different things happening to the same part. |
|
|
| Report Abuse |
|
|
|
| 11 Nov 2012 04:40 PM |
| When big updates like that happen roblox disables game joining until all the games are empty, then releases the update. None of these would happen. |
|
|
| Report Abuse |
|
|
|
| 11 Nov 2012 04:59 PM |
| Most likely the client would stop responding. |
|
|
| Report Abuse |
|
|
|
| 11 Nov 2012 05:07 PM |
First, you have to know that this situation is impossible and cannot happen.
Now, assuming it could happen, well, I'm not sure what would happen, but it certainly wouldn't stop responding.
When you open a newer place file with an old client, it just says that there was an error while parsing the XML in the output. |
|
|
| Report Abuse |
|
|
|
| 11 Nov 2012 05:21 PM |
| How could they instance a WedgePart if they don't exist yet? |
|
|
| Report Abuse |
|
|
|
| 11 Nov 2012 05:33 PM |
| I think he means that there's code ready to instance a WedgePart before it exists, so he doesn't have to update the game when the update comes out. |
|
|
| Report Abuse |
|
|
stravant
|
  |
 |
| Joined: 22 Oct 2007 |
| Total Posts: 2893 |
|
|
| 11 Nov 2012 05:35 PM |
Fortunately the situation can't happen that way. Any reasonable command script would be unable to do that.
However, let's construct a situation where it _can_ happen: - The chat scripts are all local - the chat script lets you create an instance of arbitrary type, which is parented to workspace. - Player enters a server with an old version of the game.
I suspect that the resolution of the problem is simply that the client won't even be able to connect to the server, since the server will reject the connection on the grounds that it's a different version.
If they can connect, then the "new object" packet would likely just be rejected because the type was not recognized.
It's unlikely that it would cause any problems. |
|
|
| Report Abuse |
|
|