v1.5.1

Fix

• Delete game now works properly

v1.5

Breaking change

In order to make the new features structure to work, it is mandatory this time to drop all the database. This will only make you need to re-scan, but you won't lose the cover changes or file changes you made.

I apologize for the inconveniences this may cause, as this is a new software, it may change a little bit the first weeks, at least until I can develop a proper way to migrate between versions. I hope you can understand these initial wipes in order to make a better tool.

Added

• Now RomM folder structure is more flexible to match two different patrons by priority. This change makes RomM Emudeck compatible at least with single file games platforms. Check folder structure

• Added config file support to exclude folders and specific extension files to be scanned. To reload config file RomM reload is needed. Check config.

• Added tags support for region, revision/version and generic tags. Tags must have the right prefix to allow RomM scan them properly. Check tags.

v1.4.1

Added

• Now you can use your games tags (like (USA) or (rev-1)) to filter in the gallery

v1.4

Added

• Gamecube support platforms support
• PC support added (only for single file games like zip, iso, etc) platforms support

Changed

• Now delete game only deletes it from RomM gallery. To delete it from the filesystem too you need to allow it with the checkbox.

v1.3

Fixed

Breaking change - This breaking change only applies for mariaDB users:

Updating from <=v1.2.2

Some users reported errors when scanning files with large names because filenames are limited to 100 characters in the database. As I want to give as much flexibility as possible I changed some database columns.

If you didn't make a lot of manual changes you can just get rid of the database and recreate it, scanning your library again. If you did some changes and don't want to lose the progress, you should do this changes manually from the mariadb container (or wherever you have your mariadb database) since there is not any kind of CLI for this migration.

I am so sorry for any inconvenience this can generate.

Columns to modify (examples in case that you set it with database name as romm, in other case just change the database name in the {db_name}.roms part):

• alter table romm.roms modify column filename varchar(500);
• alter table romm.roms modify column filename_no_ext varchar(500);
• alter table romm.roms modify column name varchar(500);
• alter table romm.roms modify column r_slug varchar(500);
• alter table romm.roms modify column p_slug varchar(500);
• alter table romm.roms modify column path_cover_l text;
• alter table romm.roms modify column path_cover_s text;
• alter table romm.platforms modify column slug varchar(500);
• alter table romm.platforms modify column name varchar(500);
• alter table romm.platforms modify column path_logo text;

v1.2.2

Added

• Notification added when downloading a game

Changed

• Database name when using mariadb now can be changed with the new variable DB_NAME. Check docker-compos.example.yml

Fixed

• Potential password error when using mariadb if the password have special characters
• Some other bugs

v1.2

Added

• SQLite support
• Dreamcast support (https://github.com/zurdi15/romm#platforms-support)

Changed

• SQLite is now the database by default if ROMM_DB_DRIVER is not set. Check docker-compos.example.yml
• Internal library folder binding in the container changed from /emulation to /library. Check docker-compos.example.yml
• Platforms and games are now shown by alphabetical order

Docker image v1.2

v1.1

Added

• Game names parentheses are now omitted when searching game in IGDB, allowing game names to have tags.

Docker image v1.1

v1.0

Added

• Birth of RomM

Docker image v1.0