top of page

HOW IT WORKS

Structure

Red Forge games are created by providing the core engine with configuration data that is updated and constructed using an editor. The engine supports multiple editors including visual editors for Mac, PC, VR, or editors for visually impaired developers such as the Hodr Engine.

Game developers can freely switch between editors as required, so may use a non-visual editor whilst travelling and a VR based editor for object positioning.

The game itself is rendered for the player using a 3rd party engine, Unity. We are also planning support for engines such as Unreal Engine or Godot which may be more beneficial from a licensing point of view.

Technical flowchart displayed on a futuristic tablet screen, illustrating the Red Forge engine architecture. The diagram shows multiple editors (PC, Mac, VR) connecting to core game and data nodes, which then interface with the Red Forge engine and rendering systems, including integration with Unity, Unreal Engine, and Godot

Click image to expand

Design

Red Forge uses a hierarchical approach to games development with the "Game" as the top level.

Each game is a series of levels, and each level comprises of a series of maps containing arenas, players, non-player characters and in-game objects for the player to interact with.

 

Technical flowchart displayed on a futuristic tablet screen, outlining game design architecture. The diagram displays a central "Levels" node connected to branching categories including "Quests," "Save Game," "Maps," "Players," "NPCs," "Objects," and "Arenas," all originating from a top-level "Game" node

Click image to expand

Landscapes

Within the level is a series of maps. These are typically based on different scenery styles, but we support the option to mix and match as required.

Initially the developer will be manually snapping together arenas to build their maps. But we have prototype functionality being tested that utilizes procedural generation to create maps of infinite size and scale.

The engine provides automatic optimization for object budgets so the developer will not need to undertake complex occlusion optimization (i.e. the engine automatically handles turning off objects players cannot see).

 

Technical flowchart displayed on a futuristic tablet screen, illustrating an interconnected network of arenas. The diagram shows multiple "Arena" nodes linked together in a branching structure, set against a dark, tech-themed background

Click image to expand

Arenas

The core of a Red Forge game is the arena. This is a specific game place area that contains a series of exits, in-game objects, NPCs and navigable areas.

Template arenas are provided from our content library, and the developer can then customise and adjust them as required.

All objects available to be used are designed as "Red Forge" .

 

View of a fantasy game arena displayed on a futuristic tablet screen, featuring a multi-level stone cavern, red paths leading across water, glowing lanterns, and small character figures

Click image to expand

Story

Most game engines do not consider story in the game creation process. Yet to a player, the story and its characters are the most compelling reason to play games.


“Red Nought” believes story is at the heart of the game's creation process and as such we provide a series of tools that help you design your game.


To make the games design process easier to understand we utilize the metaphor of a book with chapters and characters. We break down a complex game into a series of short sequences.

Technical flowchart displayed on a futuristic tablet screen, illustrating the narrative structure. The diagram shows a "Game" node branching into multiple "Chapter" nodes, which then lead to a "Sequence" node that further breaks down into "Characters," "Objects," "Interactions," and "Narration," all set against the background of an open antique book

Click image to expand

View of a fantasy game chapter environment displayed on a futuristic tablet screen, showing a knight character standing on a stone staircase within a cavernous, multi-level landscape that includes a wooden gate and scattered treasures

Click image to expand

Chapter

​

This is an example of a simple chapter in a game. In this case the Brave Knight has entered an Arena. The narrator will provide some backstory as he steps into a Narration Point that explains that he needs to find the key to open the door that leads to the next Arena.


Once the key has been collected, the door will open, and the second narration point will be enabled to provide the next installment of the story.


Finally, when the player goes through the open door, the status of the overall game will be updated to say that this chapter has been completed.

Technical flowchart displayed on a futuristic tablet screen, depicting a narration sequence. The diagram features a small knight figure appearing above an open antique book, with an arrow pointing to a glowing blue magical orb that is emitting ripple effects, set against a dark, tech-themed background

Click image to expand

Narration

“Narration” allows the player to be told the story as they progress through the game. Any number of processes can trigger narration to be played, but it will usually be at a point where the player has achieved a goal or walked into an area that requires them to be told about the next stage of the game.


Narration can either play once only, or every time. Narration comprises both audio as well as a transcript for audio-impaired players to make use of.

Interaction

All objects in “Red Nought” have a status. This status determines the behavior of the object and how it interacts with its surroundings. For example, a door could be “Locked”, “Unlocked” or “Open”.


All story elements are broken down into simple processes. Most object interaction is driven by “Action Points”. When a character walks into the “Action Point”, it will then change the status of itself and / or other objects in the game.


As objects change status, actions will be carried out such as a door will unlock and swing open.

Technical flowchart displayed on a futuristic tablet screen, depicting a gameplay interaction. The diagram shows a small knight character and an open book pointing to a glowing magical key, which then points to a wooden gate, set against a dark, tech-themed background

Click image to expand

Status

In this case, when the player walks into the “Key”, it will change the key’s status to “Collected”. When “Collected” the key will change the state of the door to “Unlocked”. It will then make itself invisible to show it has been “Collected”.


When the door’s status changes to “Unlocked”, it will trigger the opening animation to show the player that they can go through. It will then change its status to “Open” ready for the next stage.

Technical flowchart displayed on a futuristic tablet screen, illustrating item progression. The diagram shows a wooden gate and a key moving in a sequence involving an open antique book, indicating a transition or state change, set against a dark, tech-themed background

Click image to expand

Completed

The door changes its status to “Open” and enables a new “Action Point”.


When the “Player” enters this “Action Point”, it will change the status of the “Chapter” to completed. The “Action Point” will also change its status to “Completed”.


With the completion of the “Chapter”, the story has progressed, and the “Brave Knight” has played their role in the story by accomplishing their tasks.


The next “Chapter” can now be started.

​

Technical flowchart displayed on a futuristic tablet screen, showing a completed gameplay sequence. The diagram features a knight character pointing to a wooden gate, which then points to a glowing magical orb, all positioned over an open antique book, set against a dark, tech-themed background

Click image to expand

bottom of page