I don’t see the point in a remote event. If you are using the plugin, once you have required the animator, you can use animator.TweenName:Play() it gives you more in detail in the plugin’s tutorial
1 Like
No promises, but it will definitely allow you to get the player at least. Best way to diagnose code is to look for the basic things. Do you have Output open on your Studio? It and Script Analysis are two great tools to get past the smaller mistakes that everyone forgets about now and then.
EDIT
For example, it immediately set off errors when I started the game because the script couldn’t access localPlayer
1 Like
Yeah, I opened them and played the game for Output but nothing much happened, nothing related to applicationLoader.
1 Like
Do you mean that Output isn’t showing an error when you try to get
game.Players.LocalPlayer with a regular script
1 Like
Yes, I do. DevForum is forcing me to put more than 30 characters-
That means your Studio is doing the impossible. If the original script you posted is a Regular Script. And you run it. Output will show an error saying that loadingGUI cannot be equated to nil whereas nil is the LocalPlayer that cannot be accessed
1 Like
Wait, it worked with the Local Script. The problem was that it didn’t work with a Regular Script.
1 Like
Okay. Phew.
Is the problem solved now? Or is it still not working but at least it’s passed the first error?
1 Like
It is working now, thanks. I have to type 30 characters.
1 Like
Great to hear. Maybe mark the post above Where I mentioned replicating across the client server boundary as the solution or this one where I’ll say the same thing.
The issue was this.
Regular Scripts cannot directly affect the client, thus using
game.Players.LocalPlayer
from a Regular “Script” wouldn’t work. Simply changing the Script to a LcoalScript was all that was needed. Your script was good otherwise.
1 Like