They removed this because you had access to the Explorer, Command Bar, and Toolbox in late 2012, early 2013 when they first implemented this feature, making place stealing extremely trivial to pull off, not to mention exploits were rampant.
However, I agree with allowing teleporting inside of Studio, IF it’s a place within a game you own, or between two places you own (that could be in different games.)
I think teleportservice should be locked in Studio, first of all, if both project are laggy it can make your pc slow, and it might take time to load both projects, and we aleready know if the teleportation was suceeded or not by the orange text output, but ye it makes more sense to implement a feature like that if youre talking about debugging like loading screens and crossover values
I feel that this could be added easier if a new studio client automatically opened when you teleport, closing out the old one. The new one would be in a playtest in the other place already, just like when you test multiple clients. You obviously wouldn’t be able to test teleporting to games you don’t own, in studio.
Explorer / Toolbox / etc used to be part of the client and was removed from the client for security reasons, but that was even before teleporting was removed from studio
Also they were removed for deleting the map/etc not place stealing (there was never any file save in the client)
There was a save dialog in the client a long time ago, but only if you were the owner and that was validated on the backend, so no security risk
Unfortunately you have come to an incorrect conclusion because that is simply not true. This is coming first hand from an engineer. This was not removed because of place stealing.