Frontier Wars: Online

Frontier Wars: Online is an up-coming free-to-play browser MMO.

[Frontier Wars: Online @operator_games]

Faction level behaviours in my game are getting CRAZY #ScreenshotSaturday #Gamedev #indiegame

[Horse slug @horseslug]

top 10 black forest ham moments

[one dozen bats at a keyboard @PanasonicDX4500]

genuinely in awe of how the tech fiefdoms sent all their best hype men to try to court the Holy See and the response was Leo staking his entire pontificate on waging a crusade against AI

[mationicle @chicobionicle]

Walked into a Papa John’s and they were playing Bionicle: The Mask of Light

[Frontier Wars: Online @operator_games]

@erufutsuinteiru Unfortunately they are the ideal consumer from a dev perspective. They have money to spend, usually don’t end up playing the game past a few hours and thus rarely complain

[Saša Jurić @sasajuric]

To whom it may concern 🙃️

In abstract terms, I think of a software system (e.g. a web server, database, message queue, ...) as a collection of dynamic activities. Multiple things are happening: handling of requests, background tasks, periodical jobs, error handling, reporting, and recovery. Many of this things are completely independent, but some of them are working together.

These activities have their lifecycles. We want to be able to start the activities in the proper order. We want to be able to dynamically start more activities. We want to be able to stop the activities in the reverse order. If Bar depends on Foo, we want to start Foo first, Bar second, and we want to stop them in the reverse order. Some activities will be decomposed into smaller subactivities. So if Foo internally runs Bar and Baz, we want to be able to stop the entire subtree. For example, if a user hits the cancel button, we want to be able to stop all the activities related to that task. And we want to be able to do this even if the task is stuck in some CPU processing loop.

A software system has non-binary success semantics. Just because something fails, doesn't mean everything should stop working. But whatever is tightly coupled to the failing activity should stop too. However, the failing thing should not leave inconsistent mess (state, dangling resources) behind.

BEAM & OTP is give us the primitives that address just that. The way I think about my systems in abstract maps very closely to the way I implement them. This vastly reduces the mental overload of thinking about the code. The conceptual view of the system maps very closely to the actual physical model (process structure). This is a power of a good abstraction. For more details, see my talk Soul of Erlang and Elixir, where I tried to explain the underlying ideas.

The conceptual properties I mentioned above will have to be supported, because they are inherent to a software system. If you're building a software system without this support, these concerns will get entangled with your business logic. Whether you're doing it manually or vibe it, this work becomes more complicated. You or your agent have to deal with non-functional requirements together with the functional ones. This will make your job and the jobs of agents more difficult. Remember: code is the part of the context, perhaps its largest part.

So in the age of agentic development, my position about BEAM remains the same. If you're building a software system, it is the tool that fits the problem, and it will simplify your life. You might bump into situations where some other properties will be more important (e.g. raw processing speed), but you can then implement these parts of your system in another language, say Rust, and manage them from a BEAM-powered system.

As many of you know, I'm a long-time user of Erlang and Elixir. But I don't choose those languages for the syntax. For the record, I actually prefer C-style curly-braces syntax. I use those languages because of the runtime properties and guarantees, and because this technology reduces the impedance mismatch between the way I think about the system and the way I implement it. I also actually mostly prefer Erlang syntax over Elixir (minus some exceptions). The reason why I use Elixir is mostly tooling & some language features (e.g. macros). But the choice of the language was never a fanboy choice for me. If you're not building a system, BEAM langs are most likely not your hammers.

[Frontier Wars: Online @operator_games]

Our new debug overlay is so SICK

#gamedev #TrailerTuesday #indiegame

[xtine @abowlcut]

bringing this “0_o” back. it displays such a specific emotion no modern day emoji could ever evoke

[Frontier Wars: Online @operator_games]

Battlelog now that was a meme. But I liked the idea! I needed it to debug faction battles! Maybe it will be live on the website when the servers are up! 😅😅

#indiegame #gamedev #mmo #ProjectZomboid

[Frontier Wars: Online @operator_games]

@Izkimar I tried playing it. Its laggy af, performance is terrible. Everytime I jump its laggy. The bot controlled heros stand around and do nothing.

The interface menus clutter too much, I can't tell whats going on. Its overwhelming

[Regis Bernard @snekjar]

streaming devlog test of #GardensOfLutonia make me discover lots of things....

[Frontier Wars: Online @operator_games]

Yo dawg I heard you like 2D games so we put a 3D game in your 2D game so you can 2D game while pretending it’s a 3D game. #gamedev #ProjectZomboid

[Frontier Wars: Online @operator_games]

Here's how we finally solved issues around 2D isometric y-sorting in our MMORPG! #gamedev #indiegames #godot #survivalgame #ProjectZomboid

[itamu | Mama's Sleeping Angels dev @isthisamug]

rpg maker ass enemy

[Brooklyn Sue II (Tiger Crane) @susandonym]

damn dude, last night was heavily edited to better appeal to the sensibilities of international markets. last night does not reflect the director's original artistic vision.

[Gatnerd @gatnerd]

A level of Canadian Victory not seen since the War of 1812.