Video

nvm that wasn't hard to figure out!

Nice! Great job!

Hi @markushe73! Not particularly, and I still have quite a large backlog of C# videos for me to get through. I have recently been using GDScript a bit more as I have been prototyping features. Its definitely a great language for getting functionality fast. C# though is a critical part of development in Godot! I have shifted the video list around due to how videos perform or from requests I get from people, but I've never taken videos off my list. So more C# content is coming! Thank you!

You go to Editor -> Manage Editor Features. Then you create a profile and you can uncheck all the stuff you don't want to use!

@@DeadIndGames That sounds like a cool feature, I'll be trying it out later. Thank you

Yeah, I was thinking that the moment he put in the variables for player and enemy. Like, the moment you want a different enemy you're going to have some kind of handling that negates even having that variable in the first place.

It creates an instance in a variable, which means it can be seeded (calling the functions directly cant), and probablky more.

@tryoxiss is completely correct! While you don't have to declare the rng variable above, it does give you greater control of the randomization, should you wish to utilize those extended features.

Hi @Sudoweeb, I would declare multiple enemy packed scene variables and assign my different enemy scenes to them. You could then have another randomly generated number which evaluates over either a if/elif/else or match statement to then generate one of the enemy types in a randomized manner. Thanks for the question!

@@TundraFeedandSupplyCo Thanks, could you do a video on resources by any chance? i couldn't get my head to wrap around it.

I'll add that to the list! Thank you!

Would you be so kind as to tell the differences between the two? 😊

@@agriasoaks6721 level manager scope is to manage a level, and it can be re-used to manage different levels in different ways, like spawning enemies or items of that level here and there. Game manager is to manage elements globally, like the player's health, save/load game, load and move to a different level.

@@agriasoaks6721 a level manager handles things for each level, like this video shows. a game manager would have more global features, like handling save data and switching to different levels.

@@jayman1462 you mean level manager handles level swtiching. why would the game manager handle that.

@@opa8012 no, because a level manager is local to the level. it *could* switch scenes, but for transferring data, you would need something that stays when you change levels, hence a global game manager

Hi DasLenny! Thanks for the question! I think this depends on your game and how you want to design it. Generally speaking, I would create a "Manager" for each distinct group of behaviors I would find in a game. For instance, an UpgradeManager, an InventoryManager, an EnemyManager, etc. These would ultimately be orchestrated by the GameManager which exists as the background entity enforcing rules upon the game. While the game manager isn't the enemy AI, for example, it may monitor when the enemy's health drops below 0, and then deletes the enemy from the game (or tells the EnemyManager to remove the enemy from the game). In this way, the game manager is like a referee in a sport. A GameManager could be specific to a level, or abstracted out further. For instance if I were designing a game like the modern XCOM games, I would have a distinct GameManager for the battles, and one for the overworld/base. For something like Skyrim, you may just have a single large GameManager that controls smaller game managers, like a dungeon manager, when the player interacts with them. Does that answer your question?

Hi @alexxander7289 - I don't have a video up for that yet, but I'll get right on that and try to post a tutorial for it this coming Monday (06/03/24)!

If you click on the FireworksParticle node, there should be a set of Direction properties under CPUParticle2D in the Inspector tab. You may also need to reduce/remove the gravity and set an initial velocity in order to see the direction changes.

@@TundraFeedandSupplyCo Oh, nice! I was using GPUParticles2D, but I guess it lost the Direction properties, but they can still be found on CPUParticles2D as you said. Then I was finally able to replicate the effect I had before. Thank you!

Thanks a ton, @Petergams!

Thank you for watching! Yes, you absolutely could use _physics_process in place of _process. Good idea!

The CollisionShape2D node allows us to define the boundaries of a node, however it does not give us access to the same signals that are available on the Area2D node. Giving the Area2D a collision shape allows us to build on the functionality of the Area2D node with whatever boundaries we define with the CollisionShape2D node. The initial CollisionShape2D node assigned to the enemy and the player are used in this instance to stop the player and enemy from moving through each other. While those same collisions shapes could be used as a hitbox of sorts (though a CharacterBody2D needs a CollisionsShape2D and an Area2D needs also needs ones and I don't believe they can share child CollisionsShape2D nodes), there are instances where you may not want the sprite of an object to exactly match the hitbox. This also separates our behaviors into distinct, reusable components, following the "S" of SOLID principals (the Single-Responsibility principal). The hitbox node could be placed on any node, and immediately give hitbox related functionality.

Hi @alexxander7289! There are a bunch of different ways to do this. Pseudo coding an idea for how to implement this, I would likely: Create a "capacity" variable: @export var capacity = 5 I would then create a variable to track how many shots the player has taken: var shotsRemaining = capacity Then a reloading variable: var reloading = false Inside our if(Input.is_action_just_pressed("attack") condition, we would need to decrement the shotsRemaining every time the player shot, potentially as the last step of the if statement as its placement will change the behavior: shotsRemaining -= 1 I would wrap all the logic for creating a projectile in an if statement checking if shotsRemaining >= 0 I would also add an if statement checking for shotsRemaining and starting a "reload" timer if applicable: if((shotsRemaining < 1) && (reloading == false): reloading = true $ReloadTimer.start() ReloadTimer would just be a Timer node attached to the player. In our ReloadTimer.timeout function in the player script, I would then reset shotsRemaining and reloading: reloading = false shotRemaining = capacity Let me know if that helps!

Thank you! Apologies for the audio being quiet! I used to be too loud and it looks like I over corrected, haha.

Hi @pukagol, one way you can do this is, on the CPUParticles2D node, in the Inspector, under Drawing, there should be a Texture property. There are a lot of different options if you click the dropdown, though one simple way you can draw a circle for the particles is to drag and drop a sprite of a circle onto the Texture property dropdown. Depending on the color of the sprite, the hue and color variations might look different to the particles created in the video, though you should still get a range of colors. Let me know if that doesn't work!

@@TundraFeedandSupplyCo Thanks a lot !

Sorry about that! I over corrected when setting up a new mic. I'll make sure to fix it going forward. Thank you for the feedback and for watching!

Thank you, @kevinrabbe5066!

Thank you very much!

Great points! In this video, I was mainly looking to highlight different implementations for camera smoothing, that it could easily be done both through the built-in functionality or through code.

Thank you! I'm looking to discuss more UI styles / features in the future. I'd like to try and make command-line style menus for a future project, so we'll see how that goes!

Please do I'll be waiting for it.​@@TundraFeedandSupplyCo

Hey @Mr.TummyOfClanTummy! This should work for you: extends CharacterBody2D var speed = 400 func _physics_process(delta): look_at(get_global_mouse_position()) var move_forward = Input.get_axis("down", "up") var move_sideways = Input.get_axis("left", "right") velocity = ((transform.x * move_forward) + (transform.y * move_sideways)) * speed move_and_slide() The parentheses are important due to PEMDAS, haha. If you remove the outer parentheses, only move_sideways would be multiplied by speed, so that can cause some unexpected behavior. Let me know if this is not the behavior you were looking for. Hope this helps!

@@TundraFeedandSupplyCo Huge thank you!!!

Hi @smellfungus2801, thank you! That's a great idea. I will add those to my list to see if I can make a tutorial for those style of games.

Thank you very much, cradledani!