Warband Module System 1.166

by Lav·v1.166·Updated 2019-01-20

Warband Module System 1.166 This is the module system for Native 1.165 with many different fixes and improvements

About this mod Machine translation

Warband Module System 1.166 This is the module system for Native 1.165 with many different fixes and improvements

Warband Module System 1.166 (with tweaks and giggles)

(Official thread on the Taleworlds forum)

This is essentially a vanilla module system with many fixes and tweaks:

*) The file header_operations.py has been completely replaced with a correctly documented version.

*) Problem with (party_set_marshal {l}) operation has been fixed, Module System will accept either syntax.

*) The new 1.165 operations (try_for_prop_instances) and (try_for_players) are now correctly recognized as "depth increase" operations (this affects the compiler checking for unsafe failed operations and extra/missing (try_end)).

*) Temporary *.pyc files are no longer generated during compilation and folders are not cluttered on failed compilation attempts.

*) Info page references "ip_*" are now correctly recognized by the module system compiler and do not throw "unrecognized tag" errors.

*) Added a small tweak to module_info.py to provide a trailing slash to the export_dir constant if it was not available. Several possible options (commented out) are also provided for the export_dir setting.

*) It is now possible to add items with modifiers to the troop inventory directly in module_troops.py. For example, [(itm_item1,imod_rusty),itm_item2] will add rusty "itm_item1" and regular "itm_item2" to the army. The code used is a slightly modified version of "The_dragon".

*) Modifications to header_common.py to bring number, string and position registers up to reg127, s127 and pos127 respectively. Note that numeric and string registers with index 100 or higher cannot be used for string replacement (i.e. "You have {reg120} gold." Such a string will throw an error at runtime).

*) Modify header_item_modifiers.py to add information about hardcoded game effects of item modifiers and make the imodbit_* constants more readable.

*) Various modifications of header_items.py:

*) Item weight limit increased from 63.75 kg to 655.35 kg with an accuracy of up to 0.01 kg. Note that the game engine will round the displayed weight to the nearest 0.1 kg anyway.

*) Item miscellaneous parameters will no longer overflow into the hit point field, resulting in items with ridiculously high HP values ​​(albeit generally meaningless and harmless).

*) Project max_ammo value can now reach 65535 (compared to vanilla 255).

*) Two new flags for armor items: itp_replaces_helm and itp_replaces_shoes.

*) Modifications to header_skills.py that eliminate unintelligibly large numbers, extend know_*_# constants to include skill levels up to 15, and make it easier to change skill constants for mods with non-standard skill sets.

*) Modifications to header_troops.py to provide attribute constants for attributes in the (3..63) range.

*) Modifications to header_triggers.py, including detailed comments on trigger parameters and their effects.

Warband Module System 1.166 (with tweaks and giggles)

(official thread on the Taleworlds Forums)

This is essentially the vanilla Module System with a number of fixes and tweaks:

*) File header_operations.py has been completely replaced with properly documented version.

*) Issues with (party_set_marshal{l}) operation have been fixed, Module System will accept either syntax.

*) New 1.165 operations (try_for_prop_instances) and (try_for_players) are now correctly identified as "depth-increasing" operations (this affects compiler checks for unsafe can-fail operations and extra/missing (try_end)'s).

*) Temporary *.pyc files are no longer generated during compilation and won't clutter the folder in case of a failed compilation attempt.

*) Info page references "ip_*" are now correctly recognized by module system compiler and will not throw an "Unrecognized tag" error.

*) Added a small tweak to module_info.py which will provide a trailing slash to export_dir constant if it doesn't have one. Also provided several likely options for export_dir setting (commented out …

Install & use Install: follow the bundled instructions

  1. Unzip the archive from playbuff and read the bundled readme / instructions first.
  2. There is no universal mod manager for this game: some mods replace game files directly, some go into a game-specific Mods folder, and some need a game-specific community loader or tool first — follow the bundled readme.
  3. Place the files exactly as the readme says; mods with listed dependencies need those installed too.
  4. Launch the game to confirm it loaded; some games require enabling mods in settings or an in-game mod menu.

Install locations vary a lot between games and mods — the bundled readme is the most reliable guide.

File & checksum

Filename
Warband Module System 1.166这是Native 1.165的模块系统,具有许
File size
1.3 MiB