I have a tile entity that won't be storing items. So it wouldn't need a container, right? Am I imagining the concept of the container incorrectly? Doesn't the tile entity itself store all the information and the container is just... I'm not even sure what the real purpose of the container is. Defining what items are accessible from what tile entity?

 

The gui handler needs to pass a container (in getServerGuiElement) for a gui to be opened, so I must need a container class, but it would literally do nothing. Which confuses me.

1.if its some kind of tile entity without any gui, or anything wierd, than nop, i dont think so, (IM NOT SURE >.<)

2.containers are a wierd & confusing thing, containers probably do something hidden in the background, something that we cant see or value.

Sorry, I realized that I didn't specify: I need to have a gui for this tile entity.

Just make a container but dont add any slots. It kinda acts like an interface for saving stuff to the tile entity.