Reporting a bug

Reporting a bug

Bugs and feature requests both go to Issues. Check Troubleshooting first - several common reports are settings rather than bugs.

What to include

• Plugin version - shown on the plugin's Hub listing in RuneLite.
• RuneLite version - from the client's title bar or its About panel.
• Account type - Ironman matters, because the shared-loot grey-out only runs there.
• Where it happened - the NPC or boss name, and the encounter if it was a raid or instance.
• What you expected, and what you saw instead. One sentence each is plenty.
• The settings you changed from their defaults, or a paste of your RuneLite profile export. Most bar bugs are specific to one combination, and the defaults are the fastest thing to rule out.
• A screenshot, or a short clip for anything about timing. A bar that lingers, drains, fades or flickers cannot be judged from a still frame.

Say explicitly whether Hide Native Health Bar was on. It changes what is on screen, so a screenshot means something different depending on that one setting.

Things worth knowing before you file

• Other players' bars are percent-only. There is no max HP available for another player.
• Aggression is a flat list, so a monster aggressive in one location and tolerant in another gets one answer everywhere.
• A bar that reads a percentage instead of a number usually means that NPC id has no known max HP. Include the NPC name and the bar will get a row.
• Shield and charge bars need a live capture to add for a new encounter. If you can record the fight, say so in the issue - that is normally the blocker.

Requesting a feature

Say what you want to see on screen and when. Screenshots of the current bar with an annotation beat a paragraph of description. Settings that only make sense for one encounter are usually better as an automatic behaviour than as another checkbox, so it helps to say when the thing should appear as well as what it should look like.