I'm working on adding support for the newly-released (on Steam anyway) standalone Skyrim total-conversion "Enderal: Forgotten Stories".
My WIP forks:
1) Doing everything on master branches in my forks. Assuming that's fine.
2) Is it OK for me to release a (obviously unofficial and 100% unsupported) build of Vortex for the few players of Enderal to use until Vortex official releases it (I'd just open a thread of Steam forum for the game, and I'd definitely remove it once official comes out)? They can be a good test bed for sure - as we don't have any mod-manager for it at all right now. If that's OK, let me know if there's any flags or something to change to avoid spamming false error reports
3) Regardless of #2 above, I still want to use it personally - Is master branch relatively stable or should I roll-back to a certain commit for testing? I can't see any "release" branch nor tags so I'm not sure.
4) Made a thread on the Steam forums linking to this thread (mostly so others are aware and don't do duplicate/redundant work), assuming that's OK. It's at https://steamcommuni...62523078419686/
Right now I'm still going through and testing/working on everything as I go but I'll commit early and often of course - I'm mostly working on trial and error here since this is a unique situation - ability to install Skyrim mods from Skyrim nexus in a non-Skyrim game - so obviously it's a bit more than just copying and adjusting the skyrim entries spread all over the extensions (e.g. I'm not sure how to handle fomod yet - I'm going to test that when I get to it). And of course because I'm completely new to Vortex.
BTW, I had the popular...
...error when running yarn install command. I found the solution was to run...
npm install --global --production windows-build-tools
...which automatically installed Python 2.7 x64 and some extra Visual Studio 2017 stuff which was obviously missing in the repo readme (about 1GB worth). Maybe worth updating.
Edited by dconnolly, 17 February 2019 - 12:26 AM.