While working on the Czech localization, I sometimes come across content that players would never see during normal gameplay. The game files contain traces of unused mechanics, unfinished stories, and mysteries that only partially made it into the final game.
After I published the first findings, I received a huge number of messages. Some people wanted more detailed information and concrete evidence, while others considered these findings a hoax. That is why I separate what can be directly supported by the game files from what is only a reconstruction or an open question.
! This page contains spoilers and discusses internal game data.
What is confirmed and what is reconstruction
Development traces that are only partially visible in the game
The analysis is based on exported Blueprints, models, skeletons, animation data, textures, and the localization package. Technical names and relationships come directly from the game files. Where the data does not tell the whole story, the interpretation is explicitly presented as a probable reconstruction.
01
Inaccessible mechanic
Fishing
Fishing is not available in the final game. However, the files contain a surprisingly coherent framework of the system, showing that fishing was more than a brief idea on paper.
Confirmed in the data
The mechanic had UI, a rod, and animations
FishingWidget contains a button for working with bait.
ChooseBaitWidget is a separate interface for choosing bait.
The Blueprint calls the native function FishingWidget::ShowChooseBait(bool).
FishingRod is a dedicated SkeletalMesh with its own physics asset and skeleton.
The skeleton contains MainHandSocket, SecondHandSocket and most importantly BaitSocket.
There is a dedicated Fishing BlendSpace, idle animations, and directional poses.
FishingRodOverlay is a dedicated character animation layer for fishing.
A_PickUpLineFishing is a multi-second action animation for handling the fishing line.
Prepared locations in the world
Fishing was intended to work only at specific spots
Specific fishing spots are already prepared in the game world. They contain a chair with a fishing rod ready to use, suggesting that the mechanic was not meant to be available anywhere near water, but only at predefined locations. In the current version of the game, however, the prepared rod cannot be interacted with.
System reconstruction
How the pieces fit together
CharacterSK_NH_Ch1_Skeleton
↓
FishingRodOverlayanimation layer
↓
BP_RodVisualrod visual
↓
BaitSocketbait attachment point
Conclusion
The number of interconnected assets points to a developed gameplay mechanic that already had UI, animations, a rod model, and parts of its runtime logic. The available data does not show whether it was permanently cancelled or merely postponed.
02
Inaccessible content
Love Story
A standalone story thread that was classified directly among the game puzzles during development. The data preserves unique drawings, physical items, a spatial trigger connected to native code, a link to a painter, and a work-in-progress localization text.
Technical evidence
Love Story was structured as a standalone puzzle
The BP_LoveStoryTrigger Blueprint is located directly under /Game/Blueprints/Puzzles/LoveStory/. This is an important clue because the developers did not classify this thread merely as ordinary environmental storytelling, but directly among the game puzzles.
The BP_LoveStoryTrigger itself inherits from the native /Script/G1R.LoveStoryCollider class and contains a spatial BoxComponent named Collider. The thread therefore had its own trigger that could react to the player entering a specific area or to another event at that location.
BP_LoveStoryTrigger→LoveStoryCollider→Lovers[]
The editable Lovers[] array works with BP_StaticMeshBloodActor objects, meaning bloody or dead character objects. The GetLovers() function iterates through every entry, takes its Mesh Component, and passes the resulting meshes to the native LoveStoryCollider system.
The trigger also directly uses the P_Inscets_Flies_FlyingAccumulated_DecompositionBodies effect, a system of flies around decomposing bodies. The exact puzzle mechanism cannot be determined from the Blueprint because the main logic remains in the game's native code.
The files also contain the items ItMs_Scroll_LoveInterest, ItMs_Scroll_LoveInterest_2, ItMs_Scroll_LoveStoryWomen and LoveStoryFogTower.
In the folder Storytelling/LoveStory there are also three separate visual variants LoveStoryWomen_01, _02 and _04. Their textures survive directly in the game data and are shown in the gallery alongside this text.
Additional connection in the data
The clues lead to a painter
Another important clue is the connection between Love Story and data labeled painters. These lead to a cave on the hill opposite the Old Camp, where a note can be found from a painter who repeatedly painted someone close to him. The drawing motif therefore appears not only on the scrolls themselves, but also in another layer of surviving game data.
I painted you again tonight. I got the mouth wrong. Yesterday it was the eyes. With every new painting, there is a little less of you in it.
This place eats away at a person from the inside. The damp, the greyness, the same faces beating the same empty hours to death day after day. You forget what a clear morning looked like. You forget the sound of your own laughter. I thought painting would save me. But it only helps me count the days.
This connection matters mainly because the motif of drawing one another also appears in the surviving WIP (Work in Progress) text. The data alone is still not enough to reliably determine the full sequence of events or the identities of the people involved.
Surviving localization fragment
The only known Love Story text
I had to leave. They tell me you sail in the morning. I cannot come to the dock. Take this instead. Same body you tasted last night. Drawn while yours dried beside it. You catch the eyes better than I do. And everything else for that matter.
Conclusion
Love Story was very likely being developed as a standalone puzzle thread rather than merely passive environmental storytelling. The Blueprint being located directly under Blueprints/Puzzles/LoveStory, its own spatial trigger, the Lovers[] array, and its connection to the native LoveStoryCollider all confirm that it was intended to contain active game logic. The exact puzzle mechanism and the complete story cannot be determined from the available data because the main logic remains hidden in the game's native code.
03
Partially inaccessible content
Serial Killer
Unlike the previous two cases, this story is genuinely present in the game. Players can find the victims, bloody markings, and the cave containing the dead killer. However, the localization data shows that this storyline was not completed in the released version to the extent originally prepared.
Confirmed in the assets
Standalone storytelling module
The game contains a dedicated runtime Data Layer Storytelling_Serial_Killer directly in the main map, at the path /Game/Maps/MainMap/DataLayers/MainMap/Storytelling_Serial_Killer.
Its DataLayerType is set to Runtime. The story is therefore represented in the data as a runtime part of the main map, not merely as an editor-only organizational layer.
Several specially prepared corpses were created specifically for this story.
The assets use a hunting knife and bloody materials.
Five separate variants of the killer's bloody symbol survive.
There is an actual readable item ItMs_Scroll_SerialKiller.
A very late addition to the game
Data associated with this story was added to the game on May 19, 2026, less than two weeks before the release of Gothic 1 Remake. The Serial Killer storyline therefore belongs to the content that was still being worked on very late in development.
Story in the game
Information in the game
Wrong shape. Wrong size.
None of them fit.
One pair left. Mine.
The text strongly suggests that the killer cut off his victims' ears while searching for the "right" pair. His final sentence exactly matches the cave scene, where he is found dead with his own ears cut off.
Another in-game clue
NPC small talk also mentions the incident
The incident is not confined to the document itself. NPC small talk in the world also refers to an unknown man who tried to cut off his own ears and had to be restrained by three men until he calmed down.
... tried choppin' off his own ears, he did. Three o' the lads pinnin' him down or he'd have done it ...
Unused content
A second document missing from the game
Present in localization • in-game item not found
The localization package contains another separate text signed by the same "L.". In the analyzed game assets, we did not find a second corresponding document for it.
I am so lucky to have found you. The other one is still in that pit, no doubt. Heavy as ever. Waiting for a flower that was never for him. Poor thing. He could have known, if he had looked up once.
You are not him. You see me. You draw me back.
When you return come find me. Let me draw you this time.
– L.
Conclusion
The Serial Killer is an active environmental story for which the game even contains a dedicated runtime layer in the main map. At the same time, clear traces of unfinished development remain. The current ending works on its own, while the second complete document in the localization data confirms that the prepared content was broader than what can actually be found in the game.
04
Inaccessible content
Xardas' Raven
The game files contain a separately prepared raven explicitly named after Xardas. It does not appear in the final game, but it was shown in a trailer released before launch. The data shows that this was not merely a renamed common crow: it has its own Blueprint, model, multiple textures, materials, and a full set of specific animations. Assets for the journal and monster list also remain.
Confirmed in the data
A dedicated raven variant
RavenXardas_bp is a dedicated Blueprint inheriting from the native class /Script/G1R.AmbientCharacter.
The Blueprint uses the special model SK_XardasRaven and has flight enabled through bCanFly = true.
The character receives a standard AI Controller, can be placed in the world or spawned, and is configured as invulnerable.
The model has its own black-and-red albedo texture, a separate normal map, an MRAOT map, an auxiliary PNG/ATE texture, a dedicated body material, and a separate eye material.
Morph targets for blinking and eye expressions also survive, so this is more than a static decorative model.
The data also contains several separate animation files created specifically for Xardas' Raven.
The supplied materials also show the raven referenced in the journal and monster list.
The mesh shares the skeleton and physics asset of the common crow, allowing the developers to reuse the base rig and physics.
Official pre-release material
Xardas' Raven in the official trailer
The raven actually appeared in the official Xardas Trailer before release, directly at Xardas' side. In the final version of Gothic 1 Remake, however, this game element is absent even though its models, textures, animations, and assets for the journal and monster list remain in the data.
Journal and monster list
Separate visual assets also survive
The data includes more than model and animation files. Xardas' Raven also has its own visual assets used for the journal and monster list, further confirming that it was prepared as a standalone game element with its own supporting data, not merely as an object created for a trailer shot.
Dedicated animation set
The raven had a complete ambient movement set
Fly2.6 s • root motionFly Away1.33 s • root motionLanding1.87 s • root motionJump1.33 s • root motionSquawking2.33 sIdle 016 sIdle 029.33 s
The supplied package contains no specific combat, quest, or interaction animations. The set therefore best matches an ambient creature intended to bring a specific scene to life.
In addition to the model and animations, visual assets for the journal and monster list also survive. Combined with its appearance in the pre-release trailer, this shows that Xardas' Raven was prepared as an actual in-game object, not merely as a concept or a one-off visual element.
Conclusion
Xardas' Raven was demonstrably prepared for the game as a standalone and fairly developed game element. It has its own model, multiple textures, materials, an animation set, and visual assets for the journal and monster list, and it actually appeared in a pre-release trailer. However, it is absent from the final version of Gothic 1 Remake. The available data does not demonstrate any special quest function or direct player interaction. The most likely explanation is that it was a prepared scenic or ambient element associated with Xardas that was removed from the final game before release.
05
Inactive feature
Tattooing
There is no need to dig deeply into source assets for this feature. The localization file contains dozens of lines directly describing the option to receive a tattoo after joining the Brotherhood as part of its initiation ceremony.
Confirmed by localization
Tattooing was meant to be part of joining the Brotherhood
The dialogue shows that joining the Brotherhood was supposed to unlock the option to receive a tattoo. This was not merely a cosmetic choice without context: characters describe it as confirmation of membership in the community and as a means to help "open the mind to the Sleeper."
The player can directly ask: About those tattoos ... Can I get one?
The NPC replies that the tattoo confirms membership in the community.
Special ink must be prepared before the tattoo can be applied.
The recipe requires darkshade, molerat fat and bloodfly sting.
The ink is meant to be produced in an alchemy laboratory and then handed over to the NPC.
The game data contains three prepared tattoo categories: Novice, Guru and Templar.
Selection from the localization data
The dialogue describes the entire process
I would need ink for the tattoo. So you'll have to make some.
That's what I said. Use the lab. All you need is darkshade, molerat fat and the sting...
I'm ready for my tattoo.
Then we shall begin.
That's it. Done. May the Sleeper speak to you.
Clue directly in the final game
NPC already mention tattooing
Dialogue that can already be heard in the current version of the game also points to the planned feature. Some NPCs ask the player:
Brother. When are you going to get your tattoo?
This line is another direct clue that tattooing was not merely an internal concept in the localization data, but was intended to be a real part of the player's life after joining the Brotherhood.
What we still do not know
The extent of character customization remains unclear
The localization does not yet reveal which specific NPC was supposed to perform the tattooing. We also do not know whether the player could choose the style, placement, or extent of the tattoo, or whether there was a single predetermined Brotherhood variant. The separate categories Novice, Guru and Templar also raise another question: it is not yet clear whether the tattoo was intended to expand or change gradually as the player advanced through the ranks within the camp.
Conclusion
Tattooing was clearly planned as a real feature tied to joining the Brotherhood, not merely as an NPC appearance detail. The localization describes unlocking the feature, obtaining the recipe, collecting ingredients, producing the ink, and the tattooing itself. The option is not available to the player in the final game.
06
Inactive feature
Head Shaving
The same group of localization lines reveals a second part of the Brotherhood initiation ceremony: the player was meant to be able to shave their head and visually confirm their acceptance into the community.
Confirmed by localization
Part of the symbolic initiation
NPCs explain the shaved head as a sign of the Brotherhood's shared bond and belonging. The dialogue then offers the player the option to take part in this custom, but a necessary tool must first be obtained.
The player can ask why Brotherhood members are bald.
The NPC describes shaving as a symbol of their bond and of drawing closer to the Sleeper.
After agreeing, a requirement to obtain a razor blade.
After bringing the razor blade, the dialogue continues with the shaving itself.
The feature is directly tied to the ceremony and visual membership in the Brotherhood.
Selection from the localization data
The player first had to obtain a razor blade
You're all bald ...
Yeah. It's a sign of our bond. As a community. We're getting closer to the Sleeper...
It's mainly symbolic, sure, but who knows ... You wanna join in?
And here's the catch... you need a razor blade. Harder to come by than you'd think...
I've got a razor blade. Let's do this!
All right then, off with that stuff.
What we still do not know
What exactly was meant to be shaved
The surviving dialogue does not allow us to determine whether the feature applied only to the hair on the head or whether the player could also choose to shave facial hair. As with tattooing, the specific NPC who was supposed to perform the customization is also unknown.
Conclusion
Head shaving was not merely an artistic characteristic of Brotherhood members. The localization data shows a prepared player interaction, the choice to undergo the ritual, a separate requirement to find a razor blade, and the subsequent customization. Like tattooing, however, this feature is not accessible to the player in the final game.
07
Inaccessible content
Female Orcs
Another major finding is 271 dialogue entries related to female orcs. They are virtually absent from the current game. The exception is one specific shaman, who uses her own separate dialogue branch. The remaining discovered dialogue therefore appears to belong to additional characters or content that is not accessible in the current version of the game.
Confirmed directly in the assets
This is more than a handful of unused dialogue lines
In the folder Assets/Characters/Orcs/Female we find a complete separate branch of female orc assets. At its core is a full SkeletalMesh SK_OrcF_Base, a dedicated skeleton, ragdoll physics, cloth physics, and separate materials and textures for the head, torso, and legs.
SK_OrcF_Base contains 5 LOD levels and separate material slots for the head, torso, legs, eyes, and hair.
The model uses dedicated textures Head, Torso and Legs, each with albedo, normal, and MRAOT maps. The torso also has its own detail mask.
The skeleton contains 137 bones, including bones for hair, shaman headgear, weapons, holsters, and other accessories.
There are 105 facial morph targets for the eyes, eyebrows, jaw, mouth, nose, and neck. The model was therefore also prepared for detailed facial animation.
Two dedicated physics assets are included: SK_OrcF_ragdoll_Physics and SK_OrcF_cloth_Physics.
The skeleton declares compatibility with the male orc skeleton, allowing the existing animation system to be shared or retargeted.
Localization evidence
271 dialogue entries point to additional female characters
The localization file currently contains 271 dialogue entries with the prefix gvl_g1r_voice20_orcf_. The orc shaman who actually appears in the final game uses only a tiny fraction of this amount and also has her own separate dialogue branch. The overwhelming majority of these 271 entries therefore remains unused in the current game.
Together with the complete female model, this is strong evidence that additional female orcs or a broader part of orc society existed during development but did not make it into the currently accessible game. The supplied data does not yet reveal how many characters were planned, where they were meant to appear, or what roles they were intended to have.
Visual appearance
The textures confirm a separately created female model
The base textures clearly model female anatomy and are not merely a recolored male orc. Both the torso and head have their own structure and dedicated texture sets. The base body textures also contain no complex clothing; this was likely handled through additional meshes, materials, or equipment placed on top of the base body.
Conclusion
Female orcs are among the most convincing examples of content that was developed much further than the current game suggests. Alongside 271 localization entries, there is a complete female SkeletalMesh, a dedicated skeleton, detailed facial animation, physics, LODs, and separate textures for the full body. A single shaman in the final game does not explain this volume of data. The most likely explanation is that development originally included additional female orc characters or a broader orc society that is not currently accessible to players.
08
Partially inaccessible content
Old Camp Arena
In the final game, the Old Camp arena is used only to a very limited extent, mainly during the quest related to joining the Old Camp. Dialogue, the prepared environment, an unused audio track, and an official trailer all indicate that it was originally intended to be a much livelier location used repeatedly.
Clues directly in the final game
Scatty promises the player more fights
Arena manager Scatty already has dialogue in the current version of the game in which the player can ask whether they can bet on a match. Scatty replies that no fights are currently taking place, but more should happen within a few days and word will definitely reach the player. The branch ends there, however, and no further matches are ever unlocked.
Above the arena itself is a large prepared room for taking bets, which currently has no practical use.
A large winch intended to operate the gates stands inside the arena. In the final game it is only part of the environment and cannot be interacted with.
The localization data also contains a challenge from an unknown NPC telling the player to settle their score in the arena.
The current game therefore directly references betting and additional personal fights, but the follow-up system is not accessible to the player.
Unused audio file
Old Camp Arena, combat event
In the folder oldcamparena/events/ there is a separate audio track oldCampArena_combat_MASTER.wav, which is not used in the current game. The recording is approximately 50 seconds long and its name directly ties it to a combat event in the Old Camp arena.
Web copy of the original file oldCampArena_combat_MASTER.wav.
Technical evidence in the assets
Dedicated arena mechanism model
The game data directly contains the asset SM_ArenaMachine_01 in the folder Old_Camp/General. It is a separate StaticMesh with its own physical and navigation collision. Among other things, it uses the materials MI_Rope_01W and MI_MainDoorMachine, which matches the rope-driven winch mechanism physically present in the arena.
The export itself contains only the static model and collision. The script or Blueprint responsible for operating it and handling player interaction is missing.
Official pre-release material
The trailer showed gameplay that is missing from the game
The official trailer Welcome to the Old Camp from 2023 directly showed a fight against a monster in the arena. In the released version, however, the player never gains access to similar repeatable monster fights. Combined with Scatty's betting dialogue and the unused combat track, this is another strong indication that the arena was meant to have broader gameplay use.
Conclusion
The Old Camp arena was very likely being prepared as a repeatedly used space for additional matches, fights against NPCs and monsters, and a betting system. The final game retains only limited use during the admission quest, Scatty's dialogue promising future matches, the prepared betting room, an inactive gate-control winch, individual localization clues, and unused audio. The available data does not yet safely confirm the exact scope of the original system, for example whether tournaments were also planned.
09
Partially accessible content
Toy Maker
In the cellar beneath the ruins of a village in the forest, players can already discover a wooden toy maker's workshop, his note, and several unfinished creations that can be collected. The game data, however, shows that this scene was prepared as a standalone storytelling module and was being worked on very late in development.
Confirmed in the assets
Standalone storytelling module
The game contains the runtime Data Layer Storytelling_Toy_Maker in the main map.
There is a dedicated readable item ItMs_Scroll_ToyMaker.
Six separate collectible items survive ItMs_ToyMaker_000, 001, 005, 007, 009 and 013.
Each toy has its own World Blueprint, Visual Blueprint, item definition in /Script/Angelscript and its own inventory icon.
For the toy visuals, the developers reused selected models from the Xardas_Miniatures set and turned them into actual game items.
Very late WIP localization
The texts are dated May 19, 2026
The surviving localization key text_wip_koyhwbi_20260519_165835 points to May 19, 2026, less than two weeks before the game was released. The same time block contains several consecutive lines from the Toy Maker's note. We have already seen the same late date in part of the Serial Killer content.
“A deer today, with bent legs. Like the first one we made together.”
“You will be bigger now. Too big for wooden animals.”
“The guards think I gather wood for the camp. Let them. The best pieces are for you.”
Conclusion
The Toy Maker story is partially accessible in the final game: the player can discover his workshop, read the note, and collect several unfinished toys. The data nevertheless treats it as a separate runtime storytelling layer, and the individual toys exist as real game items. Combined with WIP localization dated May 19, 2026, it looks like another story module that may only have been partially completed before release. The available data does not yet confirm whether the collected toys were meant to have any further use.
10
Inactive mechanic
Carry Weight Limit
In the final game, the player can carry a virtually unlimited number of items. The game data, however, shows that development once included a much more elaborate system for inventory weight, maximum carrying capacity, and encumbrance.
Confirmed by localization
Carry capacity was tied to the Toughness attribute
The localization data contains a dedicated attribute Toughness and its tooltip directly explains the intended function. A higher value was meant to increase how much the character could carry. Exceeding the carrying capacity was not simply meant to block picking up more items, but to hinder the player's movement.
Toughnesscharacter attribute
→
MaxCapacitymaximum carry capacity
→
Encumbrancemovement penalty
Prepared user interface
The game had a dedicated weight widget
T_Icon_Weightsurviving inventory weight icon
The inventory interface still contains the dedicated W_ItemWeight widget. Its SetTextValues function works with three separate values: CurentWeight, MaxCapacity, and ItemWeight.
The widget can display total weight in the format {current}/{total} and use WidgetSwitcher_WeightNumber to switch between the character's total carrying capacity and the weight of a specific item.
What the data shows
It was more than a simple inventory limit
Each item could have its own ItemWeight.
The inventory tracked the current total weight CurentWeight.
The character was meant to have a separate maximum capacity MaxCapacity.
The Toughness attribute was meant to progressively increase maximum carry capacity.
According to the localization, encumbrance was meant to directly hinder character movement.
The system has its own UI widget and a dedicated weight icon.
Conclusion
The carry weight limit was not merely an early idea. The game still contains UI for the weight of individual items and the whole inventory, a maximum character capacity, a dedicated icon, and localization describing an attribute intended to directly affect carrying capacity. The system is inactive in the final game. The available data does not yet confirm whether the complete runtime logic that was supposed to apply a movement penalty after exceeding the limit still survives.
Theory for the future
An ideal foundation for a major expansion?
Fishing, unfinished stories, the fully prepared Xardas' Raven, player tattooing and shaving, extensive female orc data, the Toy Maker story, the inactive carry-weight system, and the unfinished use of the Old Camp arena all show that the Gothic 1 Remake files still contain a surprising amount of content that is either inactive or only partially accessible.
Purely in theory, this gives the developers an excellent foundation for a larger DLC or major content update that could significantly expand the current world without starting entirely from scratch. Some of the systems, models, story clues, and dialogue data already exist at various stages of development.
Important: this is not confirmation that a DLC is in development. We found no evidence in the analyzed data that such an expansion is actually being made. This is only a theory based on the amount of already prepared but currently unused content.
Discussion
The discussion is still waiting for its first comment.
Project support
Support website operation
If this website helps you, you can voluntarily contribute to its operation and the continued development of translations. Thank you to everyone who chooses to support the project. Every contribution helps keep the website available.
Discussion
The discussion is still waiting for its first comment.