Skip to content
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

[Missing] add core info file for FBNeo #13

Closed
5schatten opened this issue May 21, 2019 · 4 comments
Closed

[Missing] add core info file for FBNeo #13

5schatten opened this issue May 21, 2019 · 4 comments

Comments

@5schatten
Copy link

Looks like the dust has been settled a bit & the FinalBurn Neo repo https://github.com/libretro/FBNeo is up and running. So I guess a new FBNeo core info file will be needed?

I guess something like this could do the trick? But I guess it needs further tweaking for database files.
fbneo_libretro.info

display_name = "Arcade (FB Neo)"
authors = "Team FinalBurn Neo"
supported_extensions = "zip|7z"
corename = "FB Neo"
manufacturer = "Various"
categories = "Emulator"
systemname = "Arcade (various)"
systemid = "fb_alpha"
database = "FB Alpha - Arcade Games"
database_match_archive_member = "true"
license = "Non-commercial"
permissions = ""
display_version = "v0.2.97.44"
supports_no_game = "false"
notes = "(!) The BIOS files must be inside the ROM directory.|(!) You need a copy of neocdz.zip and neogeo.zip in your libretro system directory for neocd"
@RobLoach
Copy link
Member

Thanks! Just ran an update.

git clone https://github.com/libretro/libretro-core-info.git
cd libretro-core-info
make update

It'll only be tagged once the new RA comes out though.

@RobLoach
Copy link
Member

RobLoach commented May 21, 2019

This should be fixed now. Feel free to re-open if it's not. Thanks!

Also added some docs:
https://github.com/libretro/libretro-core-info/wiki

@5schatten
Copy link
Author

@RobLoach
I guess it should be fine & works for me. The only thing which might lead to confusion in the future is the system_id & database? I guess the fbalpha developement won't be that active anymore & if they share a common database that might contain unsupported stuff you'll run into problems.

@RobLoach
Copy link
Member

You're right. Keep watch and let's see how the database may need to change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants