<yueh> tterrag: not possible
<tterrag> lol
<tterrag> I mean, it is
--> tterrag ([email protected]) has joined #AppliedEnergistics
* Topic for #AppliedEnergistics is "Applied Energistics 2 - Download: http://ae-mod.info/Downloads/ - Wiki: http://ae-mod.info/ - 1.10: ask shartte"
* Topic set by raydeejay on 2016-10-14 19:48:02 UTC
<***> Buffer Playback...
<tterrag> [13:11:02] I mean, it is
<***> Playback Complete.
*** Mode #AppliedEnergistics +Ccnt by stormlight.esper.net
* Channel #AppliedEnergistics created on 2013-01-25 19:24:41 UTC
<yueh> we need 8 (or 14) locations
<tterrag> I don't follow
<yueh> it would kinda be possible. but thanks to forge being a piece of crap, they actively prevent any sane implementation
<tterrag> can you please be specific?
<yueh> IGridHost aren
<yueh> 't just TEs
<yueh> they can be anything
<yueh> but thanks to forge not patching TE to implement the CapProvider interface, we can't use this as alternative to IGridHost
<tterrag> what??
<yueh> of course it does not solve the issue that caps only have 6 sides (7 with a stupid implementation) while we need 8 or 14
<tterrag> TileEntity absolutely implements that interface
<tterrag> also, I'm only asking for you to *consider* caps, not convert your entire API to them
<tterrag> just *also* look for caps as a source of an IGridHost
<yueh> in my case it only implements the serialiser interface
<yueh> not the provider
<tterrag> what do you mean in your case
<yueh> ICapabilityProvider
<tterrag> TileEntity implements ICapabilitySerializeable extends ICapabilityProvider
<tterrag> it's on the hierarchy
<yueh> which is just then has (srsly. that's useless) and getCap
<yueh> hm. maybe new. i looked at it in the inital port, but it was simply not possible at that point
<tterrag> not new...
<tterrag> but anyways
<tterrag> I'm just asking for, when you are scanning for IGridNode, to call getCapability as well as checking instanceof
<yueh> not really planing it. my idea was more about completely abstracting TEs away and operate on our own datastructure
<yueh> so creating a new node would already take care of registering them for the pathing
<yueh> would also avoid the issue with caps being  technically uncachable
<tterrag> as long as it can be done modularly without implementing crap on the TE, I'm for it
<tterrag> that's the whole problem we are dealing with atm
<yueh> but that's a bit more work, as i have to hook into the chunk unloading etc to correctly clean in up and so on
<yueh> and simply no time for it