Button.Activated fired on join game?

Help and Feedback Scripting Support
#10

Also, I did. I just edited the topic.

#11

Nice okay, instead of Button.Activated, use Button.MouseButton1Click

#12

Its cross platform… So that would break anything else I’ve set up.

Shouldn’t .Activated run on mouse click, tap, and selected with gamepad? Because my other buttons work.

#13

Can you show a script so I can see

#14 
`local function startLevel(LevelNumber)
	Print("Run!")
end    

script.Parent.Parent.Parent.Parent.Overlay.StoryOverlay.StartGame.Activated:Connect(startLevel(1))`
#15

I take it that it prints ‘Run’ by itself without clicking?

#16

Yes it does, I’m starting to think that it’s an studio bug.

#17

I think you need to check what the input is before printing, I’m testing it now and I’ll send you a script once finished

#18

Why do my other buttons work then… They all work the exact same way. They are ctrl + c, ctrl + v…

#19

I think I found the issue…
Can there be too many ‘.Activated’ in 1 script?

#20

If it’s for the same button it could create issues

#21

Nvm… It worked then didn’t.
I think its a bug.

#22

So, I tested it with another button and it worked. Then I added (StartLevel(1)) – The number and it broke. I think its a bug with the number.

#23 
local function startLevel(inputObject,clickCount,LevelNumber)
	if inputObject.KeyCode == Enum.KeyCode.ButtonX or inputObject.KeyCode == Enum.UserInputType.MouseButton1 or inputObject.KeyCode == Enum.UserInputType.Touch then
		print("Run!")
	end
end    

script.Parent.Activated:Connect(function(inputObject,clickCount)
	startLevel(inputObject,clickCount,1)
end)
#24

Its a bug with ‘:Connect’, There is a problem when you send data through them. Hence the reason my other buttons work.

#25

Actually button activated doesn’t work for me at all

#26

How so?
I seem to have it working pretty well now, just needed to add a few extra steps.

#27

I don’t know, I’m actually getting pretty tired, I hope you find a solution though

#28

Yea… Its a bug. A pretty pesky bug at that.

#29

If I recall correctly, this is normal behavior. Doing something like guiButton.Activated:Connect(doThis()) would automatically call doThis() even if the Activated event did not fire (think of the parentheses after the function name as the function runner/starter). On the other hand, if you do something like guiButton.Activated:Connect(doThis), the doThis function will only be called when the Activated event fires.

Because of this, I don’t think there is a way you can directly pass a custom argument through :Connect(). What you can do, though, is create a variable somewhere inside the script, and then use that as a reference for your function.

Example:

local levelNumber = 1
local function startLevel()
    print(levelNumber)
end

guiButton.Activated:Connect(levelNumber)

Another alternative is to use an anonymous function. This way, you don’t need to use a variable as mentioned above.

Example:

local function startLevel(levelNumber)
    print(levelNumber)
end

guiButton.Activated:Connect(function()
    startLevel(yourArgumentHere)
end)
2 Likes