Skip to content

Installation

Minecraft (Windows, iOS, Android, console)

  1. Download Soulglass_v<version>.mcaddon from the Releases page.
  2. Open the file. Minecraft installs both packs automatically.
  3. Edit your world → Behavior Packs → activate Soulglass.
  4. Edit your world → Resource Packs → activate Soulglass.

Both packs are required

The resource pack carries the translation strings. With only the behavior pack active, every message appears as a raw key such as soulglass.hud.none.

Bedrock Dedicated Server

BDS does not read .mcaddon. Extract it and place each half by hand:

<server>/behavior_packs/soulglass/
<server>/resource_packs/soulglass/

Then register both in the world folder:

worlds/<world>/world_behavior_packs.json
[
  { "pack_id": "b41d7a9c-3e26-4f80-95a7-1c8d0b6e2f43", "version": [1, 0, 0] }
]
worlds/<world>/world_resource_packs.json
[
  { "pack_id": "0c7a1e46-8b52-4d93-a1f7-26e0b9c4d385", "version": [1, 0, 0] }
]

If either file already exists, add the object to the list instead of replacing the file. Restart the server; the log should show [Soulglass] ready.

Development install

A junction lets the game read straight from your clone, so an edit takes effect the next time you enter the world.

=== "Windows"

```powershell
$mojang = "$env:APPDATA\Minecraft Bedrock\Users\Shared\games\com.mojang"
New-Item -ItemType Junction `
  -Path "$mojang\development_behavior_packs\soulglass" `
  -Target "$PWD\behavior_packs\soulglass"
New-Item -ItemType Junction `
  -Path "$mojang\development_resource_packs\soulglass" `
  -Target "$PWD\resource_packs\soulglass"
```

=== "Linux (BDS)"

```bash
ln -s "$PWD/behavior_packs/soulglass"  /path/to/bds/behavior_packs/soulglass
ln -s "$PWD/resource_packs/soulglass"  /path/to/bds/resource_packs/soulglass
```

Path changed in 1.26

The Windows Store edition no longer stores data in LocalState\games\com.mojang. It now lives under %APPDATA%\Minecraft Bedrock\, with worlds separated per account profile.

Troubleshooting

The pack loads but nothing happens. Turn on Content Log GUI under Settings → Creator. Every event subscription is isolated, so a failure names itself in the log instead of silently killing the add-on.

Messages show as raw keys. The resource pack is not active.

/scriptevent says the command does not exist. Cheats are disabled in that world. Sneaking while holding the guide does the same job without cheats.