feat(killaura): add RangeIndicator visual feedback #7555
+174
−2
Conversation
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
Adds a circle around the player showing the KillAura attack range: - Idle color (red) when no target in range - Active color (green) when targeting an enemy - Optional outline and wall range circle - Synced with KillAura Range and WallRange settings
CompileRider
changed the title
- Add color modes: Static, Rainbow, Distance-based - Add pulse animation with configurable speed/intensity - Add fade animation for smooth state transitions - Add opponent range visualization - Add wall range circle option - Add conditions: hide when dead/spectator/in vehicle - Sync with KillAura Range and WallRange settings
Add visual range indicator to KillAura module showing attack range: - Circle around player indicating attack range - Color changes based on target state (idle/active) - Multiple color modes: Static, Rainbow, Distance-based - Pulse and fade animations - Optional circles for WallRange, ScanRange, OpponentRange Fully synced with KillAura settings: - Uses KillAura Range and WallRange values - Respects IgnoreOpenInventory setting - Hides when player is dead/spectator Useful for PvP to visualize attack range and spacing.
CompileRider
changed the title
...luex/liquidbounce/features/module/modules/combat/killaura/features/KillAuraRangeIndicator.kt
Outdated
Show resolved
Hide resolved
...luex/liquidbounce/features/module/modules/combat/killaura/features/KillAuraRangeIndicator.kt
Outdated
Show resolved
Hide resolved
Address review feedback from MukjepScarlet
- Use startBatch/commitBatch for render optimization - Replace multiple if-returns with takeUnless - Extract drawRangeCircle helper to reduce duplication - Use scope functions (run, also) for cleaner code - Simplify getColor with when expression
Member
|
Looks fine to me. I must say, I would not use it myself, but I remember that this was a thing in many clients. Is this typically used? |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
...luex/liquidbounce/features/module/modules/combat/killaura/features/KillAuraRangeIndicator.kt
Fixed
Show fixed
Hide fixed
...luex/liquidbounce/features/module/modules/combat/killaura/features/KillAuraRangeIndicator.kt
Fixed
Show fixed
Hide fixed
...luex/liquidbounce/features/module/modules/combat/killaura/features/KillAuraRangeIndicator.kt
Fixed
Show fixed
Hide fixed
- Add missing renderEnvironmentForWorld import - Simplify renderHandler by inlining render call - Fix BracesOnIfStatements detekt errors - Reduce cognitive complexity of render() by extracting helper functions
...luex/liquidbounce/features/module/modules/combat/killaura/features/KillAuraRangeIndicator.kt
Outdated
Show resolved
Hide resolved
- Merge showXXX booleans into color alpha (alpha 0 = hidden) - Simplify render logic by inlining helper functions - Remove redundant abs() check in updateColorFactor - Use canRender() instead of separate visibility checks
...luex/liquidbounce/features/module/modules/combat/killaura/features/KillAuraRangeIndicator.kt
Fixed
Show fixed
Hide fixed
...luex/liquidbounce/features/module/modules/combat/killaura/features/KillAuraRangeIndicator.kt
Fixed
Show fixed
Hide fixed
- Extract calculatePulse() and renderCircles() to reduce cognitive complexity - Add braces to all if/else branches
- Extract renderIndicator() to reduce render() cognitive complexity - Refactor canRender() to single expression (avoids BracesOnIfStatements)
...luex/liquidbounce/features/module/modules/combat/killaura/features/KillAuraRangeIndicator.kt
Fixed
Show fixed
Hide fixed
- Add LivingEntity import - Use short type name instead of fully qualified
| } | ||
|
|
||
| private fun WorldRenderEnvironment.drawRangeCircle(radius: Float, color: Color4b, outlineAlpha: Int = 255) { | ||
| drawGradientCircle(radius, 0f, color, color.with(a = 0)) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Add visual range indicator to KillAura module showing attack range:
Fully synced with KillAura settings:
Example: Enable KillAura → RangeIndicator, and a circle appears
around you showing your attack range. Green when targeting, red when idle.
Useful for: PvP spacing, visualizing attack range, timing engagements.
Demo
test_compressed.mp4
Configuration