DevLog #8 – The Metal-Up Rebuild & Easter Alpha Targets
TL;DR
- The Great Pivot: Commercial pre-built engines have been completely abandoned. RiftForged now runs entirely on a bespoke, 100% custom-engineered C++ and DirectX 11 engine.
- True Server Authority: Combat architecture is locked in. Zero client prediction. All animations and hit registrations are strictly server-authored for absolute fairness.
- Polymorphic Abilities: A new data-driven framework allows skills to drastically alter their behavior based on the specific weapon type equipped (e.g., Bow vs. Melee).
- RiftEditor is Live: Built a custom spatial mapping tool to visually paint biomes, triggers, and spawns directly into the engine's database.
- Alpha Target Locked: Core networking is stable. Focus is currently locked on Crafting, Progression, and UI ahead of the upcoming technical tests.
The Engine Rebuild (Goodbye Commercial Engines)
If you look back at DevLog #7, written six months ago, we were still relying on a commercial engine client to parse server snapshots. That is no longer the case. To achieve the massive multiplayer loads, deterministic physics, and absolute server authority required for RiftForged, we had to own the entire stack.
RiftForged is now running on a 100% custom-engineered C++ architecture with a bespoke DirectX 11 renderer. By removing the bloat of commercial engines, we have achieved incredibly lean network batching, maintaining 100+ FPS while syncing massive amounts of entity data. If you are searching for a true custom-built MMO, you have found it.
True Server Authority & Combat
In most modern action RPGs, the client predicts combat to hide network latency, which leads to ghost hits, desyncs, and animation canceling exploits. We went the other direction. RiftForged uses strict, zero-prediction server authority.
When you press a button, the server validates the action, begins a timer, and authors the animation state. The server calculates the exact dt_hit_time and pushes the hit event to the client. If a strike connects visually on your screen, it is guaranteed to have registered on the server. Fairness and deterministic outcomes are the priority.
The Polymorphic Ability System
We have engineered a highly ambitious, data-driven JSON ability framework. In RiftForged, abilities are not hardcoded static spells. They are dynamic events that compile their behavior based on the catalyst you are holding.
For example, casting Coronal Pulse while holding a sword compiles into a 120-degree melee cone sweep. Casting that exact same ability while holding a bow compiles it into a high-speed projectile with a sticky impact that detonates into an AoE burst. This polymorphic system provides immense player agency, allowing weapons to fundamentally alter how your class skills behave.
Crafting, Progression, and RiftEditor
The core gameplay loops are coming online. The Assembly Terminal is live, allowing players to spend Shimmer and Solar particles to forge physical gear components synchronized perfectly with the server's Wallet Component. The Ascension Tree—a massive node graph for deep hero progression—is wired and functioning.
To support all of this, we also built RiftEditor, a custom WYSIWYG spatial brush tool that allows us to paint bounding boxes, entity spawns, and biomes directly into the serialized world data, moving us away from hardcoded arrays and into true engine-level world building.
What’s Next (→ The Easter Alpha Target)
- UI Cleanliness: Replacing placeholder UI elements and refining the frontend overlay.
- RTT Smoothing: Implementing Exponential Moving Averages to perfectly sync client-side network pings with server animation ticks to ensure smooth gameplay.
- The Technical Alpha: Preparing the servers to invite the first wave of players in. We need you to log in, cast abilities, and try to break the network loop.
I am bringing true server-authoritative synchronization back to the genre. Join me.