Hey Developers,
Very soon we are going to be making a subtle change to the way ReserveServer
works. We do not expect many of you to be affected by this change, however a few of you might be.
What is the change?
At the moment when you call ReserveServer
it returns a single result, the access code which is used in TeleportToPrivateServer
. With this change we will be returning a second result, the PrivateServerId
of the reserved server, this ID matches the existing VIPServerId
property on the DataModel
.
VIPServerId
and VIPServerOwnerId
will also be deprecated in favor of PrivateServerId
and PrivateServerOwnerId
.
Why are we making it?
The purpose of this change is to allow developers to store information related to a specific reserved server in a secure way and provide a way to access that data from both the reserved server itself and the server which made the reservation.
What should you do?
While these changes are unlikely to affect many of you, there are a few cases where they might. If you are calling ReserveServer
inside of a call to another method then be aware that PrivateServerId
will also be passed through this call along with the access code. The following is an example of such a case where this could cause errors.
table.insert(accessCodes, teleportService:ReserveServer(placeId))
Since table.insert
can also accept three values it will now throw an error since it expects the second value to be an integer rather than a string.
When will this happen?
We will be enabling this change on Monday the 3rd of September.