Salut tout le monde !

Cela fait maintenant quelques jours que la démo de VectHorde est en ligne. J'ai eu le plaisir de voir quelques téléchargements, et je tiens à remercier ceux qui ont pris le temps de tester le jeu (et le ZlormaEngine en action) !

Je commence à réfléchir au développement d'une version complète. Pour que ce futur contenu réponde à vos attentes, j'aimerais beaucoup avoir vos avis :

1. Le gameplay : Que pensez-vous de la nervosité des combats et des contrôles ?
2. La progression : Est-ce que le système de loot et le Terminal Nexus sont intuitifs ?
3. Le contenu : Qu'aimeriez-vous voir dans une version complète ? (plus d'ennemis, de nouveaux types d'armes, des modes de jeu différents...)

N'hésitez pas à être honnêtes, c'est le meilleur moyen pour moi d'améliorer le moteur et de vous proposer une expérience encore plus fun.

Merci d'avance pour vos retours !

[https://zlormack-studio.itch.io/vecthorde-swarm-survival\]

I have published just a minute ago a library, which is an abstraction for managing you combat/abilities logic outside code but inside configuration files.

https://github.com/optical002/rust-logic-constructor

I hope it might be useful to someone.

PORTFOLIO: this is my first project and do not have a portfolio of any kind, Hi, I'm looking for programmers for a Tomodachi Life-style game, but open-source. We'll be using Bevy, the game engine made in Rust. The idea is this:

The Tocs: will be the alternative to Miis to avoid getting hit by Nintendo's hammer (hehe wink wink).

Archipelago: unlike Tomodachi Life, this won't be just one island, but an archipelago of up to 20 islands where you can send your characters by ferry or train. You can create your own islands.

Plugins: you can easily create food, clothing, objects, pets, and situations. You can also create more customized plugins with a language like Lua or Python. Some plugins will come with the game and can be removed. There will also be a plugin store, of course.

Base Plugins: The natural disasters plugin will have tsunamis, storms, earthquakes, and hurricanes. NOTE: the Tocs never die. The diseases plugin will include 20 diseases like the flu. Some Tocs could fall into a coma or... On the stretcher, you can bring them food and objects. These comas last between 5 and 15 days, but the tocs always heals.

NOTE: I'm a 3D artist and a bit of a draftsman, so I have some of the models. The game already has a space on Matrix; here's the link: https://matrix.to/#/#toc-life:matrix.org

Just a quick updated about progress on `wgsl-rs` including generics support and support for "extensions".

Working on a narrative roguelite. The codebase is growing and I keep hitting walls with the borrow checker, especially around systems that need shared access to world state.

So far my approach: split everything into small ECS systems through Bevy. Each system only borrows what it needs. Works ok but I end up with a ton of tiny systems and sometimes the ordering gets complicated.

Tried using events as a buffer between systems that would otherwise need to share state. That helped but adds indirection.

Are there patterns I am missing? I know about interior mutability (RefCell, Mutex) but those feel like fighting the language. Is there a more idiomatic way to handle shared mutable game state that does not involve wrapping everything in locks?

I was gonna upload a more complete full exploration including scale depth up to 12, but my computer wants to crash on me 15 minutes in. So for now, here's this. The torus / spiral formation is because of how I configured the field, it can work on its own but depending on the address space you give it, it manifests in different ways.

The goal here was/is/has been to 'simulate' a reality in a program, but technically this is a simulation of gaussian primes in/as a complex field.

The real breakdown:

This is vibecoded, its a rebuild of a rebuild of a rebuild for a project I've been working on since last June

I barely understand the concepts I utilized to make this, just barely enough to have come up with working ideas which eventually got me to this point
At first, I tried to make this in unity and I don't think I had one successful build last year outside of little webgpu HTML sims for interesting recursion

I can't really give away the sauce when I barely understand the sauce myself, there's a lot of moving parts here. Stuff that I have which I haven't put into the rust version yet. Plans to make a background neural net since I have an RX card which can run it, and then use that neural net to supercharge the sim. And I haven't worked out the full pipeline for that yet

Right now honestly it's a race for me to develop my different ideas as native programs.

Not making any claims about the sim here except that its a complex wave field. Everything about it so far (in terms of emergence) is discrete and not catalogued but I'm working on that part currently. It MIGHT have some sense of 'true emergent physics' or it might just be a violent soup of stuff geometrically bound to be in the shape it is. Or maybe the latter begets the former, who knows.

Right now this is really just an engine not just a mere 'simulation' and my big long term plans are to make actual environments and an engine scaffold for game development (it probably would be a very different kind of game though, and most familiar game features would be emergent or forced phenomena I'd have to steer, but still doable with enough work)

I'm also trying to get this thing into mythical levels of performance. For me, as inexperienced as I am, it's seriously just confusing at times. Seems to run ok for what it is, for what I can get out of it. And my background is in modding games, single script editing, following instructions for long form tasks... So I'm of course out of my depth here again and again as I move through one set of problems to the next

i was banned i rust for cheating when i have a pc that can barely even run rust i hadnt played rust for like a month or so and when i logged back onto my steam acc and hit play on rust it says i had been game banned for cheating when i literally didnt. steam wont even give me refund because i have 20 bours on the game and i tried to get a ban appeal then the

moderator said this...

please help me guys get me in touch with a moderator or something this is the first game that i bought

Been building a narrative roguelite with Rust/Bevy. One unexpected benefit: the strict compiler is perfect for AI assisted development.

I use AI to generate a lot of my game logic code. With TypeScript the AI would fix one thing and silently break another. Runtime bugs everywhere, and the AI kept making the same mistakes in new code. Super frustrating.

Moved to Rust and it just stopped happening. The AI makes suggestions, the compiler rejects the bad ones, I iterate. The feedback loop is way tighter.

Bevy's ECS was also a great fit. Game is logic only right now (no rendering), so being able to build everything as pure system transforms without worrying about visuals was huge.

Anyone else using Rust for AI heavy workflows? The compiler as a safety net for generated code has been a game changer.

Dev log: https://old.reddit.com/r/aigamedev/comments/1tqrbd9/

I'm building a 2D game in my spare time, and at some point I needed audio that went further than what existing crates offered, so I started building my own engine. I studied music technology before I got into software engineering, so audio is an area I want to get right.

If you need something production-ready today, kira is by far more mature. AIRE is more for developers who want an audio engine that eventually understands the environment it's running in, not just one that plays files and applies effects, which in all honesty is what it is right now.

Some highlights:

• Communication with the audio thread is lock-free, safe to call from any thread without worrying about blocking
• A band-limited oscillator with six waveforms: sine, saw, sawdown, triangle, square and pulse. PolyBLEP is used for antialiasing, (triangle uses PolyBLAMP)
• WAV, OGG, FLAC, and MP3 supported, both in-memory and streaming
• ADSR envelope with linear and exponential curve shapes

What I'm actually working toward is geometry-aware audio using acoustic ray tracing for my game. The idea is to shoot rays from sound sources into the tile world, use the results to derive reverb parameters dynamically, and have the acoustics respond to the environment in real time. That's not there yet, so next up is basic 2D spatial audio, then an FDN reverb.

Repo: https://github.com/Breijen/aire

Bevy Game Engine Explained Visually
A visual tour of how Bevy helps you compose complex, emergent games from small independent systems and a data-driven architecture.

I made a small game engine called Usagi for prototyping 2D games as quickly as possible with Lua. It's free and open source and made with Rust + Raylib. After experimenting with using Rhai years ago, I decided to switch to Lua and have been seriously working on the engine and games with it over the past month. I just released v1.0 today and thought it'd be fun to share with the Rust gamedev community.

Here's the project's homepage: https://usagiengine.com/

And you can view the source here: https://github.com/brettchalupa/usagi

The engine is used via a command-line, much like cargo. You can usagi init to create a new project. usagi dev to boot up the dev game that live reloads code and assets. And usagi export to generate cross-platform builds of your game for web, Linux, macOS, and Windows.

My motivation for creating Usagi was that I love using tools like Pico-8 and Love2D for prototyping and game jams. But I wanted a free and open source engine with a nicer developer experience. In particular live reload and easy web exports. Usagi embraces constraints and provides sensible defaults, like a pause menu with input binding, to try to help devs focus on the game rather than the ancillary parts of development.

Since the engine is open source, the hope is that if someone makes a prototype they want to turn into a larger commercial game, they can just fork the engine and customize it themselves, write more bits of it in Rust, and change the API as they see fit.

Rust was a particularly great fit for the project. I've made one public Rust game and a few unreleased smaller ones before Usagi. I experimented with using C, but I really missed cargo and all the crates. Writing tests, working with clippy. Just a great experience, as I think fans of Rust already know.

I'd love it if you check the project out! It wouldn't be possible without the great mlua crate, Raylib, and a bunch of other awesome dependencies.

I'm new to rust based develpment, should I use bevy, or godot rust to develop my game?

I would also like pros and cons of each

I've been adding some chunk generation and rendering optimization techniques, and here you can see the performance of the world generation.
I'm still trying to improve it, but I think I can now move on to something bigger. 😛

Previously generated chunks are instantly re-rendered. Even newly generated chunks can keep up with my movement speed.