wish it was Rust

@@climatechangedoesntbargain9140 rust has too many features that can obsturct the original concept

@@ishdx9374 explain that

@@climatechangedoesntbargain9140 the point of an ECS is to have a low-level control of your memory, rust while allows that, it's unpractical, because of the friction it imposes (yes I already programmed in rust for around a year)

@@ishdx9374 explain how it is unpractical in this context

Glad I could help

Hah, and then you go on to find a memory leak in my code :D I hope you learned something from this video, the system does have limitations which other commenters have pointed out

I'm glad it helped!

Me to bro

Glad you enjoy it! More to come!

Thank you!

You're welcome 🤗

Why thank you very much, I'm glad you found it useful :)

Glad it was helpful!

Generally with these types of systems "types" are just a combination of unique component sets. However, as you said, you may want more types of flags without making separate components, like IS_ON_FIRE, IS_FROZEN, etc. In that case you could end up with a bunch of if statements or you could use something like a state machine.

Good idea

I'm not actually using an ECS in the game I'm working on, but I see the issue. If one day you decide that component C is not necessary anymore, but you still register A, B, D, then they will be misaligned. You could just continue to register C until you need another kind of component later on. Not the most appealing solution, but should work okay. Is there another reason you may want to change the registration order?

@@DylanFalconer Thx for the reply. I understand that, if you know the internals of your own engine well, this is not really a big issue, as you can just take this small inconvenience into account. I was mostly thinking from the perspective of other people using your ECS. I actually found a pretty nice solution online, where you keep track inside your systems, which entities and components are relevant for that system, not the other way around, where the entity keeps track of that. This way, the order of the components or systems is not important anymore :) Again, great video, and thanks for the reply :)

I haven't thought about this problem in a long time, but my first approach would be to benchmark and if it's actually an issue then look into caching results.

No reason you couldn't have multiple bit fields to handle additional component types.

@@cipherpunk7409 i ended up using sparse sets after reading the article "ecs back and forth" by the creator of entt which solves this problem. But yes multiple bitfields could do however I'm not sure how nicely it would scale if you had, say 200 or more components which is not an unrealistic number especially if your game engine itself uses ecs internally as well as for gameplay programming.

@@phee3D Nice solution. I've definitely heard of people doing the multiple bit field solution for 200+ components without performance issues. But it definitely depends on what you're making. Glad you found your path forward!

Similar, github.com/Immediate-Mode-UI/Nuklear

ECS is mostly useful for engine makers rather than game-makers. If you know the types of entities you want to have in your game then you can design a straightforward system for your game with that information. If your game design is fluid and/or experimental then you may benefit from ECS's flexibility.

@@DylanFalconer alright thanks

Cheers! For this one I actually just used images and OBS's "image slide show" option.

@@DylanFalconer oh that's cool thanks

Indeed you can do that, it really depends what kind of functionality you want for your tiles. If your tiles can perform actions then it's something to consider for sure. For pure aesthetics, probably not. Minecraft has a type of split system where most solid blocks are just Blocks but more complex things like pistons and furnaces are TileEntities.

The downside of mixing tiles with regular entities is that tile position components will be mixed with entity position components. This could be bad if you have a huge number of tiles and you want to for example do collision checking between the entities, because at least in this video's implementation you'd also loop over every tile while just looking for entity position components. A more efficient and complex implementation should totally sidestep this issue. And the other issue with this video's implementation is of course that adding more components makes things slightly slower. Look up enTT on The Cherno's channel for a showcase of such an efficient implementation.

That's a shame, why is that?

Can you explain why it's bad? I bet you can't