I find that some blocks don't need to have a TileEntity and is needlessly taking up resources. For example, the heal block can have all its events be in the block itself rather than creating an additional TileEntity.

Does anyone have a reason why some blocks should create a TileEntity or is it actually better to remove them?

If they don't store anything more than 4 bits of information and don't need
an update event, they can be a block

On Wed, Sep 18, 2013 at 2:50 PM, wooky [email protected] wrote:

I find that some blocks don't need to have a TileEntity and is needlessly
taking up resources. For example, the heal block can have all its events be
in the block itself rather than creating an additional TileEntity.

Does anyone have a reason why some blocks should create a TileEntity or is
it actually better to remove them?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/77
.

Yeah, the blocks in question store absolutely no data, which is why I thought having a TileEntity for them is unnecessary.

From what I understand, in forge, a tile entity barely takes up any additional resources at all. I'm not too bothered about us using tile entities if they aren't too heavy.

I'll talk to the forge guys to find out exactly how heavy they are. I don't want to optimising this if there's no reason not to, though.

I've been told TE's have almost 0 impact on performance.
If you're generating huge areas of landscape from a single block then there IS a performance hit, but we're not doing anything like that at all.

I feel optimising this would be like a drop in the ocean, and only serve to fragment the way things are implemented within the mod.

Closing this one

For note, TileEntity's aren't just for saving data. They are also useful for running code consistently at a specific location in the world.

^ This.
Yes, the blocks don't have the ability to run constant updates like a TE does.