So I found the problem, though it's not a fault of the library, neither a compatibility issue between cc and transport drones... The error is the correct result of a weird (though technically valid) situation created by editor extensions - it creates an item in data with place_result
set to an entity that won't be created until data-final-fixes... My and transport drones' data-final-fixes happen to run during this period and we both need to work with this item, but it's invalid, so it ends up throwing an error...
What happens is a bit convoluted, but it goes somewhat like this:
- editor extensions creates the item in data
- transport drones' data-final-fixes creates a recipe for the invalid item, so it can be transported
- cc in turn needs to generate a signal for the recipe, for which it asks rusty locale what the locale is
- rusty locale tries to find the locale, which happens to fall back to the item, which then falls back to the place_result
entity
- the entity doesn't exist, so rusty-locale rightfully throws an error, since the state of the prototypes is not valid enough to determine the locale correctly
- (if there were no errors, editor extensions' data-final-fixes would run here, creating the missing entity)
I'll try to ask Raiguard if they could do something about it at their end, as I don't think any amount of hacking is going to solve this :D