-
Notifications
You must be signed in to change notification settings - Fork 367
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
Inventory -> ItemContainer #1107
Comments
Just re-read the first sentance. Yes. I agree. |
Calling a chest, for example, an inventory doesn't sound right. While Mojang doesn't use it this way, I could see an argument that a chest does indeed have an inventory. However, a chest itself isn't an inventory. A chest cannot be an inventory, but it can have an inventory. Using the inventory terminology, a chest would be an inventory in Minecraft, which doesn't make sense. On the other hand, a chest could be a container or have a container, which means it works out fine with the container terminology. The player's inventory, on the other hand, makes sense to be an inventory because a player isn't an instance of a container, it has a container as a field. Therefore, the container can be called an inventory because it is something the player has, and not something it is. |
I also agree with
|
can someone else PR this please because I did ScreenHandler :P |
Im not a fan of this change? Almost seems like its being cached for the sake of it. |
¯\(ツ)/¯ it's your opinion, but I've explained my reasoning pretty thoroughly. it's not just for the sake of it. |
The arguments for Inventory have compelled me to believe it is fine. |
This issue is assuming that #1106 is merged. Discuss in this issue as if it has been.
The word "inventory" in the game, both internally and externally, is used to refer to the player's inventory only. Many strings in the game refer to this
Inventory
class as a container, and many places in yarn already call this a container, in fact (seeLootableContainerBlockEntity
,LockableContainerBlockEntity
, etc.).I am proposing adding an Item prefix to it, for multiple reasons. Firstly,
Container
itself is too vague to be used alone for any class name. There are numerous classes already suffixed withContainer
that bear no relation to this class. Adding an Item prefix to it clarifies that it is something that contains items. Secondly, prefixing withItem
leaves ample room for modders to makeFluidContainer
s orEnergyContainer
s or whatever and not having confusing terminology with the item one being simply,Container
.The text was updated successfully, but these errors were encountered: