Godot 4 Pause Menu Tutorial 

Believe it or not, you just alleviated an hour of headaches with this one comment. For anyone else who needs clarification, the top-level node has to be a CanvasLayer, with the Control node as a parent of it. Not the other way around, like I managed to do.

Pinning

@@DavidRycan bro i dont get it :(

@@Yaya-toure-A Put static overlay UI Control nodes (PauseMenu node in this video) into a CanvasLayer parent, not as a child of the Camera2D. Or just change the type of the root node of your PauseMenu to CanvasLayer. That way, when you insert it into another scene (e.g., "main" in this video), it will render on top of everything else and disregard the camera's transformation.

This is the correct answer.

This helped out tons, thanks!!

I was confused in your example for a sec why true and false were seemingly swapped around, before realizing they're not! Huge mistake on my part, but for anyone else who gets confused, like I did, in the original script in the video, the 1 and 0 are for the timescale, and the're more like if the game time is moving or not. So in the video, a timescale of 0 means the game isn't moving, whereas in this example, if the game is in a paused state, you'd say the paused state is true (which can also be represented as 1) in programming, typically 0 is false, and 1 is true. so in my mind, I was confused why the numbers got flipped. This was very unintuitive to me until I worked it out logically. so to recap, in the video, they're setting the time scale (essentially the speed the game is moving at) to on or off (moving or not moving; paused or unpaused) which is why it uses a timescale of 0 or 1 (off or on) in this example, you're using an inbuilt pause variable, so it seems flipped, but it's really not; the question is changing from "should the game be moving" to "should the game be paused", which sound the same, but would have flipped answers to mean the same thing. if the game is NOT moving, then it IS paused. sorry for rambling, just wanted to share in case anyone else was confused.

thank you for the advice!! is there a way to make it so that you can still use the escape key to unpause, whilst still not being able to accept other keyboard inputs?

​@@chloe.v took me a minute to figure this out too. You have to set the process for the pause menu to "always" (so it can still read inputs when the game is paused) and it can't have any parents upstream that conflict with that. so for example, if you put your pause menu as a child of the player, that wouldn't work, because you want the player to pause when the menu opens, and the pause menu won't work if it's a child of a pausable entitiy and also needs to be able to read inputs when paused. my solution is to either put the pause menu as a child of the level, have the (root) set to always in the process tab, and then have a child of the level that's called "pausable" that everything that should be able to be paused gets child-ed to. then I came up with a better solution: make a new parent for the player entity, and set the pause menu and player as children of it. then set that parent to always and the player process set to pausable. The biggest thing to remember is just that anything upstream of the pause menu in the parenting tree can't be pausable, or it'll break the pause menu's ability to unpause (seeing as it'll be paused and then can't take inputs 😵‍💫)

Ya that one took me a bit, I had to find 2 shaders from both godot 4 and godot 3, then combine them together. Since, neither worked

@@Gwizz1027 I feel you. At least no one else will have to go through those steps for such a basic shader :)

@@theyellowarchitect4504 Ill have to find somewhere to post it

oooo I like this one

By a long shot! Scales better!

You can obtain the root node using get_node("/root/NameOfYourRootNode")

Yes, there are a few options: - Use @export annotation instead, and drag'n'drop the relevant node into it. - Use an absolute path instead (e.g. $"/root/MyMainScene/MyPauseMenu"). - Use a global event bus, i.e. a signal in an autoload script, which will be emitted when you click the button from wherever your code handles input, and connected to a function that toggles the pause menu's visiblity.

On your pause menu node, go to Inspector > Ordering > and change the Z Index to a number higher than the Ordering on your player node. Consider this as a Z axis where anything > 0 is approaching you and anything < 0 is going further away from you

stop taking movements from the controller

@@Gwizz1027 Seriously? I would hope the char stopped as well...

Hide the menu

Try self.visible = true when pausing and self.visible = false when unpausing

You dont need to reference self in a node, if it is the self, it's kind of redundant. You can also use hide and show.

It didn't like me just using show()/hide() or getting rid of self (it said those functions/identifiers weren't declared in the current scope). Maybe it's because the root of my pause menu is a canvas layer instead of a node? Or might be because I made my pause_menu.tscn an autoload so I don't have to put in in every scene? Don't know lol, but self.visible seems to work for me

Found my issue lol, when I changed the root to a canvas layer I had forgotten to also change extends Node to extends CanvasLayer, so now show()/hide() work as expected

its an exclamation point i believe

Make sure input checking for your “pause” key input is still happening when the “paused” state is active in your game

I'm having the same problem

You probably aren't using the canvas layer

I had the same issue when my background was not evenly filled (ie the background had empty spaces between the texture I wanted to blur). Putting another ColorRect behind with full black solved.. hope that helps you too!

In the material section of the color rect you have added shader there should be an option called shader parameters click on it and set value of 3 if you have missed it if this didn't help maybe redo the tutorial, my problem was same 😊😊😊😊

Nope! It can be anywhere

@@Gwizz1027 oh good! thanks for replying

Are you using Input.MOUSE_MODE_CAPTURED? If yes, here's what a did: In process Delta when you press pause button you set mouse mode to visible Down in the Delta func u write If not paused Paused = false. It works but quite weird.

Hold ctrl + drag

Ya that shouldn't be a problem

@@Gwizz1027 I am adding it to the camera but it doesn't work it shows it at the start X and Y axis

@@thesomeone2nd do a CanvasLayer instead and lock it to the screen boundary you want, so if it's in the center screen, lock it to that and boom.

@@OnBrandRP what is screen boundary and how do you lock it there

since, the opposite of true is false, and the opposite of false is true, so I can toggle the "paused" variable in 1 neat line

@@Gwizz1027 I might be wrong, but I think he talked about the fact that if paused == true, the game is not paused? Since time_scale is 1 if paused.

@@Snikur its reverse since we are setting the paused variable after

I suppose I could've put it before hand, then it would be more intuitive.

@@Snikur Paused is set to False, so when the function tries to call "paused:" it's reading the variable as false and thus it is hiding the pause menu.

And I love you random citizen!

why not do that lol