theoriginalbit / peripheral-framework Goto Github PK

Because the owner and provides parameters are the same in the @API annotation in com.theoriginalbit.peripheral.api.package-info.java, FML goes into an infinite loop, repeatedly putting

[Client thread/TRACE] [FML/]: Removing upstream parent peripheral-framework from APIContainer{peripheral-framework|peripheral:@VERSION@}

into fml-client.log (resulting in a massive 3.5 GB of errors). My best guess at why this happens is because Forge is trying to load the API before itself.

This would add a lot of convenience to some function calls from lua, e.g. to skip quantity/slot/side etc parameters and let the java backend handle the missing parameters.

I am pretty new to modding, but I can get basic blocks and items going, but I just get lost when it gets to tile entities or using APIs or anything more advanced.

See Computronics for example of OC component implementation