Problems when using Script.Parent on "Local"

Help and Feedback Scripting Support
, ,
#62

Are there any possible way for the tool in backpack to find it’s root like locate it back to the seat?

#63 
-- Local script in PlayerGUI or StartPlayer.StarterPlayerScripts
-- Make your seat a unique seat name ..

local rs = game:GetService("RunService")
local player = game:GetService("Players").LocalPlayer
local char = player.Character or player.CharacterAdded:Wait()
local humanoid = char:WaitForChild("Humanoid")

humanoid:GetPropertyChangedSignal("Sit"):Connect(function()
	rs.Stepped:Wait()

	if humanoid.Sit == true then
		if humanoid.SeatPart.Name == "AirCraftSeat" then
			local airCraft = humanoid.SeatPart.Parent.Parent.Parent
		
			print(airCraft.name)
					
		end
	end
end)

This should print: Aircraft. I’ve used this trick in the past, works well.

#64

Use this on StarterPlayerScripts? Alright

#65

Wait about the Local Aircraft thing, what do i use then?

#66

This will get you to Aircraft … and know you’re sitting the seat.
Add your code after that. Where print is … or call a remote.

#67

So i paste the Remove Event after the Print Aircraft thing?

#68

I’m getting very much confused right now since the tool goes to the backpack, i think i might need to find out how to make a seat that can use keybinds to fire a RemoteEvent

#69

That is how to target that folder using the seat. The rest is a different question.

1 Like
#70

Alright i guess, now i can just parent it to the vehicle without creating different vehicles

#71

Thanks for trying to help me guys.

#72

You should go learn how to use remotes anyways. It sounds like a big thing but it’s not. Soon you will use them all the time.

#73

Alright, thanks for the tip, I’ll learn more about Remove Events now

#74

It was a joke man…

spoiler