-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for extra files. #149
Comments
Just a heads up, the Portable/Installer Flag has not been released yet, and I recommend trying autodetection first before manually using those flags to override. You can refer to: Phalcode/gamevault-app#18 for more details. The usual If there is a package.json like in #148 or an Extras folder as proposed here in the same folder where the archive is located, it will be detected and utilized. This way, the file structure would look like this:
What do you think? |
That looks about right to me, the coolest possibility is creating some sort of redistribution format that people could use for distributing OSS games for instance. |
When designing this, it could be good to follow Plex's model of "media in their own folders" as being preferred and the primary way that GameVault recognizes its media. https://support.plex.tv/articles/naming-and-organizing-your-movie-media-files/ When you have a bunch of extras, mods, updates, etc, it could be good if the primary index of a game is the folder, and then there's certain files inside, found by inference (the only .zip file in a folder is probably the game) or by filename (*-install.zip is the installer, and pg828271-Manual.pdf is the game manual, etc), that GameVault then adds to the entry for the game. Sometimes a game will come with a lot of extra things like trailers, artwork, manuals, guides, cheats, soundtracks, etc, and we don't expect GameVault to handle them all, but even if not all media in the folder is recognized or used by GameVault, it's very handy to keep them together in our own file systems, rather than having to split them out to somewhere else. I'm saying this here because I'm not in favor of a package.json format, but prefer Plex's filename tags to identify media. That seems easier to manage, but that might just be me. |
You can call the file whatever you want because we only determine it by the Game Archive inside of it, additional files are in seperate subfolders inside of the game folder /files/Game 4 (2022).zip
/files/DoesntMatterHowYouNameIt
/DoesntMatterHowYouNameIt/Game 5 (2022).zip <- determines what game this is
/DoesntMatterHowYouNameIt/package.json #optonal configs and so on
/DoesntMatterHowYouNameIt/Soundtrack/ #only contains soundtrack
/DoesntMatterHowYouNameIt/Trailers/ #only contains trailers
/DoesntMatterHowYouNameIt/Manual/ #only contains manual
/DoesntMatterHowYouNameIt/Extras/8k-wallpaper.png #misc GameVault client should then offer you a small file browser / player later that you can retrieve those data from. We're not sure about the details yet though. |
+1 about this functionnality, the most important for me. Maybe be with a function for ignoring some files or subfolders in games folder ? |
Is your feature request related to a problem? Please describe.
It would be nice if we could store extra files alongside game archives.
Describe the solution you'd like
I'm not sure if I'm organizing things as expected but currently I have my games organized like so.
<GameTitle>/<GameTitle>(<GameVersion>)(<Portable/Installer>)(<GameYear>).ext
I would like to see the ability to store the extras, or however you want it titled alongside the archive and then serve those in a subpage of the game library page. Something along these lines.
Describe alternatives you've considered
Right now I'm just putting non-archived files in an Extra folder so the application doesn't pick them up.
The text was updated successfully, but these errors were encountered: