release: VelocityNavigator 4.3.0

Author: Cyrusbye720

.github/workflows/build.yml

@@ -7,15 +7,16 @@ on:
     branches: [main]
   workflow_dispatch:
     inputs:
-      version:
-        description: 'Release version (e.g. 3.0.0)'
-        required: true
-        default: '4.2.0'
       create_release:
         description: 'Create a GitHub Release?'
         required: true
         type: boolean
         default: true
+      prerelease:
+        description: 'Mark the GitHub Release as a prerelease?'
+        required: true
+        type: boolean
+        default: false
 
 jobs:
   build:
@@ -40,12 +41,7 @@ jobs:
       - name: Resolve Version
         id: version
         shell: bash
-        run: |
-          if [[ "${{ github.event_name }}" == "workflow_dispatch" ]]; then
-            echo "version=${{ inputs.version }}" >> "$GITHUB_OUTPUT"
-          else
-            echo "version=$(mvn help:evaluate -Dexpression=project.version -q -DforceStdout)" >> "$GITHUB_OUTPUT"
-          fi
+        run: echo "version=$(mvn help:evaluate -Dexpression=project.version -q -DforceStdout)" >> "$GITHUB_OUTPUT"
 
       - name: Upload JAR Artifact
         uses: actions/upload-artifact@v4
@@ -66,4 +62,4 @@ jobs:
           body_path: release_notes.md
           files: target/VelocityNavigator-*.jar
           draft: false
-          prerelease: false
+          prerelease: ${{ inputs.prerelease }}

CHANGELOG.md

@@ -1,26 +1,26 @@
 # Contributing to VelocityNavigator
 
-First off, thanks for taking the time to contribute! VelocityNavigator is a premium project by **DemonZ Development**, and we appreciate any help in making it better.
+Thanks for taking the time to contribute. VelocityNavigator is an open-source project maintained by **DemonZ Development**, and contributions of any size are welcome.
 
 ## How Can I Contribute?
 
 ### Reporting Bugs
-Bugs are tracked as GitHub issues. When creating a bug report, please include as many details as possible (logs, Velocity version, etc.).
+Bugs are tracked as GitHub issues. When creating a bug report, include as much detail as possible: the Velocity version, the VelocityNavigator version, the relevant section of `navigator.toml`, and any logs or stack traces.
 
 ### Suggesting Enhancements
-Feature requests are also tracked as GitHub issues. We love hearing your ideas!
+Feature requests are also tracked as GitHub issues. Describe the problem you are trying to solve and the behavior you expect; concrete examples and proposed config shapes help.
 
 ### Pull Requests
 - Fork the repository and create your branch from `main`.
-- If you've added code that should be tested, add tests!
+- If you add code that should be tested, add tests covering it.
 - Ensure the test suite passes (`mvn verify`).
-- Make sure your code lints.
 - Follow the existing code style.
+- Keep commits focused — one logical change per branch makes review faster.
 
 ## Credits & Attribution
-VelocityNavigator is developed and maintained by **DemonZ Development**. 
+VelocityNavigator is developed and maintained by **DemonZ Development**.
 
-Contributors who have their pull requests merged will be listed in the [CHANGELOG.md](CHANGELOG.md) and on the project page.
+Contributors who have pull requests merged are listed in the [CHANGELOG.md](CHANGELOG.md) and on the project page.
 
 ## License
-By contributing to VelocityNavigator, you agree that your contributions will be licensed under its [Apache License 2.0](LICENSE).
+By contributing to VelocityNavigator, you agree that your contributions are licensed under the project's [Apache License 2.0](LICENSE).

CONTRIBUTING.md

@@ -0,0 +1,43 @@
+# Marketplace and Brand Assets
+
+Brand artwork and guide headers are generated by `scripts/generate_marketplace_assets.py`. The Java and Bedrock selector images are real in-game screenshots, and the dashboard preview is a real runtime capture. These screenshots are never regenerated by that script.
+
+The same script also writes the compact page headers under `wiki/headers/` so the public guides share the same visual style.
+
+## Brand files
+
+| File | Size | Use |
+|---|---:|---|
+| `plugin-icon.png` | 1024 × 1024 | Marketplace and wiki icon |
+| `logo-mark.png` | 1024 × 1024 | Transparent master mark |
+| `hero-banner.png` | 1600 × 500 | README, wiki, and marketplace header |
+| `social-post.png` | 1200 × 630 | Release and social preview |
+| `java-inventory-selector.png` | 924 × 520 | Real Java Edition inventory selector screenshot |
+| `bedrock-selector.png` | 1024 × 528 | Real Bedrock selector screenshot |
+| `dashboard-preview.png` | 747 × 1096 | Live operations dashboard with configured and Redis-discovered lobbies |
+
+The visual system uses a navy background, off-white type, and one cyan accent. Avoid adding glow, gradients with heavy bloom, stock gaming artwork, or dense paragraphs inside images.
+
+## Marketplace panels
+
+The `marketplace/` panels are 1200 × 420 PNG files. They are section headers and visual summaries, not replacements for the searchable text below them.
+
+| File | Recommended alt text |
+|---|---|
+| `01-smart-routing.png` | Player routed to a healthy lobby |
+| `02-universal-jar.png` | Universal JAR architecture for Velocity and optional backends |
+| `04-resilient-routing.png` | Circuit breaker and health monitoring states |
+| `05-optional-systems.png` | Optional party, queue, and Redis systems |
+| `06-operations.png` | Network health and operations dashboard |
+| `07-localization.png` | Built-in and custom language support |
+| `08-defensive-design.png` | Security boundaries for menus, Redis, HTTP, and files |
+| `09-compatibility.png` | Velocity and backend bridge compatibility |
+| `marketplace-footer.png` | VelocityNavigator documentation and support footer |
+
+## Listing sources
+
+`modrinth-listing.md` is the canonical marketplace body. Run `scripts/generate_marketplace_assets.py` after editing it; the script refreshes `hangar-listing.md` and `spigot-resource.md` with the same feature copy and platform-specific download wording. `spigot-resource.bbcode` is the separately formatted Spigot resource-page source.
+
+Marketplace bodies keep players on their current marketplace for downloads. They must not link to GitHub releases or use GitHub as a download CTA.
+
+Keep critical compatibility, installation, command, permission, and limitation details as real text. Modrinth requires meaningful image alt text, and Spigot's premium guidelines discourage substantive description text being placed only inside images.