Skip to content

Add AC-130 Gunship plugin#11228

Open
bobbyswhip wants to merge 2 commits into
runelite:masterfrom
bobbyswhip:ac130-gunship
Open

Add AC-130 Gunship plugin#11228
bobbyswhip wants to merge 2 commits into
runelite:masterfrom
bobbyswhip:ac130-gunship

Conversation

@bobbyswhip
Copy link
Copy Markdown

AC-130 Gunship

MW2-style AC-130 killstreak mode for Old School RuneScape. This is a client-side visual effect only — no actual damage is dealt and no game rules are broken. Other players cannot see the effects. It is purely cosmetic entertainment for streamers and content creators.

Features

  • Thermal Vision Overlay — Green-tinted night vision with scanline effects and white-hot player highlighting
  • Orbiting Camera — Automatic slow orbit around your character at a top-down angle
  • Three Weapons — 25mm Cannon (rapid auto-fire), 40mm Bofors (medium), 105mm Howitzer (heavy with screen flash and smoke)
  • Projectile System — Visible projectiles descend from altitude to the targeted tile
  • Ground Explosions — Impact effects with explosion graphics and smoke clouds
  • Kill Detection — Players in blast radius play death animation and fade from thermal view
  • Kill Feed — Animated slide-in kill feed with fade-out transitions
  • Score Popups — Floating "+100 KILL" text above eliminated players
  • HUD — Weapon name, ammo bar, kill counter, fire readiness indicator
  • Crosshair — Dual-circle targeting reticle with range tick marks
  • Sound Effects — Distinct fire and impact sounds for each weapon

Controls

Key Action
Alt Toggle AC-130 mode on/off
1 Switch to 25mm Cannon
2 Switch to 40mm Bofors
3 Switch to 105mm Howitzer
Left Click Fire weapon (hold for 25mm auto-fire)

Repository

https://github.com/bobbyswhip/ac130-gunship

License

BSD 2-Clause

MW2-style AC-130 killstreak mode with thermal vision overlay, orbiting camera,
three weapons (25mm, 40mm, 105mm), kill feed, and score popups.
Client-side visual effect only - no game rules broken.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@runelite-github-app
Copy link
Copy Markdown

runelite-github-app Bot commented Mar 26, 2026

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@runelite-github-app
Copy link
Copy Markdown

This plugin requires a review from a Plugin Hub maintainer. The reviewer will request any additional changes if needed.


Internal use only: Reviewer details Maintainer details

@riktenx
Copy link
Copy Markdown
Member

riktenx commented May 13, 2026

generic player highlighting in this manner is not allowed as it is abusable for scouting and does not respect player privacy concerns

@riktenx riktenx closed this May 13, 2026
@bobbyswhip
Copy link
Copy Markdown
Author

generic player highlighting in this manner is not allowed as it is abusable for scouting and does not respect player privacy concerns

show me the game rules that state this as being disallowed, from what i see the discord just blanket denies anything they deem as AI slop.

@pajlada
Copy link
Copy Markdown
Contributor

pajlada commented May 21, 2026

@Unmoon
Copy link
Copy Markdown
Contributor

Unmoon commented May 22, 2026

IMO the only concern is highlighting players in wilderness, so if you can disable the functionality in wilderness, this should be OK.

@Unmoon Unmoon reopened this May 22, 2026
@riktenx riktenx added the waiting for author waiting for the pr author to make changes or respond to questions label May 22, 2026
@bobbyswhip
Copy link
Copy Markdown
Author

The rules specifically mention "Level-based PvP player indicators," which this plugin is clearly not. Additionally, there's a rule against plugins that indicate players in an opposing clan during PvP. The "Player Indicators" plugin currently appears to break this rule, yet it is included and distributed with every RuneLite client.

It feels like the rules are being applied inconsistently here. Could you please take another look at them? I want to make sure we're all following the same standard.

@runelite-github-app runelite-github-app Bot removed the waiting for author waiting for the pr author to make changes or respond to questions label May 23, 2026
@cdfisher
Copy link
Copy Markdown
Contributor

Player Indicators has the option to highlight players in your own clan, not an opposing clan.

Generic player highlighting is on the RuneLite rejected features list:

Highlighting "Offline" Friends (and generic player highlighting): Not included to respect players with their messaging mode set to Private and to avoid harassing players (see #951)

@bobbyswhip
Copy link
Copy Markdown
Author

sorry i have been mixed up it's the entity hider plugin which does this (combines with player indicators to make it more visible) you can up entity hider so that it HIDES your entire clan which makes only your enemies visible - player indicators is then used to label the opposing clan.

In conjunction these two plugins very specifically break the rules you allege to follow.

@cdfisher
Copy link
Copy Markdown
Contributor

That still just ends up showing any players who aren't members of your current clan, not specifically marking members of an opposing clan, or serving as a generic player highlighting feature, which is why that's considered ok.

There is some subtlety to the distinction but there isn't any deliberate inconsistency to how the rules are applied on our end.

@bobbyswhip
Copy link
Copy Markdown
Author

that's clearly false when it's used for unfair advantage in PvP, specifically it's used by bots to jam things like wilderness levers etc.

if that's allowed then I will be abusing it shortly

@raiyni
Copy link
Copy Markdown
Member

raiyni commented May 23, 2026

It's not an uncommon occurrence to ask authors to disable plug-in features in the wilderness.

@riktenx
Copy link
Copy Markdown
Member

riktenx commented May 23, 2026

doesn't build

@riktenx riktenx added the waiting for author waiting for the pr author to make changes or respond to questions label May 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

plugin added waiting for author waiting for the pr author to make changes or respond to questions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants