legion
bracket-lib
legion | bracket-lib | |
---|---|---|
13 | 27 | |
1,563 | 1,452 | |
0.0% | 0.8% | |
0.0 | 0.0 | |
over 2 years ago | 3 months ago | |
Rust | Rust | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
legion
-
A short introduction to Entity-Component-System in C++ with EnTT
I know bevy, there is also legion from the amethyst game framework.
-
I learned to love testing game code
Wow... Okay. I see you didn't even bother watching the video in full. But, I'll respond in case your misinformed comment manages to deter people from watching it.
You somehow managed to ignore all the points of the talk. Like literally every one of them, and I'm not even exaggerating. And then you somehow both managed to focused on irrelevant details and to talk out of your ass (like, at least be right about the details?), all to make a tangential point about how "sUpErIoRlY sMaRt CpP dEvs ArE" because they know this really basic shit.
Let's start.
First you talk about "borrow checker issues" she's demonstrating in the OOO design. The point here was to illustrate the amount of coupling and "explosion" in size with this approach. The point was "OOO is probably not a good design paradigm for game dev". Then she continues how Rust surfaces this bad design paradigm much earlier than it would've happened in other languages/ecosystems. That's all.
More, what you call a custom allocator with tombstoning/generations are just things that exist with a lot of ECS implementations (regardless of language), and it's just become "tribal wisdom" at this point that this table-esque storage backend work really well with ECS (I dunno which one came first; older game devs might know more about ECS history/evolution than I do).
Also not sure what you mean by "that can fail in most of the typical ways and that she's gained nothing over the cpp implementation while wasting effort to force Rust into allowing her to do something really basic"... Maybe I misunderstand what you mean, but it sounds to me like you're comparing working with `Option` as being the same failure mode as working with `void`. That's just utterly ludicrous nonsense.
Her ECS implementation is... Well, it was made to fit inside a few slides for a 40-minute talk. So, yeah it's not great; there's plenty of small issues with it, but none of them are with Rust, or with ECS itself... Did you expect a production ready ECS library you can copy off of slides and use them in your next game, lol? If anything, her implementation has too much passing resemblance with what a C++ implementation would look like (which is something she's very familiar with and her starting point) than a Rust one. So, I'm just bewildered why this is the bone you decided to pick.
If you're interested in what a production-ish ECS implementation in Rust looks like, check out Amethyst's Legion or Bevy's ECS. Although, Bevy takes takes ECS a few... staircases (rather than steps) further with its own ECS. I really* encourage everyone to read up on Bevy's ECS and check out the unofficial Bevy cheatsheet book; I'm certain at leat UE game devs will know how to appreciate how beautiful and ergonomic the design is, but others should as well). Aside: her ECS implementation is still safer than most C/C++ implementations used in published games, but that's a bit besides the point since that's the borrow checker doing its job.
Anyway, the irony is that she much better explains the pitfalls of her own implementation details that you do and she also explains why they're "fine" sometimes. And it was kinda implied that it's fine (from what I remember) because it's no worse than what you end up doing in C++ or Java when implementing ECS, but at least it's safe in Rust. She acknowledges that there's probably better ways to do it.
Here's a few links on some of the stuff I mentioned:
- https://github.com/amethyst/legion
- https://bevyengine.org/learn/book/getting-started/ecs/
-
New to Game Dev
Development on Amethyst (the engine) stopped, the Amethyst Foundation is now focusing on developing engine agnostic tools, like Legion and Distill
-
What's the state of Legion ECS development at the end of 2021?
Though, Legion Github was not too active during this year, and with the recent shutdown repurpose of Amethyst Foundation its future looks even less promising.
-
Why can't you have fields as traits in Rust?
Take a look at legion on how to compose data objects in Rust.
-
rust ECS that can register new component types at runtime?
I'm trying to avoid that architecture even though that's the path of least resistance to work with existing ECS libs in rust.This discussion about FFI for legion touches on what I'm trying to accomplish. They use a u32 as a custom type ID to deal with the FFI boundary. The size param would be for each instance of that registered component, so the Vec wouldn't have knowledge of the size of each component (which might be 16 bytes for example). Ideally, components and systems defined in the scripting language are more 'first class' instead of scripts only being invoked by entities with a DynamicComponent. This discussion is very helpful btw, I appreciate your thoughts
-
https://np.reddit.com/r/rust_gamedev/comments/pmvooc/bracketlib_a_few_discussion_items/hckui64/
In the end, I got something to work (also in issue 269):
-
bracket-lib: a few discussion items
I ended up with my own, a bit ugly, code. I'll quote it here, because even deserializing a JSON into Legion components is not 100% trivial task. Someone else filed an issue 268 in Legion, I have filed another one too.
-
Unity patents "Methods and apparatuses to improve [..] an Entity Component System (ECS)"
Bevy was introduced in 2020 and the patent was filed in 2018. I don't think any of the ECS mentioned predate the patent filing (looks like legion introduced this model in 2019), so it's not as derivative as it seems in the current landscape.
-
4MB Jam - You have a month to make a game that fits into 4 Megabytes! (No theme)
I have been working on a game using Rust, SDL2 and Legion. I statically link SDL2, which mean that only the parts that I actually use gets included. Also i have been using the include_bytes to include my assets. This creates a single executable that is around 3mb (this is without compiler optimizing for size, it could go lower at the cost of runtime speed). Running (upx)https://github.com/upx/upx on it, it comes out to about 900kb.
bracket-lib
-
Does anyone care about CLI/TUI games?
I think having to use a terminal is the scary part for many people. rltk/bracket-lib can be used to get a similar look and feel if that's what's important, but it is geared toward roguelikes.
-
Minimal 2D library for games? I'm struggling a bit to settle on one to learn.
Maybe bracket-lib from the amethyst authors? Iām currently working through that book and find the library quite intuitive and simple to use. It started out as a toolkit for rouge-like games but has been getting more general. On that note, I recommend the hands-on-rust book which teaches rust concepts while building games with bracket-lib. As you have read the book, Iām sure you would get through the first chapters quickly.
-
Bevy ECS or custom implementation?
https://github.com/amethyst/bracket-lib has a great integration with Bevy, designed for exactly this sort of thing.
- Turn-based game - architecture feedback/opinons
- libtcod use 8x8 font but scaled up to 16x16?
-
How difficult could it be to make a console program that looks like this and has a game loop running on a separate thread? Any suggestions or crate recommendations are welcome!
I've been doing some experiments with terminal based games and landed on https://github.com/amethyst/bracket-lib It's not exactly terminal based in the sense that it actually runs on OpenGL by default. But that's a plus imho because dealing with the bits of the terminal window that can change outside of your control (like fonts, window resize, etc) is a giant pita. It does let you swap the backend to run on crossterm if that's what you really want to do but if what you're after is the aesthetic like I am having bracket_lib handling all that makes life so much better.
- Rendering TUI To Web
-
Sharing Saturday #420
Bracket-Lib for Bevy Github
-
Sharing Saturday #418
Bracket-Terminal/RLTK for Bevy Github Branch | Twitter | Patreon
-
Sharing Saturday #416
bracket-lib šš» (using this now)
What are some alternatives?
bevy - A refreshingly simple data-driven game engine built in Rust
upx - UPX - the Ultimate Packer for eXecutables
Amethyst - Data-oriented and data-driven game engine written in Rust
roguelike - Turn based dungeon exploration
VTerminal - A new Look-and-Feel (LaF) for Java, which allows for a grid-based display of Unicode characters with custom fore/background colors, font sizes, and pseudo-shaders. Originally designed for developing Roguelike/lite games.
rust-sdl2 - SDL2 bindings for Rust
libtcod - A collection of tools and algorithms for developing traditional roguelikes. Such as field-of-view, pathfinding, and a tile-based terminal emulator.
rust - Rust for the xtensa architecture. Built in targets for the ESP32 and ESP8266
python-tcod - A high-performance Python port of libtcod. Includes the libtcodpy module for backwards compatibility with older projects.
raylib - A simple and easy-to-use library to enjoy videogames programming
bevy_webgl2 - WebGL2 renderer plugin for Bevy game engine