-
Notifications
You must be signed in to change notification settings - Fork 9
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
certain bosses not opening #22
Comments
There's probably an issue with the log file. Head to There's an extremely rare issue where instead of an entry being appended onto a new line it is added to an existing one. This causes the plugin to break as the file isn't in the correct format. If you send me your file I can fix it for you, or you can fix it yourself. For example, instead of the file being like this:
It is actually like this
I have not been able to pinpoint why this occasionally happens to random people, so I can't prevent the problem from happening again :l |
giant mole.log I just found it, it turned out the whole line was extended over to the right (starting about the length of a normal entry) so itd look like a double entry but it was just a single with a tonne of spaces at the front. Works now, thanks mate. |
Yeah, i found the same issue around line 768, Glad you figured it out though :) This is a really annoying issue and I wish I could pinpoint why this happens randomly. Sorry you ran into this problem :( |
Thats okay dude! I love the plugin, the fact it mixes the collection log with loot tracker is awesome! I recommend it to a few people, especially when I share screenshots of it, the only thing id consider is if you hover over the collection log section it could show what KC the item was obtained (Or multiple KCs) would be neat, but im happy as is! |
so for example my issue is the Giant Mole boss, It worked up until around 1500-1600KC, now when I click him the yellow line appears but it doesn't take me into the loot screen, all other bosses etc work other than the mole.
The text was updated successfully, but these errors were encountered: