-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
Support for minecraft's native IDs and data #2547
Comments
I'm curious why you feel this should be added? Here is why I vote no, you can easily create your own aliases within a script, ex: aliases:
my item = minecraft:stone
command /test:
trigger:
give player 1 of my item |
|
Are you meaning abolish the alias system all together? set block at player to minecraft:oak_stairs[waterlogged=true,half=top,shape=inner_left] etc... IF you were suggesting the addition of this (on top of aliases), I would understand, but straight up abolishing the alias system I feel would be a no go. |
Abolishing the current alias system is definitely not a good idea... however if you mean adding Minecraft native IDs as an alias to Skript, e.g. using |
@ShaneBeee I don't mean abolishing the current system. Sorry for any confusion! |
No need to apologize, but thank you for the clarification. |
I'm not sure if this is a good idea, because Minecraft ids change between versions. |
Suggestion
Description
Since Skript aliases are mapped to Minecraft's IDs anyways, I think it'd be a great (yet time-consuming) enhancement to allow players to use minecraft's native IDs as a replacement for aliases.
The text was updated successfully, but these errors were encountered: