Відео

Aaans full circle, since Unity supports ECS.😁

Unreal Engine uses ECS correct?

i finally have a rudimentary understanding of ECS, thankyou

Saw the thumbnail and thought: "Let me guess, fed up with Unity switched to Godot and likes but doesn't feels quite right and ends up with Bevy" ...guess I nailed it.

Let me guess, less than 100 reviews on Steam/App Stores

such a clean, simple and amazing art! looks futuristic and soo dynamic. I love it! good job!

Fantastic Video but what if you want to create, lets say, 100 abilities. You will have to create each cooldown/active time for each and everyone, right? Is there a workaround for this issue?

How do you make the amazing animations/visuals comparing Unity and bevy’s composition vs inheritance structures?

Why am I watching tutorial videos from a 12 yo? And why am I still learning from that? 😐

You should make it so if your in the water you can only go in the inventory. It'll make the player have to decide what to equipped before you go into battle

I too wanna move to bevy soon

If I want to use a function inherited from the MonoBehaviour class in script DashAblity, do I need to change it to create a variable on the Field to receive a value that is a ScriptableObject?

I miss the days when roguelikes were like Rogue.

Well this is a pain in the butt for a more complex movement system.

is there a way to do it independent ? and also not using [CreateAssetMenu]

commenting for algorithm

hi whats ur vsc theme?

I'm currently using C++ + Raylib & EnTT (an ECS) for my games. This combination makes it extremely easy and enjoyable for me. I will probably try Bevy for a future game as I am already comfortable with Rust, just to make the comparison.

Thanks!

The best way to code games Godot is to use composition, not inheritance.

how about when you add more abilities? with different cooldowns

I don't think the point about "inheritence" is actually true. Sure, if you want to make a component or node that adopts the funcionality of an already existing component/node, then inheritence is an easy way of achieving that. Fundamentally though the principle of composition is expected both in Unity and Godot, they are actually very similar. If we think about what composition is it's really just splitting an overly complex object into multiple smaller ones where each one performs a specific task - so that we can *compose* objects that facilitate that exact behaviour (resources are used to contain data). And so sharing and managing references of the indivudal objects so that the components can communicate is a natural side effect of this pattern. And there are common ways of tackling this- like export variables and prefab/scene management, where you construct a prefabricated object with all of its references set already. The final object should be an in itself functional thing. Now, additional dependencies can exist *outside* that object, but that's another story. I totally understand and respect your choice though, and I gotta say the idea of ECS and systems sounds pretty dope as well and I'm honestly curious to check this out myself one day. All that being said, I wish you best of luck with your game project!

While it's great for inspiration, I will rather analyze and design my requirements. The only thing I see reason for a SO is, that you can set it an Icon - visual representation. Otherwise I see a static class, or an xml for data seems better to me. Now thinking....

Nice video, looking forward to the next devlog!

Two enemy concepts: (similar, but different) A melee enemy that when hurting you, temporarily takes one of your PLAYER shards, gaining those buffs. Will drop shard(s) when killed A ranged enemy that when hurting you,temporarily takes one of your ARROW shards, gaining those buffs. Will drop shard(s) when killed

can we get the neovim dotfiles

when the explody enemy explodes, the screen should shake a little bit to make it feel more impactful

Literally the same path and opinion! Good luck with your game!

amazing. it's cool that more and more people notice rust and use it in their projects. i heard about bevy and it's nice to see that you enjoyed using it

Hope you feel more inspired with a more functional type of programming design pattern! I just recently started playing with phaser, which also follows a ver classical OOP design pattern. Coming from a more functional approach, I prefer OOP for game dev much more though. Happy developing!

Bist du Deutscher?

My main issue with trying Bevy was the lack of UI tooling compared to Godot. I found Godot with GodotExtension e.g. (GdExtension for Rust or SwiftGodot for Swift) to be the best middle-ground (at least for now). The ECS approach is interesting from a performance point of view, but I also hit an issue with not being able to do "joins", e.g. storing the current map ID in the Player component and then joining from that to get the map size, instead I had to work around it with some data duplication in different components.

