Celeste VS specs

Aha, found it! They opened sourced the C# version https://github.com/NoelFB/Celeste/tree/master/Source/PICO-8

forget TDD when you make a game, you want fast iteration time at all cost, gameplay is king, if you can't nail it fast enough, you'll make a bad game that is not fun

it's all about the feeling

Celeste's player class: https://github.com/NoelFB/Celeste/blob/master/Source/Player/...

https://store.steampowered.com/app/504230/Celeste/

check this out! both the readme and maddy's article that's linked towards the bottom, as well as the player.cs source code that is included. might be some decent resources

Keep in mind, the Celeste player controller is one single file of 5400+ lines of code.

So Celeste devs are shit at planning and have very poor code https://github.com/NoelFB/Celeste/blob/master/Source/Player/Player.cs

Celeste's source code is available in github :D https://github.com/NoelFB/Celeste It's a LOT of code, but some stuff in there helped me out creating momentum mechanics for a project recently.

Look at Celeste's Player.cs. Incredible games can (and often do) ship with messy code. Also read the readme where they discuss how they both agree and disagrees with criticism their massive file's received (look up the thread in this sub for a lot of it).

They dropped the controller script for Celeste. 5400 lines of tuning and refining to get everything right. https://github.com/NoelFB/Celeste

There's actually a README now, that does say it's probably messier than it should be and includes more cutscene logic than it should.

The question arises from seeing a plethora of projects using ECS: hecs , Bevy , specs, legion

Instead, I'm using now the specs Library. It's a pure ECS library and much less powerful, without any visualization capabilities, but its works for me :)

writing an ECS is defined a challenging project, no matter the language or if you're a beginner. although it is entirely possible to write one in Rust, check out specs and bevy_ecs for examples.

specs

The official 3d rendering client uses a custom engine called Voxygen. They use Specs for logic.

Rust has a delightful ECS library, specs, that I absolutely love. It has safe multi-threaded execution built right in, which is fantastic for the pretty parallelizable work I was doing. Concurrency in C++ is nasty business on the best of days, and I've run into so many nasty bugs with the custom system I've had to build out to fit the web's weird threading model.

Man, this Specs [0] library is so strange to me, coming from a Unity background. Is there some sort of comparison as to why one way is better than the other?

[0] https://specs.amethyst.rs/

Hi everyone - I just picked up one of my long-unfinished side project built with Rust and would like to show it to you here. It's a clone of the famous(?) Winterbells game. It's written entirely in Rust and uses OpenGL and an entity-component-system architecture ([the `specs` crate](https://crates.io/crates/specs)) (still learning), no game engine.

Wait did the person at your company write specs or something else because they weren't pleased with it? I don't know much about amethyst and vaguely know about entity component systems but I watched a talk on someone making a game with amethyst and was pretty impressed -- it looked thoroughly approachable and I do not doubt the performance is there (since the whole reason you do ECS is performance).