I have the exact same issue here, however if what you say is right about it being a modified welder, then I'm pretty sure adding the argument scan=welder MIGHT make it work, it all just depends on how TIM handles it. Haven't tried this myself yet, but it could possibly work

Unfortunately it's an issue with PBs. If you need sorting, use Automated Inventory Sorting which will work with this mod.

The issue is PBs do not support inventory properly. That is a problem with PBs, not with modding unfortunately. Once Keen fixes that, it will work, but until then use the mod I listed above.

Speaking of TIM and NCF... does/can NCF expose any callable API's? IE the functions for the NCF to call the assembler to queue up items to be built? this would allow TIM to see if NCF is installed (or a config flag) and use it for keeping items in stock... i kow this is a bandaid to a larger issue that KEEN should fix.

also i'd like to point out at some point someone might need to do something like buckett/forge. a base set of MOD API's for modders to use that are missing from the main app so each modder does not have to implment it them self and all the issues that can come from that.

what is a PBs?

@Damjan - PB = Programmable Block.

TIM depends on that entirely because TIM is a raw script loaded into a PB and executed via a timer block. So TIM can only use objects and methods actually exposed to it via the PB.

For example if an in-game object / method / set of API calls aren't accessible to the PB then anything depending entirely on the PB for those things is sol.

The PB's have come a long, long way since their initial inception. However they're still a far cry from the full capabilities when using a real project plugged up to the full API, and I think they're supposed to be.

Considering all of that though, TIM does a hell of a lot.

However there's a reason the PB has limits. It's not supposed to replace a fully fledged plugin solution. You can probably think of a PB as a limited lightweight go-to for simple (or moderately complex) things that don't need the full power (and overhead).

One can just whip up simple scripts, slap them into a PB and go. That's what they're designed for and they do that pretty well.

I have the NCF added to the storage of TIM with the name comment of [TIM Component] and it seems to do just fine.

^ does it actually extract? As seen when trying to set up refineries TIM obliterates priority and split specifications, reducing it to for example [TIM Ore] instead of [TIM Ore:P1:12345] etc. That seems to indicate it's operating partially, not fully. Wondering if it does the same thing with NCF.

I typically just set up a sort to drain NCF so I haven't actually tested TIM with NCF yet.

Hey Guys, to re-open an old topic rather then creating a new one.

am i correct iin thinking that NCF is registered as an entity and that is why the PB cant interact correctly with it?

im currently running through the TIM script and the NCF core .cs trying to find something myself.

does the Dev have any advice on .cs files i should be looking in and tricks i may try?