-
Notifications
You must be signed in to change notification settings - Fork 105
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
Kits - Proposal to add an option for renamed items #245
Comments
Comment by Dark_Arc I'm working on something which should replace kits entirely. :) |
Comment by Dark_Arc Or rather be a more useful kit system with the old still in the background. |
Comment by TheE @Dark_Arc: Sounds interesting. Anything to share? I found the current kit-system quit usable within other (read: personal) components, but, as a kit system itself, lacking most options that are needed. But this is more a problem of CommandBook lacking a proper and complete syntax for specifying item-metadata (CMDBOOK-2341 might be related), than a problem with the kits-component itself. Even if it might be a good idea to use yaml instead of a plain textfile. |
Comment by Dark_Arc The issue with item meta is bukkit doesn't have great support for item meta. They did implemented a few things that might allow it to be worked around though. |
Comment by TheE I was thinking at something similar to the Item syntax ME4502 implemented in CraftBook (see [here|https://github.com/sk89q/craftbook/blob/master/src/main/java/com/sk89q/craftbook/util/ItemSyntax.java]). It should cover all metadata currently possible within bukkit. |
CMDBOOK-2370 - Reported by amlette
Hello :)
I use the '''CommandBlock''' and included it on a kit to get it faster.
By default, when '''CommandBlocks''' talks to a player, the consol return the name "@".
To replace this automat's name by my server name (for example) I use an Anvil.
So I've got a suggestion.
'''Can you make an option to add item name directly in kits ?'''
+Something like+ :
Thank you for your answer.
The text was updated successfully, but these errors were encountered: