Mod system proposal

= System structure +

There main concepts of modding system are modules and mods of two kinds: extension packages and conversions.

Modules

A module refers to part of the engine that handles optional mechanics. Currently considered modules are:

• Stack experience
• Mithril (unsupported)
• Stack artifacts (unsupported)
• Commanders (unsupported)

Modules may be prerequisites for actual mods. The mod may require one or a number of modles to be active before it is avaliable to use. The module can be active or inactive. Activation of module in game options automatically activates or deactivates all related mods, assumin they were turned on in first place.

Packages

Packages are made of Python scripts. Teir purpose is to add new conetnt to the game, such as creatures or artifacts. Packages may be dependent of modules and other packages with version greater or equal of certain number.

All packages are versioned, with version being an integer. All modders are requested to bump a version number with each update.

Conversions

Conversions are also made of Python scripts. Alter original objects and behaviour of the game. They may be content replacement, alter mechanics or change graphics and sounds.

Scripting

The proposed scripting language is Python thanks to if popularity and wide array of possibilities.

Python functions use high-level callback functions of the VCMI engine to perform basic game actions or access modding engine.

ERM scripts

To maintain compatibility with old WoG mods, all ERM functions have to be mapped into new set of Python functions. This mapping may not and will not be 1-to-1 due to acrhitecture of VCMI mechanics. Also, some unsafe functions like direct memory access will be unsupported.

ERM scripts are given their own memory space, which is equivalent of variable space of original ERM.