Does the Enabled property of a tool do anything? When I toggle it, it seems to make no difference in whether the tool can be used (equipped, activated, etc) or not.
1 Like
Did some quick testing, and it seems a bit wonky from time to time however…
Basically depending on the script you have attached to the tool, it can be scripted to decide whether or not you’re allowed to use it (swing a sword, fire a gun, etc). You can still take the tool out, but you cannot “use” it.
The best example to test what it does would be the LinkedSword. It’s how I took a quick gander.
2 Likes
Okay, so it sounds like that the Enabled property does nothing by default, but functionality can be added via scripts.
1 Like
“Description: Relates to whether or not the tool can be used.”
Thats what the documentation says
If a tool is not Enabled, then the .Activated event of a tool cannot be fired.
If you’re not using the .Activated event and instead using something like InputService to detect user input, then the Enabled property is ignored.
2 Likes
I have the same problem; I am not using input service, yet toggling the .enabled property seems to do absolutely nothing. help?
2 Likes
Tool.Enabled toggles if Tool.Activated fires or not.
If you want Tool.Equipped to not fire, you can try setting Tool.RequireHandle to true and renaming the handle to something else or removing it completely.
1 Like
I gave up on fumbling around with it and included tool.Enabled on an if statement when activated fires.
1 Like