use the same naming conventions for directories and files as the vanilla units.update ui/mods/com.pa.legion-expansion/global.js.update pa/ai/unit_maps/imperial_legion.json.create sea versions when needed in pa/units/sea/.for all Legion units that can build change buildable_types to "CUSTOM1 & ( existing_buildable_types )".l_type_unit_adv (although some are different eg dox) prefix all Legion units directories and filenames with l_.Vanilla units with buildable_types must be adjusted to ignore Custom1. Create a commit that describes the update.Check all changes are as expected using git diff.Inspect output and check for errors or warnings.Create release from master and tag with version number.Bump the version number in src/base_modinfo.json.The script in src/install_prod.py depends on those locations. After cloning the repos you should have a layout like this: The first step is to make sure you have cloned the client and server mods to a Mods by updating the submodules we have for those repositories. The src/install_prod.py script automates updating the the client and server In order to update the Legion-Expansion release, the HOTFIX-x.x.x - a critical fix for a current release forks from MASTER and merged into MASTER and DEVELOP MASTER - release candidate can be forked to HOTFIX-x.x.x used to create release versions never to be directly committed toĭEVELOP - development forked to FEATURE- nameįEATURE- name - a feature which is still in development merged into DEVELOP on completion Our branch structure is based on the git-flow model:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |