#**P2P Automation : Platform Logistics**

1 messages · Page 1 of 1 (latest)

upper gate
#

Looks very promising!
What are predicted performance bottlenecks?
How does automation works? For example, can you have transport ship deliver uranium ore from nauvis to system edge factory space platform, craft uranium ammo there and then have promethium miner regularly resupply from it with uranium ammo and left promethium chunks to be converted to science packs?
I really want to have specialiased ships, instead of big everything-in-one current ships.

#

Also, what about throughput? If you need to transfer 50 stacks of items and have 50 cargo pods free on both platforms, how fast can they be send?

pearl widget
#

Performance : So far, I added plenty of requests and they were all resolved under the same tick without any performance impact, but I'm currently making sure the requests are spread over several ticks, so it's much sturdier if someone ever wanted to make tens of platforms and hundreds of requests.
The current plan is to resolve at most 1 request every tick per platforms. Which means upwards to 60 requests per second per platform (which is, I think, a lot). But I might put a setting to allow the user to resolve more requests per tick.

Throughput : I don't have the code under my eyes RN but I'm pretty sure P2PA will try to use every available cargo bay to fulfill a request if needed when it triggers.

#

Each cargo pod will be filled with upwards to 10 stacks in order to respect vanilla behavior. A platform will not send more pods than necessary. At least one stack will be sent each time (it doesn't need to be a full stack).

#

And yes, you should be able to make specialized ships. Although it will require you to think a bit about the schedules and your circuits automation.

#

Currently, P2P Automation doesn't interact with the circuit network at all. I thought a lot about this and I think you can still do a lot of things without that, because you can base the behaviors of your ships on the items that are inside them and trigger the schedule under circuit conditions.

#

If my code is somewhat correct, the making and sending of pods should respect the throughput of vanilla. A bay won't create a pod if it's busy.

#

Altough, for now, my design choice is that 2 platforms will only be able to exchange items if they are at the same space location.

#

I might allow a setting to extend the range, but the mod isn't meant to allow you to exchange items for free between 2 planets orbits.

#

Did I answer your questions ? 🙂

upper gate
pearl widget
#

Once a request is registered, if the provider platform is in range and has at least the amoung of items specified in the request threshold, the provider will try to fulfill the request and send items.

#

Same behavior than requester / provider chests.

#

And I think about the same behavior as LTN

#

And you cannot (at least for now) use circuits to disable a request.