Skip to content

PARAM.SFO Editor #81

@RupertAvery

Description

@RupertAvery

BUILD: https://github.com/RupertAvery/PSXPackager/actions/runs/21770752076/artifacts/5414001287

Image

The PARAM.SFO tab contains the following entries:

Key Default Value Required Editable Size Notes / Validation
BOOTABLE 1
CATEGORY ME
DISC_ID Empty 9 chars A game ID e.g. SLUS12345
DISC_VERSION 1.00 16 chars X.YZ where x is any number, YZ is a two-digit number e.g. 00 , 03
LICENSE Library programs Copyright(C) Sony ComputerEntertainment Inc. 512 chars
PARENTAL_LEVEL 1 A number from 1 - 11
PSP_SYSTEM_VER 3.71 16 chars X.YZ where x is any number, YZ is a two-digit number e.g. 00 , 03
REGION 32768
TITLE Empty 128 chars

Loading from a PBP

When a PBP is loaded, the PARAM.SFO section is filled in with information from the PBP. Keys that have been omitted from the above list will be listed in this section but with empty fields.

Linked fields

The following fields are linked to Disc metadata

  • DISC_ID is linked to the Save ID field
  • TITLE is linked to the Save Title field

Changing one will change the other

See #82

Field Size

Fields with a size specified will not be able to enter more than the specified number of characters.

Validation

If a field validation fails, it will display the text "Invalid Value" below.

Game ID validation uses the regular expression

(SCUS|SLUS|SLES|SCES|SCED|SLPS|SLPM|SCPS|SLED|SLPS|SIPS|ESPM|PBPX)(\d{5})

Is this too stringent? Are there Game IDs that don't match the above?

TODO: Saving a PBP should check all that fields are valid before proceeding to save.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions