this is probably the first roblox studio vid i've ever paid full attention to and actually understood the things that made it work this is awesome can't wait to watch more of your vids
Bro I don't know why you only have 38 comments on ur video but I love your videos! You got me into scripting and you've really helped me and when I wake up (it's 3:50 AM rn lol) Im gonna do your challenge yet try to make the scripts better and make it so it works on any part love your videos keep up the good work cya! ❤❤
i really do not like using clickdetectors, they just simply wont work properly when theyre a moving physics object if you are making a physics based game (like build a boat for treasure) please do not use click detectors, just make your own clickdetector using scripts
Why do we have to put that (plr) in the function? And also what does Part.color = partColor do? For me it makes it so that when I leaveHover it goes back to the normal color
Because whenever the part is clicked, it gives us the player who clicked, which we can then name whatever you want (so i named it plr, but you can literally name it anything). The goal with part color was to get the parts color before any changes occur, so that we know what its default color was before we changed anything.
I mean you can handle it in a local script as well lol, Roblox just does the grunt work of sending a message to the server whenever it detects a client click
I don't see how it is stupid, like if It actually was a property setting then people would complain why other things such as "Highlight" doesn't exists in property and then again if roblox adds it they will complain more. I like the idea of having a simple non crowded property tab. The fact that you can also do script.Parent.ClickDetector:Destroy() which would be useful in some cases.
I get what you mean, but ClickDetectors just don’t have enough properties to justify being their own instance (MaxActivationDistance could’ve just been a sub-property of a potential “Clickable” property in every part). It can also be confusing to look for MouseClick inside the ClickDetector and not the part itself. The only explanation which I’ll accept is that, somehow, giving every part the option to be clickable ruins performance
@@byteblox100 I agree, ClickDetectors not having more properties to justify really sucks. But since the only way to make ClickDetectors work is using your scripting skills. Having scripting skills lets you justify those ClickDetectors properties yourself by making them yourself (with script). Example: when clickDetector Clicked, if click detector is on (Specific team) then (run code) Otherwise you can make or find a click detector plugin for your viewers or for yourself (if you use click detector a lot in your projects) so it would be easier for them and for you. I see what you meant in the video now.
How are click detectors stupid? There is a reason they are not just properties of all instances. Firstly, that would be inefficient to add a property that very few parts use created every time an instance is created. But most importantly, how would ClickDetector's events work if it was just a property of instances? Properties can not have events, so a "clickable" property would be completely useless.
@@byteblox100 btw I was responding to a reply you posted under another comment: "I get what you mean, but ClickDetectors just don’t have enough properties to justify being their own instance (MaxActivationDistance could’ve just been a sub-property of a potential “Clickable” property in every part). It can also be confusing to look for MouseClick inside the ClickDetector and not the part itself. The only explanation which I’ll accept is that, somehow, giving every part the option to be clickable ruins performance"
Honestly I’m fine with it being an instance as long as it has enough properties/events to differ it from just being a property of the part. Dragdetectors are click detectors + able to drag, as in literally an upgrade (just make RunLocally to true and you just have a click detector which also detects drag)
@@byteblox100 You say you're "fine" with it being an instance, but what else can it be? Like I said, properties can't have events so then you'd lose a lot of functionality that makes click detectors useful. Okay, but why would you use a drag detector if you only want to act on clicks? Then you're running physics and wasting resources by calculating the physics involved in dragging.
Let’s grow a helpful Roblox developer discord together 🔥
discord.gg/ay5gc9XcAh
that wasnt a good idea
this is probably the first roblox studio vid i've ever paid full attention to and actually understood the things that made it work this is awesome
can't wait to watch more of your vids
bro, you are the first roblox channel that explain EVERYTHING that he script
Bro I don't know why you only have 38 comments on ur video but I love your videos! You got me into scripting and you've really helped me and when I wake up (it's 3:50 AM rn lol) Im gonna do your challenge yet try to make the scripts better and make it so it works on any part love your videos keep up the good work cya! ❤❤
Simple yet entertaining for newbies :)
🍇
@@byteblox100 grape
I like how you disguise a tutorial as a funny video. really clever and cool. thumbs up and subbed.
U didn t want to make it a tutorial but i just learned something new
click detectors are broken, the right click, hover, and hover leave functions work but when i use mouse click it just doesnt do anything
I found this account a few days ago, Keep it up!
This tutorial is very good thx! Btw, can other people in the sv see if the part changes color?
If you use a server script, yes
@@byteblox100 Thx! U deserve a sub and a like!
Hi, is it possible to use clickdetector and click on part, when your tool is equipped, if it is > how to do it? Thank you!!!
This tutorial is helpful, thanks!
i really do not like using clickdetectors, they just simply wont work properly when theyre a moving physics object
if you are making a physics based game (like build a boat for treasure) please do not use click detectors, just make your own clickdetector using scripts
Why do we have to put that (plr) in the function? And also what does Part.color = partColor do? For me it makes it so that when I leaveHover it goes back to the normal color
Because whenever the part is clicked, it gives us the player who clicked, which we can then name whatever you want (so i named it plr, but you can literally name it anything).
The goal with part color was to get the parts color before any changes occur, so that we know what its default color was before we changed anything.
i found it odd that a client side action such as user click is supposed to be handled in a server side script, but i guess roblox is roblox
I mean you can handle it in a local script as well lol, Roblox just does the grunt work of sending a message to the server whenever it detects a client click
How to make it so after a certain amount of clicks you want a event or maybe even make the player explode 😊
Just create a variable and add 1 to it with each click, then when the variable is 5 or wherever, run your code
I just found a hidden gem, nice video!
I don't see how it is stupid, like if It actually was a property setting then people would complain why other things such as "Highlight" doesn't exists in property and then again if roblox adds it they will complain more. I like the idea of having a simple non crowded property tab. The fact that you can also do script.Parent.ClickDetector:Destroy() which would be useful in some cases.
I get what you mean, but ClickDetectors just don’t have enough properties to justify being their own instance (MaxActivationDistance could’ve just been a sub-property of a potential “Clickable” property in every part).
It can also be confusing to look for MouseClick inside the ClickDetector and not the part itself. The only explanation which I’ll accept is that, somehow, giving every part the option to be clickable ruins performance
@@byteblox100 I agree, ClickDetectors not having more properties to justify really sucks. But since the only way to make ClickDetectors work is using your scripting skills. Having scripting skills lets you justify those ClickDetectors properties yourself by making them yourself (with script).
Example: when clickDetector Clicked, if click detector is on (Specific team) then (run code)
Otherwise you can make or find a click detector plugin for your viewers or for yourself (if you use click detector a lot in your projects) so it would be easier for them and for you.
I see what you meant in the video now.
How are click detectors stupid? There is a reason they are not just properties of all instances. Firstly, that would be inefficient to add a property that very few parts use created every time an instance is created. But most importantly, how would ClickDetector's events work if it was just a property of instances? Properties can not have events, so a "clickable" property would be completely useless.
Because dragdetectors exist
@@byteblox100 I don't understand? Drag detectors are instances just like click detectors
@@byteblox100 btw I was responding to a reply you posted under another comment:
"I get what you mean, but ClickDetectors just don’t have enough properties to justify being their own instance (MaxActivationDistance could’ve just been a sub-property of a potential “Clickable” property in every part).
It can also be confusing to look for MouseClick inside the ClickDetector and not the part itself. The only explanation which I’ll accept is that, somehow, giving every part the option to be clickable ruins performance"
Honestly I’m fine with it being an instance as long as it has enough properties/events to differ it from just being a property of the part.
Dragdetectors are click detectors + able to drag, as in literally an upgrade (just make RunLocally to true and you just have a click detector which also detects drag)
@@byteblox100 You say you're "fine" with it being an instance, but what else can it be? Like I said, properties can't have events so then you'd lose a lot of functionality that makes click detectors useful.
Okay, but why would you use a drag detector if you only want to act on clicks? Then you're running physics and wasting resources by calculating the physics involved in dragging.
true...
underrated guy idk what else to say so that i dont sound like a bot
yeah man, watch me eventually make a full roblox course lmao
👍 from me keep up the good work
cool video👍