Arjan Brussee’s Post

The earliest games were built from scratch for each project. There were no engines—just lines of custom code. This changed in the 1990s when developers realized reusable engines could save time and push innovation. Could game development have scaled without this shift to shared engines? #GamingHistory #DevEvolution #CodeInnovation

🎓 Being an Indie Game Dev = Learning in Public No formal training? No team? No problem. 🧠 You’ll learn by doing 📦 You’ll ship before you’re ready 🔁 You’ll break things (and fix them badly) 📢 You’ll post online and learn from feedback Indie dev isn’t just about making games. It’s about becoming someone who can make games.

🚀 Excited to share that I’ve been officially recognized, in their GitHub repo, as a **contributor to the [Flax Engine](https://flaxengine.com)** — an open-source game engine that empowers creators to build high-performance games! As part of my contribution, I’ve been: - 🐞 Identifying and reporting bugs to improve engine stability and usability - 🧪 Investigating and resolving issues in the codebase - 🎨 Submitted a PR to enhance the UI, making the editor more intuitive and user-friendly #GameDevelopment #OpenSource #FlaxEngine #GameEngines #SoftwareDevelopment #Contributor #BugHunting #UIUXDesign

Lots of progress today in the multiplayer plugin! A menu for hosting and joining is implemented (Only hosting is working for now, adding the join functions tomorrow). All inputs are working perfectly and the game launches through Steam as it should. I'll be throwing all the code on GitHub when it's done and making a full blogpost later. Here you can see it implemented into UE5, you can now alter the amount of players you want and select a game mode (The game I'm working on has Free For All, Team Deathmatch and Capture the Flag). UE5 doesn't make C++ dev easy, tons of setbacks and regenerating files and such, but that's part of the fun (Or something like that). You can add this to any UE5 project you are making and integrate that into Steam (Make any game modes you wish by amending the code)!

🎮 Choosing a game engine is important… but choosing the right language is critical. From C++ powering AAA giants to Lua enabling live-service updates, the language you pick affects more than syntax; it shapes your team, your timeline, and your future scalability. We broke down the top languages used in game development today: ✅ What they’re best for ✅ Why developers love them ✅ Pros & cons you actually need to consider ✅ Real examples and engine fit Whether you're prototyping an indie hit or scaling a live multiplayer game, this carousel will help you pick the right tech from the start. 👉 Check the full breakdown here: https://lnkd.in/g2bGwFna 🔗 Dive in and comment with the stack you're using in 2025 👇 #GameDevelopment #ProgrammingLanguages #GameEngine #GIANTY #GIANTYSHARE

🎮 Multiplayer Game Dev Without Real Testing Is Just... Hope. (and hope is not a strategy.) If you're building multiplayer games and you're not testing in actual builds, with lag, loss, disconnects, multiple devices, then you're basically crossing your fingers and praying nothing explodes. I’ve done that. Spoiler: it does explode. 💥 Here’s what I learned the hard way (so you don’t have to): 🧪 Editor testing is not enough Your Editor PlayMode isn’t running IL2CPP. It isn’t simulating mobile. It isn’t showing you how bad your sync really is under pressure. 🌐 Simulate network chaos Test your game with: 300ms latency 10% packet loss Random disconnects Only then will you see what your systems are truly made of. 📱 Use real devices, real builds If your game "works fine" in the editor but crashes on Android/iOS/Steam... that's not QA's fault. That’s on you, dev. 😅 🔄 Automate test flows if possible Manually pressing buttons to test the same flow every day? You’ll miss edge cases. Automate and sleep better. ✅ Best multiplayer devs I know test like maniacs. They break their games on purpose. They test on builds every single day. If you're serious about launching stable multiplayer experiences — this is non-negotiable. #GameDev #Multiplayer #Unity3D #PhotonFusion #Testing #DevTips #BuildBetterGames

🎮 Building a multiplayer Unity game? Photon + Firebase = scalable, real-time multiplayer without a backend team. We just published a hands-on guide for devs & indie studios looking to ship faster, sync smoother, and scale smart. Covers matchmaking, real-time sync, data storage & more. #Unity3D #Multiplayer #PhotonEngine #Firebase #GameDev #IndieDev

Unity is a powerful and easy to learn free game engine software that helps game developers to create awesome 2D and 3D games in both android and iOS and earn handsome money out of it. ...... #technology #internet #marketing https://lnkd.in/gfGgxbYZ

Supercell has officially lifted the invite-only restriction for mo.co, its monster-hunting action RPG. After launching in open beta back in March 2025 with limited access, the game is now open to all players globally on both Android and iOS. With the invite wall gone, Supercell is likely aiming to expand its player base while preparing for the game’s full global release. The Finnish mobile games giant has also mentioned that while the entry barrier has been lifted, the marketing will still be low-key for now. Full story: https://lnkd.in/gdcbxwG8

🚀 Day 688 of #700DaysOfCode Socket.io vs WebSocket – Which One Should You Use? ⚡🔌 Real-time apps are becoming the norm — chats, live notifications, multiplayer games... all need one thing: live communication between client and server. But the big question is: Should you use WebSocket directly or go with Socket.io? In today’s post, I’ve shared a simple breakdown of Socket.io vs WebSocket, how they work, and most importantly — which one to use in which real-world scenario. 📌 If you're building real-time features — this post is a must-read. Save it for future projects! #Day688 #learningoftheday #700daysofcodingchallenge #webdevelopment #react #next #reactnative #frontenddevelopment #codingtips #codingchallenge #codingcommunity #WebSockets #Socketio #RealTimeApps #FullstackDeveloper #LearnByBuilding #DevJourney