I want that after my IF STATEMENT Is TRUE To make a GUI Element to become visible.
What is the issue?
local function Question_Answer(Answer)
local Input = game.Players.LocalPlayer.PlayerGui.ScreenGui.Screen.Input
local Submit = game.Players.LocalPlayer.PlayerGui.ScreenGui.Screen.Submit
Submit.MouseButton1Click:Connect(function()
local Input_Lower = string.lower(tostring(Input.Text))
if Input_Lower == Answer or Input_Lower:find(Answer) then
game.StarterGui.ScreenGui.Screen.Correct.Visible = true
end
end)
end
Question_Answer('yes')
The code itself looks fine at a glance. I don’t think your issue lies within what you’ve shown. Also you don’t need to use tostring on a value that’s already a string.
Edit:
Actually, looking at it more closely, I wouldn’t recommend putting a click event inside of a function like that. If there’s only one submit button, which there seems to be, this will likely cause conflicts under certain circumstances.
I would recommend writing the function separately and then use it within the click event.
I feel like I’m missing a bit of information though to explain it properly.
The script is probably working as it should. In the troublesome line, you are setting the visibility of something in the starter gui, not in the player gui which is the one actually rendered in the client.
To avoid this kind of confusion, I’d define a variable screen on top of your code (ideally before declaring the function, but that depends on your setup). You should also consider calling WaitForChild instead of directly indexing stuff in the client.
I’d recommend using WaitForChild regardless of whether or not it’s the client. While loading issues are almost guaranteed on the client, it’s also an issue server-side as well. It’s just good practice regardless.
I don’t think always using WaitForChild can be considered good practice though. But I did not mean to say this function should only be used in the client.
About your edited post, that’s a good observation. While OP’s setup might be justifiable, there should definitely be some logic to disconnect the mouse event connection.
my attempt at fixing it before realising the issue:
local Answer= 'yes'
local Submit = game.Players.LocalPlayer.PlayerGui.ScreenGui.Screen.Submit
local function Question_Answer()
local Input = game.Players.LocalPlayer.PlayerGui.ScreenGui.Screen.Input
local Input_Lower = string.lower(tostring(Input.Text))
if Input_Lower == Answer or string.find(Input_Lower, Answer then
game.Players.LocalPlayer.PlayerGui.ScreenGui.Screen.Correct.Visible = true
end
end
Submit.MouseButton1Click:Connect(Question_Answer)
Well to clarify, I mean if it’s something you need to reference on game start. If you know it already exists, you obviously won’t need to use it in that case.
But on game start or cases where you can’t be 100% sure it already exists, I’d still recommend referencing it. If your concern is the slight delay that might occur, you could always just do:
local part = workspace.Part or workspace:WaitForChild('Part')
I replaced this the IF statement definition to print("It Worked!") and as shown in the image the “It Worked” string printed out after I said “Yes” and clicked on the submit button.
This proves that the entire script is working fine except for this line of code- game.StarterGui.ScreenGui.Screen.Correct.Visible = true