That's an awesome explanation of how Bevy works!

I looked into bevy a while back but decided it probably wasn’t mature enough when the getting started page said to use rust in godot instead

It's BS to state that you have to work with complex inherritance-structures when working with Unity. Yes: you have to inherrit from MonoBehaviour or ScriptableObject, but thats it. And the only thing you get from that is the connectivity to the game hooks and the ability to used them as an components. And one layer of Inheritance is not "overly-complex". I'd go so far to state that one-level of abstraction is a must, because you should work with interfaces and have a well defines API for your components.

Would you try SDL2 + C++. Mostly because you used C#.

Awesome video .. may I ask what software did u use for those animations? PS: oh motion canvas I see .. most people don't mention this in desc. 😅

rust is crap. you can write a perfectly safe code that rust wouldn't allow to compile. which means rust, just like swift and kotlin is trying you how to think instead of doing what you think for you. if it was in c++ focused, i would've switched to it.

Great video! I highly suggest checking out Tantan's channel as well as a rustacean and bevy game developer

The research part is the most instructive part lol

I'm unsure if you're still open to feedback-shaped thoughts at this point, but in case you are: - The geometric art direction you've been going with gives me some Tron-esque vibes (less Tron Legacy and more old school Tron, but even so) - I wonder if it's worth leaning into that a little during art refinement - kind of a Geometric Technomantic thing vibe. See also Hyper Light Drifter, the Progenitors from Homeworld, the Zeffo from Jedi Fallen Order, Endless Legends.. anything where ancient-become-archeological advanced technology is a prevalent thing and there's wonderful aesthetic to draw from. - In one of your previous devlogs you put a poll up for naming Fragments - one of the names was "Relics" - I wonder if you can/should co-opt the name as a mechanism for another upgrade distinct from Fragments. Fragments increase stats while Relics could unlock Abilities like Grapple, or a radial burst attack: stuff like that. That way it becomes a decision: "Do I want to boost my stats, or do I want to have this tactically useful ability?". It also lets you achieve progression by re-using an existing and familiar inventory mechanic - just slightly differently.

I think you enjoy programming more than you enjoy finishing games. Get it done, get it fun. Don't forget

You should stick with the first one you made.

It's difficult to find the right game engine or framework, I went from Unity, to PICO-8, to LOVE2D, then finally p5.js, all for a simple puzzle game. I agree with you that Unity is just overkill for most indie developers.

I'm migrating to Godot as well. I have 10 years of experience with Unity. I decided to switch after Unity's runtime fee hit us hard. It was the final straw for me. I already had some experience with Godot, making minigames for clients. Here are some tips: First, do not use C# in Godot! It's buggy, it's a hack, and it will be removed in favor of GDnative extensions anyway. Everyone coming from Unity thinks it'll be easy to use C# in Godot then learn GD. It's not! Learning GD is faster than trying to figure out how to do things in C# on Godot. GD is really easy to understand and powerful when you need it. It has some quirks, but it's evolving with every Godot version. Secondly, 'Scenes' and 'Prefabs' don't exist. Everything is a Node, so don't rack your brain trying to load a 'Scene' or 'Prefab'. Just instantiate it as a node anywhere you want.

Good video but saying that Unity forces (or even embraces) you to use inheritance is wrong. Actually Unity pushes you to use *Composition* (you add *components* to a prefab). Highlighting that as a problem and then showing how Godot literally uses *Inheritance* for nodes was weird (Specifying that you wanted to try different engines would have been better instead of this, the points 1 and 2 definitely stand, the editor is quite heavy and the source code is hidden) Regarding the coding structure in Unity, I think that it's mostly because of the tutorials available, most of them show you how to achieve a certain result but don't care about scalability, dependencies and so on. You can definitely make the code not look like a 🕸 if you have a proper achitecture, use patterns like Observable or Messaging to decouple the code, redeuce the scope and visibility of variables and methods, etc

Unity forces you to code in some certain way and use inheritance heavily? Have you ever tried Unreal? :)

I also recently pivoted to bevy... so far its preeeetty nice!

Welcome to the bevy team!