SASTEP: Difference between revisions

From Step Mods | Change The Game
Line 25: Line 25:
**1: a function that will edit the metas after the installation is complete
**1: a function that will edit the metas after the installation is complete
*c: get a version control up and running
*c: get a version control up and running
==Semi Automated STEP Core Mod List==
follow the main STEP guide till [[STEP 2.A|STEP:Guide#2.A._Configuration]]

Revision as of 17:01, November 27, 2013

Semi Automatic STEP Tool[edit | edit source]

Milestones[edit | edit source]

Milestones for the proof-of-concept-tools that will set the base for a complete installation program/ MO plugin etc. Once we are done with betatesting there should be a reset to an alpha that will incorporate all (probably) separated tools into a unified codebase.

  • Alpha state:
  1. Define and assemble a list of all archives (filename and checksum) that'll be used for the STEP core installation (WIP)
  2. (parallel to #1) get a working tool that returns the changed filestructure as config file for MG's ASI.
  3. (needs #2)
    1. install all mods according to the STEP core guide (+ our definition of STEP core)
    2. run the tool from #2. Adjust the tool if necessary
    3. Milestone is reached once all config files for STEP core are completed.
  4. create a tool that installs STEP core in separate folders.
    1. A simple batch file (for now) will just copy them all together for testing / or we create a switch in the ASI tool
  5. Bundle it all in one toolkit / one downloadable zip file.
    1. documentation
    2. bugfixing, catch errors/exceptions
  • Beta state:
  1. let the community give feedback and suggestions.

later/not time critical, yet:

  • a: define how data should be imported into the wiki (filelists for each mod? file archive based?)
    • 1: import data into the STEP wiki; make it editable for mod authors
    • 2: create a query that returns data ready for our tool
  • b: MO metafile-write support (have to check if I already got this working)
    • 1: a function that will edit the metas after the installation is complete
  • c: get a version control up and running

Semi Automated STEP Core Mod List[edit | edit source]

follow the main STEP guide till STEP:Guide#2.A._Configuration