i suggest to conenct signals in code not in the UI.. it gets hairy real fast when using UI.
just in the ready() function you connect them to your methods/functions.
func _ready():
var timer = get_node("Timer")
timer.timeout.connect(_on_timer_timeout)in your case as it is build in signal you just use that built in signal name
func _ready():
button_down.connect(_on_timer_timeout)
func _on_timer_timeout():
passDaveTheCoder I tried to do a minimal reproduction, just coped and pasted the scene file into another project and the button started to work?
In at least one case, I've fixed a problem like that by disconnecting and reconnecting a signal.
Or you could try kuligs2's suggestion of connecting the signals in code rather than using the Inspector. I normally connect signals that way.
DaveTheCoder I tried disconnecting them and doing it in code instead and even completely deleting and remaking the scene but I'm still having the same issue.
EDIT: Just found out that if I switch the positions of the buttons in the scene tree only the button on top in the tree works. Why does this happen?
Camp pause screen scene
Are you pausing the game as described here?
https://docs.godotengine.org/en/4.4/tutorials/scripting/pausing_games.html
If so, are you setting the Process Mode correctly for the nodes that you want to be active when the game is paused?
In addition, this is often useful to debug non-working controls:
bottom panel / Debugging / Misc / Clicked Control
DaveTheCoder Yes, the pause screen node is set as "always" and all its children are set as "inherit".
What about Debugging / Misc / Clicked Control? Does that behave differently for the two buttons?
IDK man, i recreated this based on your posts and image.. it work on my 4.3 stable
I even connected the signals through UI
I didnt change any process properties.. all default values.. i just played around with anchors and expand things.. the label doesnt want to show up (always under the button) when its not expanded.. idk why..
DaveTheCoder Yes, when I click the bottom button it shows that the button was clicked but when I click the top button it says that the VBoxContainer that the buttons are in was clicked.
You said earlier that if you switch the positions of the buttons in the scene tree, only the first one works. Is that still true, using Debugging / Misc / Clicked Control?
You might try adding a third button, and see which of the three buttons' clicks is detected. You don't need to add code, just use Debugging / Misc / Clicked Control.
Also look at the controls in the 2D view, and ensure that it looks reasonable.
DaveTheCoder In clicked control, it says that the VBoxContainer was clicked when you click on the top button, no matter what order they are in, and when I add a third button the same thing happens for all three of them.
Camp when I add a third button the same thing happens for all three of them.
With three buttons, none of them work, but with two buttons, only the bottom one works?
DaveTheCoder I found out the issue. The VboxContainer that was coming up in clicked control was in the UI of the game, not in the pause screen. I fixed the issue by making it smaller.
Camp it says that the VBoxContainer that the buttons are in was clicked
So that was a lie? 
DaveTheCoder yea, I didn't really read the whole node path, I just read the end and assumed, which was dumb on my part.
