Online community platforms are assembly-kits for large, communal bonfires, designed to draw people towards the light and into the warm togetherness of community. I think the primary function of bonfire software is to create space for group-scale discourse.
Riffing on thoughts about healthy information consumption, Tom Critchlow described his personal campfire thusly:
If you haven't heard the news, Reddit is making some drastic, user-hostile changes. This is essentially the final stage of any ad-supported and VC-funded platform's inevitable march towards enshittification.
I really love the /r/rust community. As a community manager it's my main portal into the latest happenings of the Rust ecosystem from a high-level point of view primarily focused on project updates rather than technical discourse. This is the only Reddit community I engage directly with; my daily fix of the Reddit frontpage happens strictly via login-less browsing on Apollo, which will soon come to an abrupt end.
This moment in time presents a unique opportunity for this space to claim its independence as a wholly community-owned operation. If the moderators a
The primary of our first PoC is a static site export that can easily be pushed to one of the popular free host providers:
⚔️ Salutations fellow legends! ⚔️
Wow! Time has passed quickly since our last blog post, however, much progress has been made! Today, we're going to go over the technical aspects of the core engine for Legend of Worlds and what has been accomplished so far. The core of the engine has been completed, and now we are at the point where we can focus on gameplay and world creation logic!
Legend of Worlds is a cross-platform, cross-play, 2D online sandbox multiplayer experience where you can join, play, create and share player created worlds. This blog post covers the open-source game engine I've created in order to build this game.
In the last post, we discussed the benefits of Rust and WebAssembly in our game engine architecture. Rust gave us many benefits, but one issue it gave us was long compile times, depending on the more code and libraries we jammed into one module. This was getting to be a problem, as a Rust project starts off on my machine as a few seconds to compile
I started filling in the gaps in my home-made physics implementation. In this post I go painstakingly detailed about my adventures in implementing one-way platforms and prematurely optimizing broadphase collision detection. Bonus yak-shaving sections on bevy_screen_diagnostics, and bevy_sparse_grid_2d
Why on earth am I making a physics engine when there is Rapier?
As I've now experienced first hand, and we'll see in the rest of this post, making physics can be a deep rabbit hole, with so many yaks to shave you never get out.
[Posted 22. February 2022] [Author: Erlend]
Our 🌶Spicy 🦞Lobster studio venture is among the first of what we hope will become a common type of company, designed first and foremost to Do Good by means of radical openness.
I drew a couple of sprites, added cross-platform multiplayer, added some ui using kayak_ui and fixed a lot of network-related bugs. Last time, I thought I would be able to take a break from the technical side. It turned out I was wrong. I had a lot of tough bugs, both with de-syncs, and NAT-traversal. I guess it’s one of those reasons why they tell you not to make a networked multiplayer game.
Last time I thought I’d managed to get a completely deterministic simulation. As I tested more thoroughly with friends over the internet, that turned out not to be the case. After a long time of playing, positions of players and the ship would go slightly out of sync.
I’d run out of obvious non-determinism bugs to fix (
"How I Didn't Clip the Sound Effects" Redux - Handling Sounds During Rollbacks Handling sound effects during rollbacks is a difficult problem!
Now that all the issues with sounds-during-rollbacks are resolved in Skullgirls, I'm gonna document what I did so that everyone else doesn't have to figure it out from scratch.
The title is a reference to Mauve's now-deleted article about Rollcaster, titled "How I didn't clip the sound effects" (archive.org) which is incomprehensible. I feel okay saying this because when I started working on sounds-in-rollbacks I talked to Mauve, who said, and I quote, "This is incomprehensible, why did I write it like this?" :^)
Now, I lied - handling sound effects during rollbacks is fairly simple. You just have to have someone else think about it for a long time first to come up with the simple way. :^P
Many systems in games, like well-written menus or even the characters in FPSes(!), sometimes work by keeping two states: a "desired" state, and an "actual" (or "displayed")
If you already know what an ECS is, jump to the "Comparison With Other ECS" section.
The title is a lie. In reality, this is an Entity-Component-Resource-System library.
First, let's start at the beginning. What is an ECS you ask?
| Event Chaining as a Decoupling Method in Entity-Component-System | |
| Joël Lupien (Jojolepro, [email protected]) | |
| https://patreon.com/jojolepro | |
| ================================================================================ | |
| Context | |
| ================================================================================ | |
| In game engines, we often have a lot of dependencies between modules. | |
| For example, the user interface often depends on the renderer, window and |
