Ignore default text files

[Bladehawke]

While it's convenient for the app to try to select all text files for activating, steam_appid.txt, sfse_whatsnew.txt, and sfse_readme.txt probably shouldn't be selected :)

[rfuzzo]

Hi, yeah thanks. But it’s a bit hard to check what is a Commandfile and what isn’t :D I guess could check for common commands but not sure

[LaundryHamper]

I might have a sort-of workaround for this - I installed a few of JustAnOrdinaryGuy's mods and for whatever reason he's placed his command .txts inside Starfield\Data\. The game happily runs bat "Data\whatever" as long as the directory and filename are within quotes, but there's no way to make sf_gmst_editor see those files. Easy to copy them across manually, but maybe not obvious to some users.

Maybe you could include a Starfield\GMSTs\ folder in the .zip, use that instead of using \Starfield\ as the source for commands to copy to the .ini - have an "Import" button open a file browser which would let the user select .txt files from other directories, and make copies of them in \GMSTs\. Copy all the .txt files already in \Starfield\ on first launch, then you can allow files from the editor's directory to be deleted from within the editor without risking getting rid of a load of user settings or breaking the Steam installation or whatever.

If any modder making a mod which needs to run an on-launch command wanted, they could include a \GMSTs\ folder with second copies of their .txts - that wouldn't break their mod for anyone not using the editor, but would make it appear pre-imported for anyone using it. And if they mention the editor in the description of their mod, and convince people to use it, they might get fewer comments from users who think their install is broken because remembering to run a command to make the mod work is confusing/requires reading, and manually adding sStartingConsoleCommand to the .ini is slightly more confusing, and adding multiple commands in a string is slightly even slightly more confusinger.

You could place dividers between commands from separate mods, maybe by using subfolders (\GMSTs\WhateverMod\whatever.txt), which could work as expandos - I have NAS.FX installed, which lets you apply the photo mode's filters during ordinary gameplay. It's got 14 separate command .txts (and a readme, which also shows up in the editor) so it makes the list of files a huge mess. It'd be nice to make those ones disappear temporarily. Also, though the effects in that mod have descriptive names, the command files are named "NASfx05.txt", etc, so that they're easier to enter in the console. I think that underscores are the only punctuation mark you can use without wrapping the filename in quotes, even ampersands cause an error - it'd be safest to just wrap every filename in quotes by default to be safe.

Unfortunately none of this would properly solve the other mess issue, which is that there're 84 items in my \Starfield\ folder by now, so I've to scroll five miles to get to StarfieldCustom.ini every time I want to double-check it, which (because paranoia) I always do 😅

I think the editor is straightforward enough, and so useful since so many mods need to rely on commands for now, that everyone installing mods should be using it: it should be as mandatory as installing SFSE or putting "don't forget to do the bInvalidateOlderFiles=1 thing!" in the description of every mod for the game forever...Maybe Nexus will eventually buy you out and integrate the whole thing into Vortex's code, like all the script extenders 😛