<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Gamedev on Hi, I'm *squid*</title><link>https://orivega.io/tags/gamedev/</link><description>Recent content in Gamedev on Hi, I'm *squid*</description><image><title>Hi, I'm *squid*</title><url>https://orivega.io/images/og.png</url><link>https://orivega.io/images/og.png</link></image><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 26 Mar 2026 23:00:00 +0000</lastBuildDate><atom:link href="https://orivega.io/tags/gamedev/index.xml" rel="self" type="application/rss+xml"/><item><title>Moongate V2 Dev Log #5: GM Tools, Template Tooling, ModernUO Imports, and Smarter Guards</title><link>https://orivega.io/moongate-v2-dev-log-5-gm-tools-template-tooling-modernuo-imports-and-smarter-guards/</link><pubDate>Thu, 26 Mar 2026 23:00:00 +0000</pubDate><guid>https://orivega.io/moongate-v2-dev-log-5-gm-tools-template-tooling-modernuo-imports-and-smarter-guards/</guid><description>This week I added a GM menu, a template validation tool, a dotnet new plugin template, deeper ModernUO import tooling, a cleaner AI runtime, and much better city guards.</description></item><item><title>Moongate V2 Dev Log #4: Combat, Corpses, Scripted NPCs, and a Cleaner Architecture</title><link>https://orivega.io/moongate-v2-dev-log-4-combat-corpses-scripted-npcs-and-a-cleaner-architecture/</link><pubDate>Thu, 19 Mar 2026 23:00:00 +0000</pubDate><guid>https://orivega.io/moongate-v2-dev-log-4-combat-corpses-scripted-npcs-and-a-cleaner-architecture/</guid><description>This week I added combat, corpses, loot chests, scripted NPC dialogue, OpenAI-backed NPC behavior, scheduled events, plugin infrastructure, and a major persistence cleanup to Moongate.</description></item><item><title>Moongate V2 Dev Log #3: Player Portal, Maps, Books, and a .NET Bug I Didn't Own</title><link>https://orivega.io/moongate-v2-dev-log-3-player-portal-maps-books-and-a-net-bug-i-didnt-own/</link><pubDate>Thu, 12 Mar 2026 23:00:00 +0000</pubDate><guid>https://orivega.io/moongate-v2-dev-log-3-player-portal-maps-books-and-a-net-bug-i-didnt-own/</guid><description>This week I shipped a player portal, better world visibility tools, writable books, and lost two days to a .NET bug that turned out not to be mine.</description></item><item><title>Moongate v2 Dev Log #2 — Three Bugs That Forced an Architecture Upgrade</title><link>https://orivega.io/moongate-v2-dev-log-2-three-bugs-that-forced-an-architecture-upgrade/</link><pubDate>Fri, 06 Mar 2026 11:36:00 +0000</pubDate><guid>https://orivega.io/moongate-v2-dev-log-2-three-bugs-that-forced-an-architecture-upgrade/</guid><description>Three hard production issues in Moongate v2: MemoryPack+AOT crashes, doors shifting when toggled, and single-thread bottlenecks under load.</description></item><item><title>Moongate v2 Dev Log #1: When Your Architecture Lies to You</title><link>https://orivega.io/moongate-v2-dev-log-1-when-your-architecture-lies-to-you/</link><pubDate>Thu, 26 Feb 2026 23:00:00 +0000</pubDate><guid>https://orivega.io/moongate-v2-dev-log-1-when-your-architecture-lies-to-you/</guid><description>How I fixed the bootstrap, added source generators, and scripted items with Lua in Moongate v2 -- a modern Ultima Online server built with .NET 10.</description></item><item><title>Moongate v2: Rewriting a Ultima Online Server From Scratch (Because I Wanted To)</title><link>https://orivega.io/moongate-v2-rewriting-a-ultima-online-server-from-scratch-because-i-wanted-to/</link><pubDate>Fri, 20 Feb 2026 23:00:00 +0000</pubDate><guid>https://orivega.io/moongate-v2-rewriting-a-ultima-online-server-from-scratch-because-i-wanted-to/</guid><description>A personal story about nostalgia, a terrible job, and rewriting an Ultima Online server emulator from scratch with .NET 10 and NativeAOT.</description></item><item><title>Small Objectives, AI-Driven Architecture: How Abandoning Dark Lilly Built LillyQuest</title><link>https://orivega.io/small-objectives-ai-driven-architecture-how-abandoning-dark-lilly-built-lillyquest/</link><pubDate>Fri, 23 Jan 2026 11:56:00 +0000</pubDate><guid>https://orivega.io/small-objectives-ai-driven-architecture-how-abandoning-dark-lilly-built-lillyquest/</guid><description>&lt;p&gt;&lt;img alt="lillyquest_logo" loading="lazy" src="https://orivega.io/images/lillyquest_logo.webp"&gt;&lt;/p&gt;
&lt;p&gt;Sometimes the only way to understand constraint-driven design is to ignore constraints entirely, realize you&amp;rsquo;re drowning, and start over.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s the story of Dark Lilly and LillyQuest.&lt;/p&gt;
&lt;h2 id="part-1-the-ambitious-mistake"&gt;Part 1: The Ambitious Mistake&lt;/h2&gt;
&lt;p&gt;In November 2026, I started Dark Lilly. A DOOM-like engine. 3D. OpenGL 4.1. Sector-based geometry with portal rendering. Room-over-room architecture. Full BSP tree implementation. A complete demo level in 10 weeks, working 1.5 hours per day&lt;/p&gt;
&lt;p&gt;On paper, it made sense. I&amp;rsquo;d written about &lt;a href="https://orivega.io/building-a-doom-like-engine-in-2026-discipline-through-constraints/"&gt;building engines through constraints&lt;/a&gt;. DOOM&amp;rsquo;s architecture—sectors and portals—felt like the perfect constraint. Limited but powerful. Reductive but elegant.&lt;/p&gt;</description></item><item><title>Building a DOOM-Like Engine in 2026: Discipline Through Constraints</title><link>https://orivega.io/building-a-doom-like-engine-in-2026-discipline-through-constraints/</link><pubDate>Wed, 14 Jan 2026 19:53:00 +0000</pubDate><guid>https://orivega.io/building-a-doom-like-engine-in-2026-discipline-through-constraints/</guid><description>&lt;p&gt;&lt;img alt="Darklilly" loading="lazy" src="https://orivega.io/images/darklilly.webp"&gt;&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m building (Dark) Lilly Engine, a 3D DOOM-inspired engine in C# with OpenGL. Not to clone DOOM. Not to romanticize the past. But because rebuilding foundational ideas until they&amp;rsquo;re &lt;em&gt;yours&lt;/em&gt; is the only way to truly understand them.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Sometimes the only way to understand a system is to rebuild it.
Not copy it. Not romanticize it. Just rebuild the ideas until they&amp;rsquo;re yours.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m not building a DOOM clone.
I&amp;rsquo;m building an engine that grew from the same questions DOOM answered, under different constraints.&lt;/p&gt;</description></item><item><title>The Book That Pulled Me Back Into DOOM’s Engine Room</title><link>https://orivega.io/the-book-that-pulled-me-back-into-dooms-engine-room/</link><pubDate>Sun, 11 Jan 2026 19:29:00 +0000</pubDate><guid>https://orivega.io/the-book-that-pulled-me-back-into-dooms-engine-room/</guid><description>&lt;p&gt;&lt;img alt="IMG_2654" loading="lazy" src="https://orivega.io/images/img_2654.webp"&gt;&lt;/p&gt;
&lt;h1 id="why-i-bought-the-game-engine-black-book-doom"&gt;Why I Bought the &lt;em&gt;Game Engine Black Book: DOOM&lt;/em&gt;&lt;/h1&gt;
&lt;p&gt;I recently picked up Fabien Sanglard’s &lt;em&gt;Game Engine Black Book: DOOM&lt;/em&gt;.&lt;br&gt;
Not as a collector’s item, not as a coffee-table trophy, but because DOOM has always been an unfinished chapter for me.&lt;/p&gt;
&lt;p&gt;It was the second game I ever fell in love with.&lt;br&gt;
The first one was Wolfenstein 3D, which ran fine on my old 486 (yes, IBM PS/2). DOOM didn’t. I would launch it, stare at a frozen screen, and realize the hardware simply wasn’t enough. So I played DOOM at friends’ houses, glued to the monitor, half jealous and half hypnotized.&lt;/p&gt;</description></item><item><title>Half-Life 2, Havok, and the Quiet Journey of Building Lilly.Engine</title><link>https://orivega.io/half-life-2-havok-and-the-quiet-journey-of-building-lillyengine/</link><pubDate>Sat, 06 Dec 2025 20:20:00 +0000</pubDate><guid>https://orivega.io/half-life-2-havok-and-the-quiet-journey-of-building-lillyengine/</guid><description>&lt;p&gt;&lt;img alt="Half-Life2" loading="lazy" src="https://www.cdkeyit.it/wp-content/uploads/ravenholm-half-life-2-rtx.webp"&gt;&lt;/p&gt;
&lt;p&gt;In the late evenings, when everything finally slows down, I find myself replaying &lt;strong&gt;Half-Life 2&lt;/strong&gt; on my Linux workstation - the one powered by an RTX 5080.&lt;br&gt;
It’s a ridiculous mismatch, I know. With a GPU like that I should be stress‑testing cutting‑edge engines, ray tracing showcases, tech demos that melt silicon.&lt;br&gt;
And yet, instead, I’m back in City 17.&lt;br&gt;
Back with Gordon Freeman.&lt;br&gt;
Back with wooden crates, metal shelves, and that strangely comforting “thunk” when physics does exactly what your brain expects.&lt;/p&gt;</description></item></channel></rss>