The message "Quester not found for UUID" is quite spamming
PikachuEXE opened this issue ยท 4 comments
I just encounter this today.
If the file is not found for a specific player, it will keep logging this message to console (and log file)
I wonder if the continuous message is necessary
I'm guessing you mean when trying to use one of the new commands. It indicates that no UUID was resolved for the name provided (lookup failed). As long as you're not spamming the command, it shouldn't be an issue.
I don't think it's triggered by spamming commands :(
The message is located in Quests#getQuester
And the method is being used by many event listeners
The new commands do call getQuester() whenever a name variable is passed, but you're right, it is called elsewhere. I wouldn't know how to proceed unless you know from which event is triggering it.