Think of it this way; when a developer triggers a teleport request, theyâre effectively asking the client to comply. A malicious exploiter, bent on breaking the experience, is already capable of declining (or perhaps worse, stalling). As such, developers should not be operating on the assumption that teleports are enforced to begin with. For cases where itâs necessary, if developers are unable to implement a timeout, then I would consider that to be the real issue here.
Given this context, Iâm of the opinion that much of this doom calling is a bit unprecedented. When taking a moment to consider the matter thoroughly, I think it can be appreciated how little these changes actually impact developer freedom. Simply put, developers arenât giving anything up here. No one can force the client to join a new server on the developerâs schedule; the potential for these requests to stall, has always posed a concern. Now, with this update, the issue has merely been brought to light. This, quite frankly, is a very good thingâas its now elevated attention, should encourage more intelligent design (both from developers, as well as from Roblox in the form of API changes).