-
Notifications
You must be signed in to change notification settings - Fork 4
Plugin packaging
Gratt-5r2 edited this page Apr 11, 2022
·
4 revisions
Your product can be considered completed and high-quality if it assembled with the rules described below.
- Use understandable names for your plugin. The name should show the meaning of the plugin.
- Place your
.dllto theGothic\System\Autorun\directory. This directory guarantees that your plugin will be started with the Engine. All plugins in the Autorun directory are sorted automatically by dependencies. - Pack you
.dllplugin and all resources in the.vdfvolume.- If you create a standalone plugin, use the
Gothic\Data\Plugins\directory to place your volume. - If you create a plugin for some modification, place the
.dlland all resources in the.modfile of this modification. You can use one of exists.modvolumes, or use an individual.modvolume.
- If you create a standalone plugin, use the
- The name of the volume must match the name of the
.dll.- If you have a several
.dlls, must match the main module of your project. - If other
.dlls relate directly to this project, these must have the same root of the name.
- If you have a several
⠀
← Home | Next page →
- Introduction
- Project hierarchy
- Default functions
- Build options
-
Gothic API
- Base objects
- Models and visuals
- Static and interactive objects
- Animations
- Interface
- Scripts
- Worlds
- Renderer
- Other
- User API
-
Union API
- Hook
- Hook Functions
- Array
- ArraySorted
- Map
- MapArray
- String
- Unicode string
- UTF-8 converter
- RowString
- Console
- Logger
- Message
- Thread
- Event
- Semaphore
- ThreadLocker
- Crc checker
- Options
- Timer
- Union
- VDFS functions
- VirtualFile
- Hooks
- dynamic_cast patch