migrations VS retool

With database created, we also need to create tables in which our data will be store. And best way to do that is using migrations. We will be using go-pg/migrations module. On GitHub page you can find basic installation and usage guide, and we will use that. Let's start by creating new directory migrations/ inside of project root and file file migrations/main.go:

github.com/go-pg/migrations: Package (Explicit SQL),

Additionally there's Project Peacock and the redump supplement. So the only thing needed is a full redump set and a 1G1R tool to get rid of the redump duplicates.

As for 1G1R I would suggest the tool Retool it lets you import a DAT file and then export a new filtered DAT file with whatever filters you selected and then you would use that with a ROM manager. Download the .zip then make a folder to extract the files to then run the GUI and let it download the clone lists then open a DAT file.

A no-intro set will have every version of every game. If you want a single version of every game with the European PAL region preferred, you need to get the no-intro set and then use a utility to create a 1G1R (1 game 1 rom) set. These programs have databases that know which games are clones of other games, and which is the best "version" of a game based on what your preferred region is. I recommend Retool: https://github.com/unexpectedpanda/retool

FWIW, SegaNet titles are already demoted, as are Sonic Classics and Collection of Mana so long as you leave Titles ripped from modern platform releases replace standard editions unchecked. They were all added in about two years ago, so worthwhile to update, or if you're still seeing problems, file an issue and I can look into it :)

I use retool to make 1G1R lists for each system from the full romsets. Then I make a text file of each list of the 1G1R roms and edit them down into certain sets (favorites for each system, 2D Dreamcast games, PSP RPGs, etc.). Then I use a script to copy just the sets of roms I want for that handheld to the SD card. The end result is a curated set of games for each handheld based on the performance of the handheld and what kinds of games I want to play on it. And since it uses scripts and text files I don't have to do anything for a new handheld other than tell the script which lists to use.

Would you recommend this over using Retool to edit the Dat file and then using Romcenter for instance? Could you maybe do a 1G1R comparison between EzRo and Retool and share your thoughts?

Why do I have 49 versions of vanilla chrono trigger? Sure, SNES doesn't take up much space, I can afford to be CrAzY there, but i carry this madness to other systems. Systems not so compressible past .chd and I need help man. I need some rehab, so I am going to go through the process of 1G1R with the help of ReTool, Romulus, DatOMatic, and others Fuck yeah!

Perhaps you might want to check out retool to generate your 1G1R sets, which is what I'm planning to do in the future. I was a little skeptical about the effectiveness of that method to identify clones correctly, but from what I see the clonelists are updated quite frequently which implies that the project is actively maintained by the community. I know that creating your own lists manually is very time-consuming, since this is what I've also done in the past.

Take a look at https://github.com/unexpectedpanda/retool