#beginner coding

Paste the above code into your bio, replacing the link section with the full link and the text section with your desired text. Be sure not to leave a space when copying over.  

If it's breaking, or you're lost, check this post here.

Recap: I was instantiating scenes and needing to connect signals in C#. In Godot. With minimal code understanding. The search for info is in this other post. (It's late in Aus and I'm tired so excuse formatting pls)

okay, so the way that I found worked was:

(21) get the node from the instantiated scene that has the signal.

(22) type that node, then the signal type, then connect it with += to a method. (the method is out of view, just trust me)

(If you're looking at the rest of the code above in confusion:

lines 6-7 are scenes I want to bring in. Can't bring them if I don't say their names like 3 times in the script istg.

lines 8-11 are filepaths that I'll be changing a lot, so want to only have to change them in one place.

lines 16-18 are how I added the start menu to my main scene.)

ANYWAY, SIGNALS.

Here's the code a little highlighted for you, with some information about where I referenced it. startmenu is the variable I made that is the copy if the scene tree you see below. The PackedScene, if you will. Note: C# uses PascalCase for signals, so whatever Signal you want, remove any "_" and capitalise the 1st letter of each word. I did some examples in the image, also Pressed is used. There might be an extension of Godot that translates the Signal list for us, that would be great.

+= is how you connect a signal to a method. In this case, it means that whenever the NewGame button gets pressed, the NewGamePressed method will activate. (but you can call the method anything. it doesn't have to make sense)

var NewGameButton = startmenu.GetNode<Button>(NewGameButtonFilePath); NewGameButton.Pressed += NewGamePressed;

If you get into making custom signals, you will want to know more about -= which disconnects things, because they wont magically disconnect like normal signals do. Sounds gross and I don't want to get into that until I have to.

It took me a while to figure these out because from the get-go I was working with an instantiated scene (or a PackedScene). Basically, I couldn't use the handy-dandy UI method of connecting signals. And wow is the information spread out.

Page C# signals talks about timers and the important += and -= Operators. I had no experience with timers so this was gobbledygook

Further down the page, it gets into making custom ones, which-

I'm not ready for that either BUT it has an important element that I noticed

This wasn't starting to make sense yet, but it's got some surprise breadcrumbs that will help us later.

Subjectively speaking, as a newbie, I found C# API differences to GDScript useless. [Signal]? delegate void? I had no frame of reference for these. It doesn't deserve a screenshot, you can go investigate if you like.

I finally found the answer (for me) in Button.

This was the answer to my Agnostic Prayers. This is what made it click.

but also who calls a variable 'button'. c'mon bud.

Signals in C# are different and weird and trying to make them talk across scenes is causing me a headache. I'm in Main Tree. I Instantiate the startmenu. In the start menu is the button NewGame. I want to get the signal of that button being pressed so I can drop startmenu and pick up another scene.

I know line 23 is wrong, I'm just not sure how to make it right.