Revision 1

Gothic 1 Remake is a ground-up rebuild on Unreal Engine 5. The studio, Alkimia Interactive, has talked about the technical stack in several public dev posts and "Making Of" episodes. This article collects the parts that are publicly confirmed: the engine version, the audio middleware, the scripting language used for game logic, the way NPC daily routines are built, and the modding pipeline. Specific version numbers are hedged where the public materials are not exact.

Engine

• Renderer. DirectX 12. See System Requirements for the published GPU and VRAM tiers.
• PSO precaching. On first launch the game pre-compiles a set of pipeline state objects to avoid the stutter that often shows up when the renderer compiles shaders on demand mid-play. The pass adds a small one-time wait to first boot in exchange for smoother frame pacing once the player is in the Colony.
• Lightweight actor cache. A studio-built actor management layer keeps the per-frame cost of large NPC and creature counts under control. The system is built to scale to the dense, persistent population the Colony needs.
• Expanded world. The studio has stated the playable area is roughly 10 to 30 percent larger than the 2001 reference layout, filling in areas the original team planned but could not fully build out.

Audio Middleware

Audio is handled through the FMOD middleware. The soundtrack is composed by Kai Rosenkranz, returning from the 2001 release, who has rewritten and expanded the score for the larger world. FMOD is used both for music and for the dynamic ambient mix that drives the camp soundscapes, weather, and combat layers.

Scripting Language: AngelScript

• Why a scripting language. Most gameplay rules live as scripts rather than as compiled C++ code. That keeps iteration fast for the team and gives modders the same entry point.
• Dogfooded by the studio. The press-only 2024 demo build was itself constructed as a mod of the full game, which the studio has cited as evidence that the modding tools will be capable enough to support full custom campaigns after launch.
• Public modding surface. Alkimia has stated that the same AngelScript pipeline used in development is the public modding pipeline. Specifics about modding tools, distribution, and console availability will follow the launch.

NPC Pipeline And Motion Magic

NPCs in the Colony follow believable daily routines that come from a studio process Alkimia has talked about as "motion magic." The pipeline records longer mocap sessions of actors performing realistic routines (working, eating, walking, sitting at a fire), then splits the captures into categorised sequences that get assigned to characters. See Alkimia Interactive for the studio profile. Public talks reference around 600 unique NPC faces, with persistent state so the Colony reacts when a named character dies; the exact population count should be treated as approximate until a launch patch note confirms it.

• Face variety. Faces are generated with a deep-learning morphing pipeline, used to avoid the repeated heads that were a known limitation of the 2001 build.
• Routines. NPCs work, eat, sleep, drink, gather, play instruments, and socialise on visible schedules. The same routines are the foundation for the day-night structure of camp quests.
• Persistent state. Named NPCs carry persistent state. Killing one removes them from later routines and changes which quest beats are still available.

Linguistics: A Built Orcish Language

The studio commissioned a professional linguist to design a full constructed language for the orcs. The Hero can learn it through a progression path that unlocks new dialogue and quests with Orc NPCs. See Orcish Language for in-fiction detail and Orc Culture for the cultural context the language sits inside.

Studio Footprint

See Also

System Requirements for the PC tier the engine targets. Alkimia Interactive for the studio. Kai Rosenkranz for the composer. Orcish Language for the in-fiction language the linguist built. Release History for the milestones the build hit along the way.