-
-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting (EN)
If a patch does not seem to work properly, this might be due to incompatibilities. If you can manage to get into the game, first try to confirm that Ninja is active (see Confirm That Ninja is Active) and if the patch is loaded (see Confirm That a Patch is Loaded).
If the game crashes or closes down before that, start the zSpy.exe application (usually in [GothicDirectory]\_work\Tools\zSpy\
or [GothicDirectory]\System\
). In Options → Logging, add checkmarks for all categories (information, warnings, faults and critical errors).
Ninja will detect when the zSpy is running and enable logging automatically. Wait for the crash to happen, save the log (File → Save as...) and post it in this forum thread along with information about the used mod and any other active patches. Help is on the way!
To confirm that Ninja is active, type Ninja
into the default in-game console. If Ninja is correctly installed, the current version and build information should be displayed. To confirm the integrity of Ninja you can compare the CRC32 checksum with these valid ones listed in Checksums.
If the game is installed in the program files directory, Ninja requires administrative privileges to properly run.
To confirm, that a patch is loaded, type Ninja
into the default in-game console. Below the version information of Ninja, all loaded patches will be displayed. If the patch in question is not displayed, it may either be installed incorrectly or it is not compatible with the mod you are playing.
Entering Ninja PatchName
into the console will give you a brief description about the patch named PatchName
.
Click to expand and view the explanations.
One of your patches is outdated (Ninja <= 1.2)
or Outdated patch found (Ninja < 2)
One of the installed patches uses an old version of Ninja and is thus outdated. Update or remove that patch to proceed.
Ninja was attached too late (after VDFS)
Ninja is not being loaded correctly. Reinstalling Ninja may fix the problem.
If using Union, make sure Ninja.dll**
is added to the PluginList
in SystemPack.ini
(or Union.ini
before Union 1.0h) and Union is updated to version 1.0e or higher. Under normal circumstances, this entry is created automatically when installing Ninja. When using Spine, it is also done automatically and should not be done manually.
Another cause for this problem is when Gothic is not started in the correct working directory. If you are starting Gothic from a link on your desktop, make sure that the path to the [GothicDirectory]\System\
directory is entered under "Start in".
Version mismatch of [Ikarus/LeGo]. Ikarus/LeGo must not be contained in any patch.
There is a malformatted patch installed. Remove the patch to continue.
Version mismatch of [Ikarus/LeGo]. Game: [x], Ninja: [y]
Your Ninja version is outdated. Install the newest version found here.
Introduction
Virtual Disk File System
Formats
Single File Formats
Collected File Formats
Limitations to Overcome
Scripts
Animations
Output Units
Solution
Implementation
Patch Structure
VDF File Tree
VDF Header
Patch Template
Patch Validator
Inter-Game Compatibility
Inject Changes
Daedalus Scripts
Overwriting Symbols
Naming Conventions
Preserved Symbols
Initialization Functions
Init_Global
Menu Creation
Ikarus and LeGo
Initializing LeGo
Modifications to LeGo
PermMem and Handles
Daedalus Hooks
Inserting NPC
Disallow Saving
Helper Symbols
NINJA_VERSION
NINJA_MODNAME
NINJA_PATCHES
NINJA_ID_PATCHNAME
NINJA_SYMBOLS_START
NINJA_SYMBOLS…PATCHNAME
Common Symbols
Localization
Animations and Armor
Output Units
Other Mechanics
Remove Invalid NPC
Safety Checks in Externals
Preserve Integer Variables
Detect zSpy
Incompatibility List for Mods
Applications and Examples
Add New NPC
Set AI Variables
Add New Dialogs
Add New Spells
Add New World
Translation Patch
Installation
Requirements
Instructions
Troubleshooting
Is Ninja Active
Is Patch Loaded
Error Messages