forked from libretro/libretro-core-info
-
Notifications
You must be signed in to change notification settings - Fork 0
/
00_example_libretro.info
86 lines (70 loc) · 3.72 KB
/
00_example_libretro.info
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
## All data is optional, but helps improve user experience.
# Software Information - Information about the core software itself
# Name displayed when the user is selecting the core:
# display_name = "Nintendo - Game Boy (Core Name)"
# Categories that the core belongs to (optional):
# categories = "Emulator"
# Name of the authors who wrote the core:
# authors = "Martin Freij|R. Belmont|R. Danbrook"
# Name of the core:
# corename = "Nestopia"
# List of extensions the core supports:
# supported_extensions = "nes|fds"
# License of the cores source code:
# license = "GPLv3"
# Privacy-specific permissions needed for using the core:
# permissions = ""
# Version of the core:
# display_version = "v0.2.97.30"
# Hardware Information - Information about the hardware the core supports (when applicable)
# Name of the manufacturer who produced the emulated system:
# manufacturer = "Nintendo"
# Name of the system that the core targets (optional):
# systemname = "Nintendo Entertainment System"
# ID of the primary platform the core uses. Use other core info files as guidance if possible.
# If blank or not used, a standard core platform will be used (optional):
# systemid = "nes"
# The number of mandatory/optional firmware files the core needs:
# firmware_count = 7
# Firmware entries should be named from 0
# Firmware description
# firmware0_desc = "filename (Description)" ex: firmware0_desc = "bios.gg (GameGear BIOS)"
# Firmware path
# firmware0_path = "filename.ext" ex: firmware0_path = "bios.gg"
# Is firmware optional or not, if not defined RetroArch will assume it is required
# firmware0_opt = "true/false"
# Additional notes:
# notes = "(!) hash|(!) game rom|(^) continue|[1] notes|[^] continue|[*] list"
# Libretro Features - The libretro API features the core supports. Useful for sorting cores
# Does the core support savestates
# savestate = "true"
# If true, how complete is the savestate support? basic, serialized (rewind), deterministic (netplay/runahead)
# savestate_features = "serialized"
# Does the core support the libretro cheat interface?
# cheats = "false"
# Does the core support libretro input descriptors
# input_descriptors = "true"
# Does the core support memory descriptors commonly used for achievements
# memory_descriptors = "false"
# Does the core use the libretro save interface or does it do its own thing (like with shared memory cards)?
# libretro_saves = "true"
# Does the core support the core options interface?
# core_options = "true"
# What version of core options is supported? (later versions allow for localization and descriptions)
# core_options_version = "1.0"
# Does the core support the subsystem interface? Commonly used for chained/special loading, such as Super Game Boy
# load_subsystem = "false"
# Whether or not the core requires an external file to work:
# supports_no_game = "false"
# Name of the database that the core supports (optional):
# database = "Nintendo - Nintendo Entertainment System|Nintendo - Famicom Disk System"
# Does the core support/require support for libretro-gl or other hardware-acceleration in the frontend?
# hw_render = "false"
# Does the core require ongoing access to the file after loading? Mostly used for softpatching and streaming of data
# needs_fullpath = "false"
# Does the core support the libretro disk control interface for swapping disks on the fly?
# disk_control = "false"
# Is the core currently suitable for general use? That is, will regular users find it useful or is it for development/testing only (subject to change over time)?
# is_experimental = "true"
# Descriptive text, useful for tooltips, etc.
# description = "This is a brief description of the core. It should be informative, but probably not super-long. 1024 characters, tops, all on one line (i.e., no manual line-breaks)."