-
Notifications
You must be signed in to change notification settings - Fork 0
Release v0.7.0 — per-event notifications, UI rework, TriOS readiness #7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 12 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
28ce4af
feat: visual feedback on ramscoop toggle — cyan/blue activation, grey…
powerfulqa bffbec5
chore: remove build artifacts and ignore compiled classes/jars
powerfulqa 2cadcd7
chore: remove generated build artifacts from working tree (temp_class…
powerfulqa 9707359
Update ramscoop notification colors for nebula and corona entry
powerfulqa 0d02cbb
Add configurable color themes for ramscoop floating text notifications
powerfulqa 8d0928a
Replace color themes with individual active/inactive color selection …
powerfulqa 2b14268
Remove color preset radios; use only HSV color pickers for nebula/cor…
powerfulqa 82614f0
feature(visual): notification UI & behavior
powerfulqa 2009e7b
chore(docs): release notes and version bump to v0.7.0
powerfulqa 99d087d
docs: update README for v0.7.0 and add TriOS compatibility notes (TRI…
powerfulqa c3f1347
chore: add TriOS download/changelog URLs to mod_info.json
powerfulqa 9582b2b
docs(release): tidy v0.7.0 changelogs and TriOS notes
powerfulqa bf0877d
Update data/config/LunaSettings.csv
powerfulqa 072db6f
Update docs/RELEASE_v0.7.0_SUMMARY.md
powerfulqa File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,37 @@ | ||
| ````markdown | ||
| # Release v0.7.0 Summary | ||
|
|
||
| ## Release Date | ||
| 2025-10-13 | ||
|
|
||
| ## Changes Overview | ||
|
|
||
| ### Added | ||
| - Per-event notification toggles for Nebula Entry, Nebula Exit, Corona Entry, and Corona Exit exposed via LunaLib. | ||
|
|
||
| ### Changed | ||
| - Reordered Notification UI in `data/config/LunaSettings.csv` to group Nebula and Corona settings together. | ||
| - Removed legacy color preset radio controls; LunaLib color pickers (hex + HSV sliders) are now the single source of color configuration. | ||
| - Default notification colors set to light gray (#D3D3D3). | ||
|
|
||
| ## Files Modified | ||
| - `data/config/LunaSettings.csv` — reorganised notification section, added per-event toggles, default color updated | ||
| - `src/ramscoop/ModPlugin.java` — added LunaLib reads for new toggles, default colors updated, debug logging updated | ||
| - `src/ramscoop/Ramscoop.java` — notifications gated by runtime scoop toggle, removed blue-text scheduling | ||
| - `Ramscoop.version`, `version.json`, `mod_info.json` — version bumped to 0.7.0 | ||
| - `CHANGELOG.md`, `changelog.txt` — added v0.7.0 entries | ||
|
|
||
| ## Testing | ||
| - Rebuilt JAR with the project's build script and verified compilation | ||
|
powerfulqa marked this conversation as resolved.
Outdated
|
||
| - Confirmed in-game via user testing that per-event toggles appear and function, notifications respect the master Scoop toggle, and the delayed blue text is removed | ||
|
|
||
| ## Notes | ||
| - This release is a small feature addition and UI rework; it is backwards-compatible with existing saves and settings. LunaLib-stored color values will continue to override new defaults where present. | ||
|
|
||
| --- | ||
|
|
||
| **Build Status**: ✅ Successful | ||
| **Testing Status**: ✅ User-verified | ||
| **Ready for Release**: ✅ Yes | ||
|
|
||
| ```` | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| TriOS compatibility checklist for Passive Ramscoop | ||
|
|
||
| This short guide lists the things required by TriOS (TriOS mod manager) to accept a mod release and the validation steps to confirm those requirements are met. | ||
|
|
||
| Checklist | ||
| - [ ] Semantic versioning: ensure `Ramscoop.version` contains numeric `major`, `minor`, and `patch` fields (e.g. `{"major":0,"minor":7,"patch":0}`) and matches other version files. | ||
| - [ ] `changelog.txt` must be plain text and include headers of the form: `Version X.X.X` (no markdown headings). TriOS reads the plain-text changelog directly. | ||
| - [ ] `mod_info.json` must have a `directDownloadURL` and `changelogURL` that point to the release assets (case-sensitive paths). | ||
| - [ ] Include `jars/Ramscoop.jar` in the release assets uploaded to the host used by TriOS (or make sure `directDownloadURL` points to a downloadable jar). | ||
| - [ ] `Ramscoop.version` and `version.json` should be kept in sync with `mod_info.json` to prevent TriOS version mismatches. | ||
| - [ ] Use a Git tag with `vMAJOR.MINOR.PATCH` (for example `v0.7.0`) when creating the release so TriOS and CI workflows can find the correct version. | ||
|
|
||
| Validation steps (quick) | ||
| 1. Verify `Ramscoop.version` contains numeric fields and matches `mod_info.json`: | ||
| - Open `Ramscoop.version` and check `major`, `minor`, `patch` values. | ||
| - Open `mod_info.json` and `version.json` and ensure the `version` string matches `major.minor.patch`. | ||
|
|
||
| 2. Verify `changelog.txt` formatting: | ||
| - Ensure it is a plain-text file and contains a line starting with `Version ` followed by the version number and a newline before the content. | ||
|
|
||
| 3. Verify `directDownloadURL` and `changelogURL`: | ||
| - Check `mod_info.json` for the `directDownloadURL` and `changelogURL` fields. | ||
| - Ensure the URLs are correct, reachable, and case-sensitive matches of the files you upload. | ||
|
|
||
| 4. Package test: | ||
| - Build with `.uild.ps1` to produce `jars/Ramscoop.jar`. | ||
| - Locally host the `jar` (or place it where your release tooling expects) and confirm the `directDownloadURL` points to a working download. | ||
|
|
||
| 5. Tag & release: | ||
| - Create git tag `vMAJOR.MINOR.PATCH` and push tags: `git tag v0.7.0; git push --tags`. | ||
|
|
||
| Notes & tips | ||
| - TriOS expects plain text and exact path names. Double-check file case, especially on case-sensitive hosts. | ||
| - `Ramscoop.version` is specifically used by TriOS: keep it machine-friendly (plain JSON with numeric fields) and bump the `patch` field when publishing bugfixes. | ||
| - If you automate releases (CI), ensure your workflow uploads `jars/Ramscoop.jar` and `changelog.txt` and updates `mod_info.json` `directDownloadURL` to point at the uploaded asset. |
Binary file not shown.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.