Scripting Helpers is winding down operations and is now read-only. More info→
Ad
Log in to vote
0

Is there a way to have Custom Loading GUI's that don't disappear?

Asked by
Overscores 381 Moderation Voter
8 years ago

So, you know when you use the TeleportService to teleport a player and you can insert a custom loading GUI? How would I make it so that after it teleports the player, it stays forever?

2 answers

Log in to vote
2
Answered by
joritochip 705 Moderation Voter
8 years ago

If the destination place is also your game, you can place the same GUI (the loading one) inside of StarterGui to give it to the player again upon joining the destination place. There is no way to keep the custom loading GUI directly through TeleportService.

If the destination place is NOT yours, you'll have to contact the developer to have them put it in the game.

0
Accept the answer and give it a thumbs up if I helped! :) joritochip 705 — 8y
0
No Overscores 381 — 8y
Ad
Log in to vote
0
Answered by
DanzLua 2879 Moderation Voter Community Moderator
8 years ago
Edited 8 years ago

We can set a CustomLoadingScreen to be shown while the player is teleporting, then after the player has arrived at the destination we can remove that gui using the gui instance that LocalPlayerArrivedFromTeleport gives us (Or you could not destroy it resulting in it stay there :P I'm guessing like how you want)

**But scripts and tweening will not work with this! ** Lets start by teleporting the player,

view source
1game:GetService('TeleportService'):Teleport(1818, game.Players.Player1)

Your normal teleport line right? But we can also give :Teleport more things to work with,

view source
1void Teleport (
2    int placeId,
3    Player player = nil,
4    Variant teleportData,
5    ScreenGui customLoadingScreen = nil
6)

Basically this is like,

view source
1:Teleport(placeID,THEPLAYER,ATABLE(USEFUL :D),ThisISTheGUI!!!!!)

We can send it a useful table of information we want to send over and the custom loadinggui.

Lets make the script,

view source
1local guitosend = script.Parent.Gui --CHANGE to the gui your sending!!!
2local info = {} --atm this table is empty
3local id = 1231234
4 
5game:GetService('TeleportService'):Teleport(id, game.Players.Player1,info,guitosend)

There we go, we have our teleporting from place setup now lets go to where they'll be arriving.

We are going to setup a local script that will fire when someone is arriving from teleporting.

This will be a localscript and it will be located inside ReplicatedFirst

We will use LocalPlayerArrivedFromTeleport event from the teleport service to fire this code

view source
1game:GetService('TeleportService').LocalPlayerArrivedFromTeleport:connect(function(customLoadingScreen, teleportData)
2 
3end)

As you can see it gave us two values, the gui that we sent over from the other game and that empty table we set called info

right now the code is not running anything so the gui will remain on your screen forever. But you could wait for the character to spawn in and then remove it with cutomLoadingScreen:Destroy() but the choice is yours :)

Hope you found this information useful :D Source 1 Source 2

Answer this question