Files
dalamud-plugin-list/README.md
T

41 lines
1.6 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Dalamud plugin list
This repo holds the plugin lists for Dalamud.
## URLs for Dalamud / XIVLauncher
Add **one** of these as a custom plugin repository:
### Live (stable) for everyone
```
http://brassnet.ddns.net:33983/KnackAtNite/dalamud-plugin-list/raw/branch/main/pluginmaster.json
```
### Dev (testing) for you and testers
```
http://brassnet.ddns.net:33983/KnackAtNite/dalamud-plugin-list/raw/branch/main/pluginmaster-dev.json
```
- **Live** (`pluginmaster.json`): Stable releases. Update when you promote a build for everyone.
- **Dev** (`pluginmaster-dev.json`): Dev/test builds. Update when you publish a pre-release for testing.
## Publishing a dev build (e.g. HSUI)
1. Bump the plugin version (e.g. `1.0.8.4``1.0.8.5`).
2. Build Release, run the plugins create-release script (e.g. `HSUI/create-release.ps1`).
3. Create a Gitea release with a `-dev` tag (e.g. `v1.0.8.5-dev`) and upload the zip.
4. Update `pluginmaster-dev.json`:
- Set `AssemblyVersion` to the new version (e.g. `1.0.8.5`).
- Set `DownloadLinkInstall`, `DownloadLinkUpdate`, and `DownloadLinkTesting` to the dev release URL (e.g. `.../releases/download/v1.0.8.5-dev/latest.zip`).
- Update `LastUpdate` (Unix timestamp).
5. Commit and push `pluginmaster-dev.json` to Gitea.
Testers add the **dev** URL above and refresh their plugin list to see the new build.
## Promoting a dev build to live
1. Create a Gitea release with the stable tag (e.g. `v1.0.8.5`) and upload the same zip.
2. Update `pluginmaster.json` with the new version, download URLs, and changelog.
3. Commit and push.
4. Optionally remove the `-dev` release from Gitea once live is published.