Jump to content
LaunchBox Community Forums

spiritedusual

Members
  • Posts

    75
  • Joined

  • Last visited

2 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

spiritedusual's Achievements

16-Bit Artificial Intelligence

16-Bit Artificial Intelligence (4/7)

20

Reputation

  1. Version 1.0.1

    10 downloads

    Project Merger Plugin for LaunchBox The Project Merger Plugin is a high-performance utility designed to integrate massive retro-gaming collections—including the eXo collections, C64 Dreams, and Flashpoint—directly into your LaunchBox library. Rather than moving or duplicating terabytes of data, this plugin utilizes symbolic links (symlinks) and surgical XML injection to make external collections behave as if they were natively installed within your LaunchBox directory 🛠 Requirements LaunchBox Version: 13.26 or higher If merging Flashpoint and you want the images then download the Flashpoint image archive from the flashpoint site (https://download.unstable.life/ultimate-direct/14_packed/) and extract them to your flashpoint directory. This is only required if you have Flashpoint Infinite. Flashpoint Ultimate comes with the images. ❓ Why This Plugin Exists When you know how Launchbox works the concept of merging installs is not difficult. However, it is a pain to do and can cause issues if you mess things up. I wanted a way to automate the process and merge the projects in to an existing launchbox install in a way that would not change the users existing library, be neatly organized, have a small storage footprint, and be non destructive to the original project files. 📂 Supported Projects The plugin is fingerprinted to recognize and process the following specific directory structures: eXo Collections: eXoDOS. exoDOS Lite, eXoWin3x, eXoWin9x, eXoAppleIIGS, eXoScummVM, eXoDREAMM, eXoDemoScn, and eXoIF. Can be merged in either individual projects or if you've already merged exo projects. C64 Dreams Flashpoint: Support for both Ultimate and Infinite. 📖 How to Use Extract the content of the archive to your /plugins/ folder. Download and follow the instructions to install/unpack your desired projects (exo, c64, and/or flashpoint). Start launchbox and go to the tools menu and select the plugin. In the plugin window browse to your source project folder. If you have multiple projects select the root folder that contains the project sub folders. The plugin will auto populate with the projects available for import. There is a "Dry Run" option enabled by default if you'd like to see get an idea of whats about to happen otherwise uncheck that option. Click start import. The plugin will create a backup of your parents and platform xml files prior to making changes. These can be found in the plugin directory. You will get a UAC prompt about half through the process. This is required to create symlinks. A full import of all the projects on a destination NVME takes about 10 minutes. If you run in to issues or want to remove a project the second tab is for you. You can get a very basic idea of what the condition of the install is in, repair it, or uninstall one or multiple projects. Additionally, If there is ever an update you simply update the project at the source and select repair on the second tab. 💻 How does it work? Retro Exo and C64 Dreams are simply just highly curated Launchbox libraries by themselves. They both utilize a custom project folders at the root of their Launchbox folders. With this in mind and remembering our goal of small storage footprint and wanting to keep the source intact we can move over dependencies and symlink anything else. In broard terms the games and media themselves are all still at their source while things like emulators and config files are copied over. You could technically play a game on exodos and then pick it back up where you left off on your merged launchbox folder. There are also dependent plugins for C64 Dreams and Retro Exo that get added in as well. I include these in the plugin folder because depending on which version of the project you are importing you may have an out of date version so the plugin contains the most up to date for you. Flashpoint is a little different. It looks similar to Launchbox but it is not Launchbox thus we must convert it to something Launchbox can understand. There are over 200k titles in Flashpoint. The plugin scans the source Flashpoint directory finds the sql database and converts it in to a Flashpoint.xml. It does the same for the playlist json files converting them to xml files. Additionally, the images folder is nothing like what Launchbox needs. Thus it finds all images in the Flashpoint folder and creates symlinks of them to your destination Launchbox directory. Finally, we extract ClifP from the plugin folder to bridge Flashpoint and Launchbox and actually run the games. To get the archive imported without conflicting with the users current library we rename the platforms to identify them as purely the project they represent, ie MS-DOS = eXoDOS, AppleIIGS = exo AppleIIGS, etc... Additionally, to keep it clean we create "master platform categories" such as "Retro Exo" and nest all the projects/platforms under the master platform category. IE: Retro Exo (Master Category)>eXo DOS (Project Category)> "exo dos platform and playlists go here". The plugin does all the xml injections and edits in the background. ⚠️ WARNING Flashpoint Scale: Flashpoint is incredibly resource-intensive, featuring approximately 200,000 titles and nearly 500,000 images. It's recommended you use an SSD as your destination Launchbox install for best performance. StableBit DrivePool Incompatibility: During development, it was identified that StableBit DrivePool does not handle large volumes of individual files and symbolic links effectively. Attempting to use this plugin on a pooled drive can and will cause system crashes that wont resolve after a restart. I spent about 24 hours in windows recovery and physically unplugging drives to get my system to boot again. Please ensure you are targeting a standard physical drive to maintain system stability. A final word on compatibility. While I tested several games across all the projects during the course of development I cannot guarantee that this is truly 100% working. Thus any and all feedback is appreciated. Eventually I plan on creating a custom media pack for this plugin so everything has, icons, clear logos, and videos.
  2. C64 Exo Flashpoint Merger View File Project Merger Plugin for LaunchBox The Project Merger Plugin is a high-performance utility designed to integrate massive retro-gaming collections—including the eXo collections, C64 Dreams, and Flashpoint—directly into your LaunchBox library. Rather than moving or duplicating terabytes of data, this plugin utilizes symbolic links (symlinks) and surgical XML injection to make external collections behave as if they were natively installed within your LaunchBox directory 🛠 Requirements LaunchBox Version: 13.26 or higher If merging Flashpoint and you want the images then download the Flashpoint image archive from the flashpoint site (https://download.unstable.life/ultimate-direct/14_packed/) and extract them to your flashpoint directory. This is only required if you have Flashpoint Infinite. Flashpoint Ultimate comes with the images. ❓ Why This Plugin Exists When you know how Launchbox works the concept of merging installs is not difficult. However, it is a pain to do and can cause issues if you mess things up. I wanted a way to automate the process and merge the projects in to an existing launchbox install in a way that would not change the users existing library, be neatly organized, have a small storage footprint, and be non destructive to the original project files. 📂 Supported Projects The plugin is fingerprinted to recognize and process the following specific directory structures: eXo Collections: eXoDOS. exoDOS Lite, eXoWin3x, eXoWin9x, eXoAppleIIGS, eXoScummVM, eXoDREAMM, eXoDemoScn, and eXoIF. Can be merged in either individual projects or if you've already merged exo projects. C64 Dreams Flashpoint: Support for both Ultimate and Infinite. 📖 How to Use Extract the content of the archive to your /plugins/ folder. Download and follow the instructions to install/unpack your desired projects (exo, c64, and/or flashpoint). Start launchbox and go to the tools menu and select the plugin. In the plugin window browse to your source project folder. If you have multiple projects select the root folder that contains the project sub folders. The plugin will auto populate with the projects available for import. There is a "Dry Run" option enabled by default if you'd like to see get an idea of whats about to happen otherwise uncheck that option. Click start import. The plugin will create a backup of your parents and platform xml files prior to making changes. These can be found in the plugin directory. You will get a UAC prompt about half through the process. This is required to create symlinks. A full import of all the projects on a destination NVME takes about 10 minutes. If you run in to issues or want to remove a project the second tab is for you. You can get a very basic idea of what the condition of the install is in, repair it, or uninstall one or multiple projects. Additionally, If there is ever an update you simply update the project at the source and select repair on the second tab. 💻 How does it work? Retro Exo and C64 Dreams are simply just highly curated Launchbox libraries by themselves. They both utilize a custom project folders at the root of their Launchbox folders. With this in mind and remembering our goal of small storage footprint and wanting to keep the source intact we can move over dependencies and symlink anything else. In broard terms the games and media themselves are all still at their source while things like emulators and config files are copied over. You could technically play a game on exodos and then pick it back up where you left off on your merged launchbox folder. There are also dependent plugins for C64 Dreams and Retro Exo that get added in as well. I include these in the plugin folder because depending on which version of the project you are importing you may have an out of date version so the plugin contains the most up to date for you. Flashpoint is a little different. It looks similar to Launchbox but it is not Launchbox thus we must convert it to something Launchbox can understand. There are over 200k titles in Flashpoint. The plugin scans the source Flashpoint directory finds the sql database and converts it in to a Flashpoint.xml. It does the same for the playlist json files converting them to xml files. Additionally, the images folder is nothing like what Launchbox needs. Thus it finds all images in the Flashpoint folder and creates symlinks of them to your destination Launchbox directory. Finally, we extract ClifP from the plugin folder to bridge Flashpoint and Launchbox and actually run the games. To get the archive imported without conflicting with the users current library we rename the platforms to identify them as purely the project they represent, ie MS-DOS = eXoDOS, AppleIIGS = exo AppleIIGS, etc... Additionally, to keep it clean we create "master platform categories" such as "Retro Exo" and nest all the projects/platforms under the master platform category. IE: Retro Exo (Master Category)>eXo DOS (Project Category)> "exo dos platform and playlists go here". The plugin does all the xml injections and edits in the background. ⚠️ WARNING Flashpoint Scale: Flashpoint is incredibly resource-intensive, featuring approximately 200,000 titles and nearly 500,000 images. It's recommended you use an SSD as your destination Launchbox install for best performance. StableBit DrivePool Incompatibility: During development, it was identified that StableBit DrivePool does not handle large volumes of individual files and symbolic links effectively. Attempting to use this plugin on a pooled drive can and will cause system crashes that wont resolve after a restart. I spent about 24 hours in windows recovery and physically unplugging drives to get my system to boot again. Please ensure you are targeting a standard physical drive to maintain system stability. A final word on compatibility. While I tested several games across all the projects during the course of development I cannot guarantee that this is truly 100% working. Thus any and all feedback is appreciated. Eventually I plan on creating a custom media pack for this plugin so everything has, icons, clear logos, and videos. Submitter spiritedusual Submitted 04/26/2026 Category Third-party Apps and Plugins  
  3. There is a log file in the plugin folder. Please post the relevant section where you are manually skipping and I will try to help you out. I can say that a manual entry prompt is due to the plugin not being able to match your game. Are your titles correct?
  4. Hey there thanks for the kind words. I'm trying to understand what you're asking. It sounds like you're saying manuals are not included. I just tested it and the manuals are working for me. Do you use the manual importer from the launchbox import process or are you downloading them manually? Do you keep your manuals in the default manuals folder? Should be /manuals/"platform"/"game.pdf".
  5. Playnite for sure has a lot of scrapers and is better at some things but I've used both a lot and Launchbox IMO is better once you get over the learning hurdle. Playnite themes looks really nice though.
  6. Add your game just the title and platform would be the bare minimum I would say. Then right click on it after adding it and click PC Game Scraper and run the plugin. Please review the instructions for API information. If this is NOT a PC game you will need API access to IGDB.
  7. My plugin doesnt show up there. When selecting a game or games right click and select the PC Game Scraper at the bottom of the menu.
  8. Wow whoever made that plugin must be super cool
  9. Glad to hear its working out for you!
  10. Got it. Well its good to hear it's working as its designed but yea right now not a way to change the default download location. It is something I will add soonish though. In the mean time you'll have to manually move your media to your designated drive. I know you've already got your system all set up, but you might want to look in to symlinks/junctions. If you don't know what they are it basically a way to make your files appear in two locations without using up any extra space. If you used this you could leave launchbox settings as they are and just move your files in to a folder and symlink/junction that location to where launchbox expects the media to be. I'm not super knowledgeable about it but it might be worth looking in to.
  11. Great thanks. Yea there are instructions for how to deal with the youtube thing. And as for your media location, it looks like you dont keep it with the launchbox install. So the media that is downloaded is in the /launchbox/videos/ and /images/ folder though right?
  12. There is a log in the plugin folder that will detail whats happening with youtube if you post it here I can help you with that. Also let me know how you organize your videos so I can understand what you need for when I add in the custom location feature.
  13. So yea that summary screen at the end is not accurate and its on my to do list. Im getting some mixed messages from you here though. You're saying that it fails and you see no added media following use but then in your edit you say that the images and videos have been downloaded. Maybe you mean its saying nothing downloaded in the summary screen but they files are present and you're not seeing them because your folder structure is different? You're not the first person to ask for a way to define the download location. Its something I'll look into when I'm done with my current project. So just to confirm, the media and metadata are downloading but the media isn't in the location you want it to be in so launchbox isn't detecting it? How do you have your folders set up?
  14. No everything you may need is in the archive and the log is created as soon as you click the plugin even if you cancel right away you should have something. Please send a screenshot of your plugin folder with all the files. And please still detail your exact situation as well.
  15. It's in the same folder as the plugin
×
×
  • Create New...