-
Notifications
You must be signed in to change notification settings - Fork 5
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
Hotbar items stop working when moved to another slot #11
Comments
This was intended to work to prevent issues with having two of the same item. I'll implement a fix using nbt. |
Amazing, ty sir! |
@artulloss Is it possible to make an option for it to not clear inventory when you login aswell? |
I feel like your use case is not what this was intended for- this is for menus in like a lobby. Mind telling me what you're trying to do? If it's just commands to be clicked on items I suggest this plugin. https://github.com/TheAz928/ItemCommands |
Sorry I guess I was just pushing the limits of your plugin I guess. I was intending to use it as the plugin you linked is used. Thanks for the help. My discord is Danub#4689 if you'd like to hear about what I'm trying to do. |
Didn't work. Mine is adam#9876. |
whoops, lowercase D. Sent you a request. Solved the issue using https://github.com/TheAz928/ItemCommands and https://poggit.pmmp.io/ci/IceCruelStuff/SpawnWithItems/SpawnWithItems |
Any issues regarding pocketmine spoons will be disregarded and closed.
Make sure that you can produce the bug without any other plugins.
Describe the bug
When you have a hotbar and you have the locked-hotbar option disabled the item will work in the desired hotbar slot only. Then once moved to another slot it doesnt work, then once moved back to original spot it still doesnt work.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected the hotbar item to be able to be used whenever it is clicked regardless of the hotbar slot it is in when hotbar-lock is disabled
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: