Hi,
i have a player who cannot claim his reward(s).

He had enough inventory space and was not crafting (i have seen this could be a reason for that message).
He told me he was just standing around and could not claim
Hi,
i have a player who cannot claim his reward(s).

He had enough inventory space and was not crafting (i have seen this could be a reason for that message).
He told me he was just standing around and could not claim
Hi,
any logs?
I am having the same issue. My players cannot turn in and collect their rewards... they simply receive a `Unable to issue your reward. Please contact an administrator` message. There are no console errors whatsoever. Does this have anything to do with the inventory changes in the last Rust update on Nov 4?
I can't find any Quests-Logs. Just the error in the chat for the player
It seems like this is related to having oxide perms enabled. I had this issue with a few of my players, but when I turned off oxide perms, it fixed it. Alternatively, it could be that if a player does not have command permissions they cannot receive rewards for quests.
UseOxidePermissions is false in my config, so I don't believe it is a permissions issue... and here's why: it turns out that the reward that the player was attempting to claim was a holdover from the wipe before that she never claimed. After she tried 3 or 4 more times, it eventually gave her the reward successfully. Additionally, she was able to claim rewards for quests she had initiated during this current wipe just fine. Why the holdover reward didn't work several times and then eventually did, I have no idea, but it made me wonder if Quests could use a similar feature like Backpacks and NTeleportation where you can configure it to force wipe pending reward data on map wipe? Seems like that might be worth the effort. Much like how, if enabled, NTeleportation will clear /home data on map wipe and Backpacks will clear inventories on map wipe, perhaps Quests should audit and clear unclaimed quest rewards for all stored players the same way?