j_rika
New Zealand
https://discord.gg/MApVWgVYrX

I am building the RLW Engine to break down the barriers between playing and creating. Most engines require a computer science degree just to build a simple quest, but I am designing RLW on a simple principle: if you need a text editor to add content, the tool has failed. My goal is to make a world where anyone can design a branching narrative as easily as they can fight a monster.

Design Principles
To keep the engine powerful but easy to use for a solo developer and future creators, I follow these seven pillars:
Data over Code: If it can be JSON, it is JSON, which keeps the engine modular and lightweight.
Hot Reload Everything: I never want to restart the client to see a change. Whether it is an NPC, a quest, or a map layer, updates happen instantly.
Visual First: I believe in building the playground while standing in it. If a task requires an external code editor, the tool is not finished.
Server Authoritative: Even in a creator-first environment, fairness matters. The architecture ensures the server always decides the game state to prevent exploits.
Modular Architecture: Every system is independent and replaceable so the engine can grow without breaking the core framework.
Welcoming UX: Error messages should never be a dead end. They must explain exactly what went wrong and how to fix it.
Content Creator First: The ultimate goal is total accessibility so that a non-programmer can pick up the tools and build complex RPG systems immediately.

The World Construction
The engine uses a sophisticated 8-layer isometric rendering system to allow for deep and atmospheric world building. By separating terrain, environment, and overhead visuals, I can create complex verticality and detail while maintaining high performance through tile culling.

Interactive Systems
RLW is built on a foundation of interconnected RPG mechanics that are entirely data-driven:
Dynamic NPCs: Characters with schedules, wandering behaviors, and branching dialogue trees.
Narrative Quests: Multi-step quest chains including gathering, combat, and exploration.
Live Combat: Real-time stat-based combat with skills, status effects, and loot tables.
Companions: Integrated pet and mount systems that provide both utility and mechanical bonuses.

Seamless Multiplayer
I am building a join-and-play ecosystem where the technical hurdles of multiplayer are invisible:
Global Connectivity: A master server system for discovering and hosting community worlds.
Automatic Distribution: When a player joins a server, all unique content like sprites and maps downloads and loads automatically.
Social Integration: Built-in systems for party management, secure trading, and player inspections.

Value and Access
The RLW Engine represents a transition between adventuring and building. While pricing is currently unknown, the focus remains on providing a suite of in-game editors that allow me to use the same tools I provide to the community, ensuring that the process of making a game is as fun as the game itself.
https://discord.gg/MApVWgVYrX

I am building the RLW Engine to break down the barriers between playing and creating. Most engines require a computer science degree just to build a simple quest, but I am designing RLW on a simple principle: if you need a text editor to add content, the tool has failed. My goal is to make a world where anyone can design a branching narrative as easily as they can fight a monster.

Design Principles
To keep the engine powerful but easy to use for a solo developer and future creators, I follow these seven pillars:
Data over Code: If it can be JSON, it is JSON, which keeps the engine modular and lightweight.
Hot Reload Everything: I never want to restart the client to see a change. Whether it is an NPC, a quest, or a map layer, updates happen instantly.
Visual First: I believe in building the playground while standing in it. If a task requires an external code editor, the tool is not finished.
Server Authoritative: Even in a creator-first environment, fairness matters. The architecture ensures the server always decides the game state to prevent exploits.
Modular Architecture: Every system is independent and replaceable so the engine can grow without breaking the core framework.
Welcoming UX: Error messages should never be a dead end. They must explain exactly what went wrong and how to fix it.
Content Creator First: The ultimate goal is total accessibility so that a non-programmer can pick up the tools and build complex RPG systems immediately.

The World Construction
The engine uses a sophisticated 8-layer isometric rendering system to allow for deep and atmospheric world building. By separating terrain, environment, and overhead visuals, I can create complex verticality and detail while maintaining high performance through tile culling.

Interactive Systems
RLW is built on a foundation of interconnected RPG mechanics that are entirely data-driven:
Dynamic NPCs: Characters with schedules, wandering behaviors, and branching dialogue trees.
Narrative Quests: Multi-step quest chains including gathering, combat, and exploration.
Live Combat: Real-time stat-based combat with skills, status effects, and loot tables.
Companions: Integrated pet and mount systems that provide both utility and mechanical bonuses.

Seamless Multiplayer
I am building a join-and-play ecosystem where the technical hurdles of multiplayer are invisible:
Global Connectivity: A master server system for discovering and hosting community worlds.
Automatic Distribution: When a player joins a server, all unique content like sprites and maps downloads and loads automatically.
Social Integration: Built-in systems for party management, secure trading, and player inspections.

Value and Access
The RLW Engine represents a transition between adventuring and building. While pricing is currently unknown, the focus remains on providing a suite of in-game editors that allow me to use the same tools I provide to the community, ensuring that the process of making a game is as fun as the game itself.