What steps will reproduce the problem?
What is the expected output? What do you see instead?
Shooting is impossible, eating is impossible (except rare cases when you shot on ground which you can dig).
What version of the product are you using?
Do you have an error log of what happened?
I have one but it is for another bug (only error log): here
I don't understand what this means: "Create big amount (about 20) MapView with recipes (only with 1 "page"). Bug appear on another world too."
Can you clarify please?
It may be not be important what I have wrote there. Anyway, bug was appear on update from some dev build (probably before after yesterday's commits).
For this with Map, this means that I created wall with MapViews on itemframes in Dungeons world. Player can't change what it show. This bug also appear in OldRPG world.
I'm still not very clear on the problem here. So you're creating a large wall of item frames with a different map view in each frame?
What do you mean by "player can't change what it show"? They can't scroll the menus in the frames? Do they have the scrollingmenusign.use.map.framed permission node? Are you (or another admin) able to interact with the maps?
Try running in debug mode: /sms set debug_level 1 and see what is logged on the console when someone tries to interact with a framed map.
/sms set debug_level 1
And what does this have to do with eating & shooting?
Those MapViews are very simple and just show background, nothing else.
"And what does this have to do with eating & shooting?" I don't know, if I might to say true ;)
Just tried to show all options (maybe those stupid too, nevermind). Anyway, my second sentence in comment is probably this, I'll check older build to make sure.
OK, I tested and I see that build 25 gave something that shouldn't. In build 24 I can use normal bow and food.
Yep, found & fixed - try build #57.
isCancelled()/setCancelled() with the PlayerInteractEvent is really weird. AIR click events arrive with isCancelled() == true, but still allow interaction with things like food & bows. But if you do setCancelled(true) on the event, it stops that interaction (even though the event was already cancelled). Daft Bukkit behaviour, but I've fixed SMS now to only cancel the event when it really needs to be.
Oh, the stack trace you posted should also be fixed now, just needed to do a little extra null validation when migrating users. If a UUID can't be found for a particular username, it will just make the menu/view owned by the console. This is unfortunately likely to be the case if your server is in offline mode; if you're using Access Control you can go back afterwards and change menu/view ownership.
Indeed. Quick and awesome fix. Thanks.
To post a comment, please
or register a new account.