what about adding a cheevos flag in gamelist.xml ?

robertybob

With all the exciting developments going on in Emulationstation this year, I think it'll be a crying shame if something RetroAchievements-related isn't added. It's such a good idea and one that, if more widely known, would make RetroPie even more attractive to users.

Yes only (some) RetroArch emulators are compatible, however I'm willing to bet that most users spend most of their time on said emulators anyway!

Worst case scenario, would it be possible for your flag to be installable via the RetroPie experimental menu (i.e. rebuilds the stable ES but with the flag added)? If we can have a 3do emulator (which doesn't even really work on a Pi) within the Experimental section, then why not this? It would be used by many more people.

meleu

@robertybob said in what about adding a cheevos flag in gamelist.xml ?:

Worst case scenario, would it be possible for your flag to be installable via the RetroPie experimental menu

If you're talking about a EmulationStation fork only with this feature, EmulationStation development fragmentation is strongly unwanted.

But I'm sure we will find a satisfactory solution for this. Let's just wait a little... ;-)

robertybob

@meleu Not as a separate branch, but a patch that, if Emulationstation was updated, would still be there. ...I suppose when you update ES it deletes the existing installation, rather than installing over the top of it? (I have no idea how it all works)

pjft

@meleu What would you think about the output of your script being custom-collection files? They're just plain text files with the absolute path to the ROMs, one per line, named custom-<name>.cfg, and stored in ~/.emulationstation/collections.

If you were to generate, say, custom-nes achievements.cfg and add it to that folder, the user only needs to go to the collections menu and enable it. You'd have a dedicated system with all NES games with achievement support, in this case.

Just a thought. Might be easier to generate, easier to use, and not depend on any changes to ES, which would alleviate the current concerns in that thread.

@robertybob the concept makes sense, but the patch itself would need to be updated as with any ES developments the code may change in ways that it would render the patch changes incompatible.

meleu

@pjft said in what about adding a cheevos flag in gamelist.xml ?:

@meleu What would you think about the output of your script being custom-collection files? They're just plain text files with the absolute path to the ROMs, one per line, named custom-<name>.cfg, and stored in ~/.emulationstation/collections.

The hascheevos is already able to do such thing, as in this example. But I'll make it easier.

Thanks for the suggestion. ;-)

pjft

@meleu If you output in that format and filename, to that folder, then they'll automatically show up in the "Custom Collections" menu to be enabled. That'll make it easy for the user to immediately have access to a collection in ES filtered with only achievements titles.

EDIT: if you want to go the extra step, though I wouldn't especially encourage it myself, you may then also edit the es_settings.cfg file automatically and add those files to the enabled custom collections list. It's riskier, though, as if something goes wrong ES may stop working :)

hansolo77

That's how I'm doing it. Although I don't have it broken down into individual systems (nes-cheevo, mega drive-cheevo, etc). I just have 1 big system called "Achievements, and all the games are in there. Works great!

meleu

@pjft OK bro, I'm working on hascheevos to make it create the custom collections cfg files. Is there some doc on how to use it? I think I've figured out how to use it based on yours and @cyperghost 's posts, but I can't see any mention to it in ES section of docs.

pjft

@meleu no, I haven't had the chance to document those there yet, apologies.

What I stated is effectively how it works. If you go to the folder and open one of the files you'll understand how it's meant to be fairly quickly.

But let me know if any questions arise, definitely!

cyperghost

@meleu @pjft
Yes all is wrapped up here but indeed there is no docu about the HOW-TO-Use system from ES.

Collections file got structure custom-ANY FILENAME.cfg in path /opt/retropie/configs/all/emulationstation/collections

Collections file got structure
$pathtomainrom/$system/$romname
Last character is \n for newline. Look here in MAME 1th anniversary thread

meleu

@cyperghost your posts were from where I learned the most about this feature. ;-)
Thanks for sharing!

cyperghost

@meleu
So you may create RetroAchievements for each system ...
Use your haschevos tool and then compare with user ROMset and write filehit to collection for system....

As every user gots different name for ROM this way via checksum would be the generic usage. As you put a lot of time in the development of the cheevos_scraper it would be just angry to loose the progress.
:D

For retro-gods sake @pjft used a straight system to make the collections work ;) It's very powerfull and it would be just fair to set this ES development as milestone.

meleu

I'm working on that. If you are curious here is what I've done so far: https://github.com/meleu/hascheevos/pull/11

I'm coding away from my RetroPie (cygwin on windows), then I'm currently unable to actually test it. Will try it later.

cyperghost

@meleu Good luck mate. As the xml-flag eventually miss the main branch the collections is also a way to success

meleu

yeah guys! using custom collections for this is a nice approach too.

Posted about how to automatically generate RetroAchievements custom collections. Check it here:
https://retropie.org.uk/forum/topic/13487/hascheevos-sh-a-tool-for-retropie-retroachievements-users