-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
[feature] Add inventory/item manipulation. #69
Comments
This issue has been automatically marked as stale because it did not have recent activity. It will be closed in 7 days if no further activity occurs. If you wish not to mark it as stale, please leave a comment in this issue. |
This could be a potential interface for python player.inventory: dict[str, int | list[item|None] | dict[str, list[item|None]]] = {
"hotbar": [], # Always has a length of 9, defaulting to None
"armor": { # Always has the below, replacing the appropriate None with the item.
"head": None,
"chest": None,
"legs": None,
"feet": None
},
"hand": 0, # Replace with index of the current hand pointing to the slot in the hotbar key
"offhand": None # Replace with item.
"general": [] # The rest of the item slots, default to None
} I don't know how to implement this in the source code, nor do I know how item will be implemented. |
This issue has been automatically marked as stale because it did not have recent activity. It will be closed in 15 days if no further activity occurs. If you wish not to mark it as stale, please leave a comment in this issue. |
Is your feature request related to a problem? Please describe.
There isn't a good way to fully manipulate item NBT in vanilla.
Describe the solution you'd like
I think it would be great to have the ability to set an item's enchantments, id, etc. to values that might even lie outside of methods like Script API.
Describe alternatives you've considered
You can accomplish nbt manipulation with external editors, but it'd be great if it was apart of the API, like BDSX did.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: