This website is a work in progress.
Please report any issues to our Discord server, or thebug report forum.

Featured Groups Featured Players

DropTracker.io

A community-oriented, all-in-one loot and achievement tracking system built for Old School RuneScape clans.

Track your drops, compete on leaderboards, and share your achievements with your clan.
The DropTracker is an approved third-party Old School RuneScape® client plugin that seamlessly integrates with your Discord server.

Community Statistics

5,441
Tracked Players
50M+
Achievements Tracked
620B+
Loot Tracked
87
Registered Groups
A new plugin update is in the process of being developed (v4.1).
In hopes of receiving some additional feedback and testing prior to attempting to get the update approved; I've created a thread that outlines what will change & what you can expect.
You can read more about the upcoming updates here
If you have any thoughts our suggestions, you know where to go :)

RuneLite Big Upcoming Changes

posted by joelhalen ·
There will soon be an update to the DropTracker that allows players to track their drops using our API instead of relying on discord webhooks for transmission of data.

This will be highly recommended for all players; but will come alongside a warning for enabling it.

For the time being and until these changes go live (stay tuned here for updates), the DropTracker is only going to be around 10% functional.

If you want to read more about the process of this update feel free to grab the Clan Leader role from the roles channel.

Last night runelite approved our plugin update request!

Droptracker plugin was updated to version 3.83:

  • Fix PB tracking for Grotesque Guardians
  • Fix PB tracking for Fight Caves (TzTok-Jad)
  • Fix PB tracking for Inferno (TzKal-Zuk)
  • Improvements to how we are handling webhooks
To receive this update you need to restart your client or visit the plugin hub to update!

Enjoy and let us know if you run into other issues or have other suggestions!
Bug Report

Hall of Fame contains non-group members

posted by joelhalen ·
It seems that as a result of the way we have our cache structured, we are not properly removing players from their respective groups' cached loot data when they are removed from the group.

This relates to the way we store data in Redis, and the fact that the keys we delete on each 24-hour invalidation only include player-specific keys, not those that are involved in z-scores; which is where loot totals are extrapolated from.

Suggestion

Track loot events effectively

posted by joelhalen ·
When players receive drops, collection logs, etc, we oftentimes send a number of messages in quick succession, and our backend reads each one individually with no context to the last one.

It would be ideal for us to have a way of knowing which "event" each drop a player sends came from. This would help us be able to more accurately track how many kc a player has tracked at specific bosses within the system.

Could use a simple integer on the client that signifies how many events have been processed, incrementing it each time a new one occurs.

This could also help us group messages together; for example if someone receives a drop that is also a collection log, we could send a message containing both sets of information instead of sending two; or note that its a collection log in the drop embed

Bug Report

Discord Bot Hall of Fame duplications

posted by joelhalen ·
Hall of fame is currently duplicating entries and sending new messages every few hours/days, seemingly at random.

Needs a bit of inspection...