-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
World hopping - mining Adamant / Runite timer and world logger #6659
Comments
Duplicate of #3097 |
Hi @deathbeam I opened this from your advise received on #6600 and considered it different to #3097 (which seems very broad and without scope for world tracking?). Should I contribute on #3097 (or #3924 for the thieving aspect) or should I make a seperate thieving world tracking feature request? Thank you again. |
or #4557 would be a nice canidate to include world tracking functionality? |
I guess this would be better as a comment on 3097 mentioning that you'd find it helpful to persist timers across world hops as well. It's essentially the same request with a small bit of extra functionality. |
Thanks @Nightfirecat |
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always
frustrated when [...]
When mining rune ore and keeping track of the timer for re-spawn, I find it frustrating to start various different timers and trackers to know which world will next re-spawn for me to mine.
Describe the solution you'd like
I would like a plugin that displays a list of worlds that I've mined a certain rock in even after I've hopped world. As well as a 'countdown' until that resource is available again in that world. This could include Adamant and Runite rocks as most others are not hop-mined.
Describe alternatives you've considered
Running timers and stopwatches. This quickly falls apart as it can take a varied amount of time to mine something.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: