10-21-2021, 04:02 PM
I plan on using Game Actions to lump various ROMs from different consoles under one game entry (Wario's Woods NES and Wario's Woods SNES together, for example) in instances where the box art does not differ, just to reduce visual duplicate noise. Before I go about doing this, however, I'm wondering what the best method would be. I already have a number of Powershell scripts that point to the emulators I'd prefer, so I could just plop those into the {InstallDir} and use the language inherent to Playnite to refer to the scripts, which would be super easy to modify when I need to, *or* I can point to my emulators and use arguments from Playnite itself to accomplish what it is that I want to do. This might be my preferred method, just because I prefer as few windows involved as possible, but I can't find a way to easily access Game Action details outside of Playnite itself, so mass editing the directories would be a bit of a pain, whereas with a slew of Powershell scripts it would bas simple as find-in-files with Notepad++.
Is there an easy way to mass edit Game Action and other game metadata outside of the Playnite application, or should I stick with Powershell scripts?
I guess writing this out, I already know which path is going to be the most portable... Still, wouldn't mind some responses before I commit to something.
Is there an easy way to mass edit Game Action and other game metadata outside of the Playnite application, or should I stick with Powershell scripts?
I guess writing this out, I already know which path is going to be the most portable... Still, wouldn't mind some responses before I commit to something.