Interfaces vs Capabilitys

[Pingubro]

Good evening,

 

I am very curious about this new thing called "Capabilitys" because I

have two questions I am asking myself all the time:

 

1.) When shall I use Capability, wehen Interfaces?

So my answer to myself is use Interface for Complex things e.g.

Chests and large Inventorys or Complex Machines. Capabilitys seem like

they are for Simple Machines and Simple Inventorys.

 

I know there are way more Capabalitys and I understand they primary

advance to Interfaces because of alle the casting.

 

2.)Is every TileEntity implementing Capabilitys or is it like a need Helper

for us Modders?

In that case I am thinking about things like conduits sending Power, Items

and Fluids. Who gurantees that a Capability is implemented and not an Interface.

 

Thanks in advance.

Pingubro

[larsgerrits]

Here's the documentation on capabilities: http://mcforge.readthedocs.io/en/latest/datastorage/capabilities/. This explains capabilities, and how to use them.

 

1) You should be using capabilities if you want your mod to be able to work with other mods, e.g. have another mods pipes be able to extract and input items into your inventory. You can use interfaces if you are only gonna use it for your own mod, and no other mod has to use it to work with yours.

 

2) Forge has added capability support for the vanilla inventories, e.g. chests and furnaces. Ever modder should support capabilities. The main goal is, for inventories in this case, to say

TileEntity#hasCapability

on ANY

TileEntity

, and if it returns

true

, get it using

TileEntity#getCapabilit

and manipulate that inventory and let the

TileEntity

itself handle everything else.

 

Other people probably know how to explain it better, but this what my general idea of capabilities looks like.