Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>SoundShaper ModsNew to Visual Studio Code? Get it now.
SoundShaper Mods

SoundShaper Mods

soundshaper

| (0) | Free
Make SoundShaper mods for Sound Shapes: .edit files checked against the game's files, mod.json checks, dependencies, previews, downloading mods from a Sound Shapes server, and installing mods as a patch archive for any version of the game.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

SoundShaper Mods for VS Code

For making SoundShaper mods for Sound Shapes, and getting them from a Sound Shapes server. It needs the Sound Shapes GameMonkey extension (the soundshapes-vscode repo), which gives .gm files and the GameMonkey inside .gm.edit files completion, hovers and signature help for the engine.

What it does

.edit files are parsed and applied exactly as SoundShaper does (a port of its src/edits.c):

  • Mistakes in the file are shown as SoundShaper would report them (line 12: expected "@@ end").
  • Every block is checked against the game's own files, as the mods the mod depends on, and the blocks before it, leave the file. A block that matches nothing, or more than one place, is an error that lists where it matches.
  • Above each block, a code lens gives the line it matches in each game version. Click it to open the game file there.
  • Preview the edited game file (the diff button in the editor title) shows the game's file next to the result.
  • Open the game file this edits opens the original, read-only.
  • In .gm.edit files, the GameMonkey in the blocks is highlighted, and completion and hovers work there as in .gm files.

mod.json is checked by SoundShaper's rules, with each problem underlined where it is:

  • required fields, ids of at most 63 bytes, platforms, list limits, screenshots that stay in the mod's folder;
  • ids shared with another mod, dependencies that aren't there or can't be installed, and mods that need themselves;
  • notes that aren't errors, such as "not made for PS Vita, so the app won't install it", a category the server doesn't know, or a screenshot over 2 MB.

Dependencies get completion with the ids of the mods next to it, a hover showing what each one is, and go to definition (opens its mod.json). One that nobody has gets a quick fix: Download it from the server.

Mod core: New mod… asks whether to use Mod core. If so, the mod gets "dependencies": ["mod-core"] and an entry script, SoundShaper/Mods/<id>.gm, which Mod core loads when the game starts. If you don't have Mod core, it is downloaded from the server into the dependency folder. Use Mod core in this mod does the same for an existing mod.

Functions mods define for each other (global MODCORE_IsInstalled = function(id) …) get completion, hovers with their comments, and go to definition (Ctrl+click), which offers the line of its mod's README that describes it and its source. Calling one from a mod that does not list its mod in dependencies is a warning, with a quick fix that adds the dependency.

Server mods: the SoundShaper view in the activity bar lists the mods on a Sound Shapes server (by default sound.ture.fish). It has search, category, platform and ordering filters, and marks the mods you have and the ones with a newer version. Each mod shows its details (description, readme, versions and their changelogs). Download one from the view, or with SoundShaper: Download a mod from the server…. The zip is checked against the server's sha256 and written into the dependency folder, with the mods it needs if you don't have them. There is no uploading and no signing in.

The dependency folder: mods downloaded from the server go into .dependencies/ at the top of the workspace folder, one folder each, and /.dependencies/ is added to that folder's .gitignore, so they are not committed with your mods. The mods in it count as dependencies of the mods in the workspace: they are checked against, applied before yours in previews and checks, and offered in completion. The dot keeps SoundShaper and the mod lists from taking the folder for a mod. When installing on the console, copy the dependencies into ux0:data/soundshaper/ next to your mods. With no workspace open, downloads go to soundshaper.downloadFolder, or you are asked where.

Installing mods, for any version of the game. Press the run button (▷, top right) on a mod's mod.json, .edit or .gm file: it installs the mods you installed last time, on the same target, again, in one go. Its menu, or SoundShaper: Install mods…, lets you choose where and which mods. The mods they need come too, and the mod you are editing is picked already. Installing works as the SoundShaper app does it on the Vita:

  • The mods are applied to the game's own archives: game_data.psarc and its patch_data001.psarc, from a game you set up with SoundShaper: Set up a game…. The wizard asks for the platform and the folder the archives are in, finds them, leaves out archives SoundShaper made, and checks that they open.
  • The files the mods change are written as an archive of their own, with mods.json and SoundShaper's marker in it. It is named as the next patch archive the game reads (patch_data002.psarc; the wizard lets you change it). mods.json is written next to it.
  • Then the archive goes where the install target says:
    • Export to a folder puts the archive and mods.json right in a folder you choose. On PS3 and RPCS3, choose the game's USRDIR (on RPCS3 dev_hdd0/game/<game ID>/USRDIR): the game loads patch_data002.psarc from there over its own archives (tested on RPCS3). For other versions, copy the archive to the game from the folder.
    • A PS Vita, over FTP sends it to ux0:rePatch/<title ID>/ with VitaShell's FTP server running (SELECT in VitaShell): the archive in game_data/, mods.json at the top, as the app puts them. rePatch loads it, and the SoundShaper app sees the mods as installed. The wizard asks for the Vita's address and your copy's title ID (PCSA00003 USA, PCSF00076 Europe, PCSD00027 Asia, PCSC00024 Japan). For a Vita, set up the game from decrypted copies of its archives: the Vita keeps them encrypted.
    • A PS Vita rePatch folder is the same layout in a folder, to copy to the Vita some other way.

An install never writes over one of the game's own archives, and asks before replacing an archive that SoundShaper did not make. Installing again replaces the archive it made before.

Commands: New mod…, Install mods…, Install the mods again, Set up a game…, Make an edit of the selection… (select text in a game file, pick a mod, and the block is added to its .edit file), Open a game file…, Check the mod as SoundShaper would install it (the app's log, per game version, in the SoundShaper output), Reload the game files.

Settings

"soundshaper.games": [
  {
    "name": "PS3",
    "platform": "ps3",                       // only mods that list this platform are checked against it
    "sources": [                             // folders of extracted files or .psarc archives, base game first
      "E:/rpcs3/dev_hdd0/game/NPUA80543/USRDIR/game_data.psarc",
      "E:/rpcs3/dev_hdd0/game/NPUA80543/USRDIR/patch_data001.psarc"
    ]
  },
  { "name": "PS Vita", "platform": "psvita", "sources": ["D:/vita/game_data.psarc", "D:/vita/patch_data001.psarc"] }
],
"soundshaper.installTargets": [              // where Install mods… installs (the wizard adds them)
  { "name": "RPCS3", "game": "PS3", "destination": "E:/rpcs3/dev_hdd0/game/NPUA80543/USRDIR", "layout": "flat" },
  { "name": "My Vita", "game": "PS Vita", "destination": "ftp://192.168.1.20:1337/ux0:/rePatch/PCSA00003", "layout": "repatch" }
],
"soundshaper.modFolders": [],                // more folders of mods that dependencies can come from
"soundshaper.server": "https://sound.ture.fish",
"soundshaper.dependencyFolder": ".dependencies", // in the workspace folder, git-ignored: where downloads go
"soundshaper.downloadFolder": ""             // where downloads go outside a workspace; asked when empty

A mod's folder is the nearest folder above a file that has a mod.json. The mods next to it, in the same folder of mods, are the ones its dependencies can come from, as on the console, and so are the ones in the dependency folder and in soundshaper.modFolders.

Build

npm test               # the edit format, mod.json rules, order and building; the example mods against the PS3 game when there
npm run package        # soundshaper-mods-<version>.vsix
code --install-extension soundshaper-mods-0.1.0.vsix

When SoundShaper's rules change (src/edits.c, src/mods.c), change src/edits.js and src/mods.js to match.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft