Scripting Helpers is winding down operations and is now read-only. More info→
Log in to vote
1
Trouble with causing something to happen when value changes? [SOLVED]
So, I'm trying to make it so that when the value of this IntValue changes, a script becomes enabled. When the value changes, the script is still disabled. I can't seem to figure out the problem and want to see if anyone can find a solution. (lstats is leaderstats, but I just changed the name)
01 | game.Players.PlayerAdded:Connect(function(player) |
02 | repeat wait() until player.Character |
03 |
04 | local element = script.Parent.Parent.lstats.Element |
05 |
06 | element.Changed:Connect(function() |
07 | if element.Value == 1 then |
08 | player.PlayerGui.Element.Disabled = false |
09 | end |
10 | if element.Value == 2 then |
11 | player.PlayerGui.Element2.Disabled = false |
12 | end |
13 | if element.Value == 3 then |
14 | player.PlayerGui.Element3.Disabled = false |
15 | end |
View all 25 lines...
0
I'm confused, is this script located on the client or the server? User#9949 0 — 6y
0
client Conquesias 85 — 6y
0
Can you explain what each script does and the difference between them (or if they are the same), and also what exactly this is for. mattscy 3725 — 6y
0
I don't quite understand what you mean by the first part of your question, but the script here is meant to take the Value from the IntValue called "Element". I made another script to of course make the IntValue and the Value of it is from 1-6. If the value equals one of those numbers, a certain script gets enabled. Example: If it equals 1, the script titled Element1 which is in PlayerGui gets Conquesias 85 — 6y
View all comments (4 more)
0
enabled. Conquesias 85 — 6y
0
Are all the element scripts the same? mattscy 3725 — 6y
0
Almost Conquesias 85 — 6y
0
The only thing that changes is the thing they set off Conquesias 85 — 6y
1 answer
Log in to vote
0
I fixed the issue myself. I first changed this over to a server script and then there was also an issue with my other script that made the value. It set it automatically as a number 1 through 6, but I was using the Changed event. To fix this, in my other script, I put a wait(1) and then changed the value. (the wait isn't necessary though.)