Rename remaining branding to LightningGrim #1

2026-03-18T14:29:46-04:00

NotAlexNoyle commented

2026-03-18 14:29:46 -04:00

(Migrated from github.com)

Motivation

Consolidate the public and runtime branding so the project and shipped artifacts consistently present as LightningGrim instead of GrimAC.
Ensure user-facing messages, plugin metadata and shipped configuration comments match the new project name to avoid confusion for admins and end users.

Description

Updated documentation and contributor guidance including README.md and CONTRIBUTING.md to use LightningGrim and adjusted a few related headings and sentences.
Changed the Bukkit packaging metadata in bukkit/build.gradle.kts so the plugin name and author are LightningGrim.
Replaced runtime and logging/update strings in Java sources (notably GrimVersion, GrimLog, SuperDebug, PacketEventsInit, JavaVersion, TAB, ViaVersion, and CommonGrimArguments) to reference LightningGrim where appropriate, including User-Agent headers and diagnostic messages.
Rewrote admin-facing comments and source links in the bundled localized config templates under common/src/main/resources/config/ and updated the versioning helper comment in buildSrc/src/main/kotlin/versioning/VersionUtil.kt.

Testing

Verified text substitutions with repository searches using rg to locate remaining GrimAC occurrences in the edited files and confirm targeted replacements.
Ran a configuration cleanup pass over common/src/main/resources/config/*.yml to remove accidental double replacements and rechecked for stray LightningLightningGrim tokens.
Attempted to run ./gradlew compileJava to validate compilation, which failed in this environment due to the Gradle/Kotlin script evaluation failing to parse the installed Java version string (25.0.1), not because of code changes.

Codex Task

### Motivation - Consolidate the public and runtime branding so the project and shipped artifacts consistently present as `LightningGrim` instead of `GrimAC`. - Ensure user-facing messages, plugin metadata and shipped configuration comments match the new project name to avoid confusion for admins and end users. ### Description - Updated documentation and contributor guidance including `README.md` and `CONTRIBUTING.md` to use `LightningGrim` and adjusted a few related headings and sentences. - Changed the Bukkit packaging metadata in `bukkit/build.gradle.kts` so the plugin `name` and `author` are `LightningGrim`. - Replaced runtime and logging/update strings in Java sources (notably `GrimVersion`, `GrimLog`, `SuperDebug`, `PacketEventsInit`, `JavaVersion`, `TAB`, `ViaVersion`, and `CommonGrimArguments`) to reference `LightningGrim` where appropriate, including `User-Agent` headers and diagnostic messages. - Rewrote admin-facing comments and source links in the bundled localized config templates under `common/src/main/resources/config/` and updated the versioning helper comment in `buildSrc/src/main/kotlin/versioning/VersionUtil.kt`. ### Testing - Verified text substitutions with repository searches using `rg` to locate remaining `GrimAC` occurrences in the edited files and confirm targeted replacements. - Ran a configuration cleanup pass over `common/src/main/resources/config/*.yml` to remove accidental double replacements and rechecked for stray `LightningLightningGrim` tokens. - Attempted to run `./gradlew compileJava` to validate compilation, which failed in this environment due to the Gradle/Kotlin script evaluation failing to parse the installed Java version string (`25.0.1`), not because of code changes. ------ [Codex Task](https://chatgpt.com/codex/tasks/task_e_69bae3f102d8832fac71ffc1477fe886)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: trueog/LightningGrim#1