How do I make a tool detect what brick I have clicked on?
How do I use mouse.Target to set the brick that I click?
like
'when player clicks'
brick = mouse.Target
or something like this.
0
0
0
0
2 answers
so first, in a local script establish some variables also, create a remote event and put it inside the replicated storage
1 | --put this in the tool |
2 | local plr = game.Players.LocalPlayer |
3 | local mouse = plr:GetMouse() |
4 | local tool = script.Parent |
5 | local event = game.ReplicatedStorage.RemoteEvent |
then after establishing the variables, you need an event when the tool is clicked, luckily there is already and event for that, it is the Activated event
01 | local plr = game.Players.LocalPlayer |
02 | local mouse = plr:GetMouse() |
03 | local tool = script.Parent |
04 | local event = game.ReplicatedStorage.RemoteEvent |
05 |
06 | tool.Activated:Connect(function() |
07 | local target = Mouse.Target |
08 | if target then |
09 |
10 | end |
11 | end) |
if you want to modify the properties of that part then you need the remote event.
01 | --local |
02 |
03 | local plr = game.Players.LocalPlayer |
04 | local mouse = plr:GetMouse() |
05 | local tool = script.Parent |
06 | local event = game.ReplicatedStorage.RemoteEvent |
07 |
08 | tool.Activated:Connect(function() |
09 | local target = Mouse.Target |
10 | if target then |
11 | event:FireServer("ChangeProperties",target) |
12 | end |
13 | end) |
14 |
15 | --server |
Reminder that this is basic stuff! If you don't want to try this, then go on with theking48989987's answer!
Put a tool inside, and uncheck it's ReqiresHandle checkbox. It should be somewhere inside StarterPack.
After that's done, add a LocalScript inside it. There should be some code like this:
1 | local mouse = game.Players.LocalPlayer:GetMouse() |
2 | local player = game.Players.LocalPlayer |
3 | script.Parent.Activated:Connect(function () |
4 | local target = mouse.Target |
5 | if target then |
6 | print(player.Name .. " targeted " .. target.Name .. "!") |
7 | end |
8 | end) |
This line of code is simple and basic to go through.
First, Line 1 and 2 declare the local player and it's mouse. (their client)
Beginning of the third line connects an event listener.
The lines of code after that declare a variable, which can be used to know which part the Mouse is targeting, so it goes through a check, if the mouse's Target exists. If we didn't add that if condition, we would get an error while printing this through the console output.
This is pretty much most of the basic stuff this sample of code can do. and when you click a part, it will print it to the Output. (can be turned on in the View tab)
There's also dot notation in one line of the code sample. This is an efficient way of getting to print multiple declared strings at one line to the Console.
The console is very useful and powerful when debugging, and is a great need.
If you don't get what you expected, you'll have some errors.