diff --git a/dist/info/puzzlescript_libretro.info b/dist/info/puzzlescript_libretro.info
index 5b3628bc..f53511e4 100644
--- a/dist/info/puzzlescript_libretro.info
+++ b/dist/info/puzzlescript_libretro.info
@@ -1,30 +1,105 @@
-# Software Information
+# Software Information - Information about the core software itself
+# Name displayed when the user is selecting the core:
 display_name = "PuzzleScript (pzretro)"
+
+# Categories that the core belongs to (optional):
 categories = "Game engine"
+
+# Name of the authors who wrote the core:
 authors = "Nathan Whitehead"
+
+# Name of the core:
 corename = "puzzlescript"
+
+# List of extensions the core supports:
 supported_extensions = "pz|pzp"
+
+# License of the cores source code:
 license = "MIT"
+
+# Privacy-specific permissions needed for using the core:
 permissions = ""
 
-# Hardware Information
+# 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 = "PuzzleScript"
+
+# Name of the system that the core targets (optional):
 systemname = "PuzzleScript"
+
+# 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 = "puzzlescript"
 
-# Libretro Features
+# The number of mandatory/optional firmware files the core needs:
+firmware_count = 0
+
+# 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"
-savestate_features = "deterministic"
-cheats = "false"
+
+# 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 = "true"
+
+# 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.3"
+
+# 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"
+
+# Does the core have a single purpose? Does it represent one game or application, requiring predetermined support files or no external data? Used to indicate to a frontend that the core may be presented/handled independently from 'regular' cores that run a variety of content.
+single_purpose = "false"
+
+# Name of the database that the core supports (optional):
 database = "PuzzleScript"
+
+# Does the core support/require support for libretro-gl or other hardware-acceleration in the frontend?
 hw_render = "false"
+
+# Which hardware-rendering APIs does the core support? Delimited by pipe characters.
+# required_hw_api = "Vulkan >= 1.0 | Direct3D >= 10.0 | OpenGL Core >= 3.3 | OpenGL ES >= 3.0"
+
+# 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"
 
-description = "Plays PuzzleScript games"
+# 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 = "false"
+
+# Descriptive text, useful for tooltips, etc.
+description = "Plays PuzzleScript and PuzzleScript Plus games"