This will keep fights intact you might not want to have removed, however, very old fights are also kept intact which can make your combat stats confusing (e.g. when there are a couple of hours in between all the DPS values are based on that).

This is to prevent graphic IDs triggering attack classifications of other types.

This gives info about other team members.

Less code to maintain with shorthands like Comparator.comparing.

Perhaps after actor despawned and restarted after the next hit? This can come in usefull when comparing total fight stats with the last fight. Some bosses might have 5+ minutes in between, giving a skewed image.

We can use the onLootReceived event (e.g. https://github.com/TheStonedTurtle/Loot-Logger/blob/master/src/main/java/thestonedturtle/lootlogger/LootLoggerPlugin.java).

Add new fight statistics for this.

Some additional situations seem to trigger this as well.

This gives some more information about whether the connection with Twitch is working properly. Perhaps also possible to display the JWT expiry time here?

The onGraphicChanged events do not trigger with players.

Could there be a way to show contents of the looting bags, seedbox and death storages? Would be really nice for UIM streamers.

Check the fonts of the following repository: https://github.com/RuneStar/fonts

Specifying a User Agent is recommended for other plugins as well.

This NPC does not despawn, but it can be detected via an animation. However, an animation is content specific and this is something we would like to avoid for lower maintenance.

It happens from time to time that the Twitch servers fail and give a 404 or 500 response. This is not caused by the plugin or any rate limits (that would return 429). This can come across as buggy, but we can easily accept these errors and just retry.

Seems that the value jumps to zero then, even though the default is 35.

Now it is updated the API is probably fairly stable.

Getting the damage is a bit harder due to hits on the same tick.

It looks like these are disease hitsplats? Also the NPC lookup goes to a different totem on the Wiki.

Do this via a fight that is always present and does not count towards the max fights?

This can happen when the actor is different, but the name is the same. When calling registerFightHit of other damages we should not override the last actor of the fight and check whether the actor is a match with the current one.

This might be something each streamer would like to switch.

When casting a spell directly (via the spellbook) the onInteractingChanged is triggered after the onGraphicChanged event. When attacking directly this is the other way around, which is required for the current mechanism.

Currently they are syncing both at the same time causing the extension to switch all the time between the two accounts. Add a setting to enter a display name of one of the accounts that should be synced when multi-logged?

Older code is still using the System.out.println statements.

MVP for now:

• DPS for all attack types (shared)
• Smite damage

This allows viewers to pick a certain state to inspect when something is going on where the inventory / gear changes all the time.

This should probably become a custom UI panel. Will also come in handy for future features.

Easy to confuse extension ID with token field.

This to prevent overload in the chat window when not having time to set up the settings again correctly.

See if there is a way to look the name up easily via external sources.

"Something has changed with Twitch. Please report this to the RuneLite plugin maintainer. The time of this message was 04:04:58. An error occurred with code: 400"

Gives possibility to add toggle to Twitch Extension to select view.

• 10 for low level NPC's
• 10 for high level NPC's (e.g. bosses).

When casting a spell one time without autocast it will nog register because of the interacting actor check.

There is a check with expiry time in place. Make sure this is working correct?

Should've been fixed with a previous update. Verify this.

Several options:

• Decode the JWT and deduce the expiry date from there.
• Show message on invalid HTTP response from Twitch (preferred as it might catch other JWT errors as well).

To prevent overload of messages. Throttle every 30 seconds?