Skip to content
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

event-slot for helmet,chestplaye,leggings,boots #3430

Closed
ExtraSmartMiner opened this issue Oct 4, 2020 · 1 comment
Closed

event-slot for helmet,chestplaye,leggings,boots #3430

ExtraSmartMiner opened this issue Oct 4, 2020 · 1 comment
Assignees
Labels
bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. completed The issue has been fully resolved and the change will be in the next Skript update. priority: medium Issues that are detrimental to user experience (prohibitive bugs or lack of useful implementation).

Comments

@ExtraSmartMiner
Copy link

when I was using "if event-slot is (player's helmet, player's chestplate, player's leggings or player's boots):" it would also think that it was slots 39,38,37,36 in a double chest

To do just do:
on inventory click:
if event-slot is (player's helmet, player's chestplate, player's leggings or player's boots):
broadcast "Armor"

It should only work for slots 39,38,37,36 in the player inv not double chests/guis

chest

Server: 1.16.3
Script Version 2.5

@ShaneBeee ShaneBeee added bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. priority: medium Issues that are detrimental to user experience (prohibitive bugs or lack of useful implementation). labels Oct 4, 2020
@ShaneBeee
Copy link
Contributor

Tested and can reproduce.

@ShaneBeee ShaneBeee self-assigned this Oct 5, 2020
@ShaneBeee ShaneBeee added the completed The issue has been fully resolved and the change will be in the next Skript update. label Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. completed The issue has been fully resolved and the change will be in the next Skript update. priority: medium Issues that are detrimental to user experience (prohibitive bugs or lack of useful implementation).
Projects
None yet
Development

No branches or pull requests

2 participants