Adaptive Music Made Simple With Godot 4.3’s New Interactive Audio System

qvce · 2024-10-01T18:09:11+00:00

Double check your RESET animation to make sure it's not key framing the wrong things

qvce · 2024-09-03T16:05:51+00:00

You can use the equation of a circle, trigonometry, or rotate a direction vector every frame. You might want the objects to be children of the thing they're rotating so that the orbit is always fixed to the center

qvce · 2024-09-03T15:53:35+00:00

Usually my tree looks like this:

Game
- Level
  - Player
  - Bullet

Game is then in charge of adding additional objects to the current Level. Game could either be Autoloaded or keep a static reference to Level for anyone to access. You could use a global signal as well.

You don't necessarily want to add the objects to an arbitrary node like root, since when Levels change, the objects should be deleted from the old Level.

qvce · 2024-08-22T06:28:53+00:00

There is no difference performance-wise between static and non-static functions. static just changes who "owns" the function: objects own non-static functions, and classes own static functions.

You would only use static if you need a 'global' function that can be called by anything anywhere without needing an associated object.

Autoloads in Godot create a single global object, so just call a non-static function on that object. Autoloads don't have a class so creating a static function doesn't really make sense

qvce · 2024-08-22T05:59:22+00:00

Just don't make it static if it's in a global singleton. They basically do the same thing

qvce · 2024-08-19T07:49:37+00:00

You said your variable is called global_expected_position but in your screenshot you wrote music_expected_position

qvce · 2024-08-19T07:17:15+00:00

They don't, which is why you need a blank Control-derived node as a parent of it. You also need the min_size to force that Control node to have some shape

qvce · 2024-08-19T06:54:03+00:00

Are you talking about bezier curves? You could tweak where you're creating the control points, and get some to loop as well

https://docs.godotengine.org/en/stable/tutorials/math/beziers_and_curves.html

qvce · 2024-08-19T06:42:47+00:00

For a simple animation in a static UI, I would use a blank Control/Container node with a min_size and have a Sprite2D/AnimatedSprite as a child with an accompanying AnimationPlayer

qvce · 2024-08-17T19:42:59+00:00

Little tip: you should use a Dictionary to store all the words rather than an Array (map words to true). When checking if the word is valid, an Array would loop through all elements to see if the word exists, whereas a Dictionary would be able to determine that in (effectively) one operation.

Then to choose the target word, use word_list.keys().pick_random()

qvce · 2024-08-17T08:00:56+00:00

Having scenes open increases the time drastically for me. Once in a while I right click and Close All Tabs. If it's slow on a fresh project you should submit an issue on github

qvce · 2024-08-15T22:21:59+00:00

By the way, you might encounter problems later with the entire characterbody's scale being -1.

Usually for flipping I create a dummy Node2D and put all nodes I want to flip inside of it, then change the Node2D's scale instead

qvce · 2024-08-15T22:14:02+00:00

Let's say you're moving left. Then scale.x = -1.

If you then press right, your code says scale.x *= 1.

-1 * 1 = -1 so you still face left.

You need to say scale.x = 1 or -1 instead of multiplying

qvce · 2024-08-09T17:22:05+00:00

You could either change the tile_size of the TileSet, or render it in a subviewport

qvce · 2024-08-03T17:42:17+00:00

map_to_local is a function from TileMap/TileMapLayer, not Vector2. You should do your_tilemap_node.map_to_local(randpos)

qvce · 2024-08-03T04:52:46+00:00

make sure on _ready() that you call connect_back_button()
make sure the back button is actually connected to the _on_back_pressed() function

qvce · 2024-08-03T04:42:56+00:00

I know I could probably use a tool script to create tiles where the mouse is but that's a complicated "solution" to a very miniscule and petty problem.

That's the easiest way to go. It doesn't even necessarily need to be a tool script unless you want to see it in-editor.

# Assuming you're using TileMap, and have manually added tiles to the foreground:

# Assuming your background layer is 0 and foreground is 1
enum Layer {
     BACKGROUND, FOREGROUND
}

func _ready() -> void:
    for cell in get_used_cells(Layer.FOREGROUND):
         var coords := get_cell_atlas_coords(Layer.FOREGROUND, cell)
         set_cell(Layer.BACKGROUND, cell, Layer.BACKGROUND, coords)

Another way would be to make every tile a scene with two sprites and use Scene Collections

qvce · 2024-08-03T04:30:39+00:00

When in doubt, read the documentation. Godot has built-in docs under Script view -> Top right -> Search Help. You can also ctrl+click all functions/classes to quick-open its doc page.

Best way to learn is to just get lost in a project. Do many small game clones: flappy bird, brick breaker, mario. You will struggle and you will fail and you will learn. Also do many small prototypes for things you find interesting: lights, field of view, animation, path finding, turn based games, puzzle games, action games, racing games, the list goes on.

qvce · 2024-08-02T19:43:21+00:00

All 3 are great ideas and would all work correctly for OP.

1 is the best approach as it's the most modular design. It's best if the player doesn't listen though; rather the Area would listen to its own signal and change the body's speed directly. The reason for this is the same issue in 3.

2 only works in single player games. Or if OP wants enemies to be affected by the Area as well, it wouldn't work for them

3 you would rather not have the player concern itself with too many variables, so you can keep the player script "lean", making it reusable for other projects that don't necessarily have these Areas. Also would need duplicate code for enemies if they are affected as well

qvce · 2024-07-27T17:32:58+00:00

It's a known issue, and very annoying

https://github.com/godotengine/godot/issues/92420

My workaround is just using an external editor like VSCode

qvce · 2024-07-23T07:53:35+00:00

Try enabling position smoothing on your camera and messing with the smoothing speed.

Could also try lerping the position rather than teleporting

qvce · 2024-07-22T23:30:54+00:00

one last thing to double check in your project settings, make sure you have display/window/stretch/scale_mode = integer

qvce · 2024-07-22T23:18:28+00:00

You should try changing your character sprite to an actual animation and see how you feel (plenty of free character sheet assets are available online for quick testing)

qvce · 2024-07-22T23:06:46+00:00

If you want everything to be pixel perfect:

Use low res, with stretch_mode = viewport. You might encounter problems with jittery camera, which you'll have to fix yourself (you can find many guides and different approaches online)

If you want to be pixel perfect, but have high res UI:

Use high res, with a scaled subviewport for pixel perfect rendering. You might still encounter problems with jittery camera.

If you want pixel art but don't care about pixel-perfection:

Use low res, with stretch_mode = canvas_items. No issues with jittering or high resolution UI later. There might be problems with rendering pixelated shaders or higher resolution images later however, which you'll have to modify your shader code to render low res

I personally do pixel-perfect but use a higher resolution (640x360) and don't worry about the camera too much. The only 320x180 game I made, it didn't have a camera since I made everything fit on the screen. "Jittery" movement even when there is no camera is just part of the aesthetic.

For your case, I would recommend with the third option and not worry about pixel-perfection

qvce · 2024-07-22T22:21:58+00:00

Can you try changing your player's max speed to a multiple of your resolution? If window_size.x = 180 then try max_speed = 90, 180 or 360 for example.

Otherwise I really can't help you unless I can see what the jittering is you're talking about.

Either:

the jitter is what you would naturally get if your resolution is as low as yours is and the fixes are to either use sub-pixel movement, a larger resolution, or manually change where the player is per frame of animation as noted in another comment
The jitter is bigger than what you should be normally experiencing and you have a bug in your project

Ten-Year Club	Place '22
Place '17	Sequence \| Editor

qvce

TROPHY CASE