Closed SirStig closed 1 year ago
Think the Post Deploy files should be put into a Post Deploy folder on the desktop as to not crowd it.
Parenthesis are a bit weird in file names, so I'd do this:
Should be clear enough.
Think the Post Deploy files should be put into a Post Deploy folder on the desktop as to not crowd it.
Also forgot to add the falloutnv-pre-deploy.desktop to the desktop
Parenthesis are a bit weird in file names, so I'd do this:
* keep the skyrim SE one the same, so it won't break existing shortcuts * name the skyrim LE one skyrimle-post-deploy.sh and skyrimle-post-deploy.desktop
Should be clear enough.
Sure, will do!
Think the Post Deploy files should be put into a Post Deploy folder on the desktop as to not crowd it.
Desktop is fine for now, people can just delete shortcuts they aren't using.
Think the Post Deploy files should be put into a Post Deploy folder on the desktop as to not crowd it.
Desktop is fine for now, people can just delete shortcuts they aren't using.
True, was thinking of changing everything to Symlinks, but not sure how much that would break anything.
True, was thinking of changing everything to Symlinks, but not sure how much that would break anything.
Yeah, I was playing around with symlinks a bit too for plugins.txt and loadorder.txt, instead of copying. Works well if you know the paths, but not sure how I'd handle migrating people over to it yet. And you still sort of need a post-deploy anyway to set up the script extenders.
These post-deploy scripts seems easier for people to understand too, so I'll probably leave it alone for now.
True, was thinking of changing everything to Symlinks, but not sure how much that would break anything.
Yeah, I was playing around with symlinks a bit too for all of this. Works well if you know the paths, but not sure how I'd handle migrating people over to it yet.
These post-deploy scripts seems easier for people to understand too, so I'll probably leave it alone for now.
Honestly, never really bothered me running the scripts. Takes two seconds. Symlinks would be easy in theory but would require finding and checking where the files are, if they are at all. Would have to run the script once anyway.
Easiest thing to do would be to add a script that runs when you launch vortex, checks for games that are installed, creates symlinks for them if they don't exist.
Additions:
Added Skyrim (LE) post deploy and .desktop.
Added Fallout 3 post deploy and .desktop.
Changes:
Fixes:
Notes:
Have not had anytime to download these three separate games and test everything out but in theory everything should work properly, Fallout 3 if it has any extra files as Fallout NV will not work then but never modded any of the Fallouts so I have no experience in this field.