[0.15.40] Logistic Bot Dispatch Experiments

Post all other topics which do not belong to any other category.
Post Reply
ASDFGerte
Burner Inserter
Burner Inserter
Posts: 14
Joined: Wed Dec 13, 2017 9:34 pm
Contact:

[0.15.40] Logistic Bot Dispatch Experiments

Post by ASDFGerte »

UPDATE 2: The following behavior has changed and therefore been "fixed" in 0.16.8. Thanks devs, now i can make what i originally wanted :)

I was designing a train loader when i came across imho weird behavior of logistic bot dispatch speed. These results would need to be confirmed by someone as it is not too unlikely i just did some stupid mistake. I sadly did not find any comprehensive explanations on how logistic bot spawn works (got tons of unrelated uninteresting links only).

From what i can see, assuming unlimited logistic bots, roboports, and resources in the logistics network, requester chests give these logistic bot spawn amounts:
  • A single requester chest:
    One logistic bot per tick (slow but understandable)
  • Two or more requester chests for n_{end} ticks:
    Image
    where f_{odd} is 0 from 1 to 30, 1 from 31 to 40, 2 from 41 to 50, ..., 7 from 91 to infinity (named accordingly, i have no idea what this is)
As an example, requesting for 100 ticks with a single chest will spawn 100 bots. Requesting with two chests for 100 ticks results in 543 bots in the air (5.43 times more for twice the chests). For 200 ticks, it is already 200 bots vs 2093.

My tests are in creative mod, as testing anywhere else is a real pain. Afaik it behaves the same as vanilla in all relevant aspects though. The remainder of the post is about test setup, so people can see if i did silly mistakes:
  • Overview of test (just general setup, yeah, which pixel are you supposed to watch), roboports with 14k logobots, duplicator chests for green circuits as item source in the middle
    Image
  • Small combinator setup to request for a set amount of ticks at lower right (i mostly used void requesters, tested a bit with normal requesters aswell - make sure the chests are on "set requests")

    Code: Select all

    0eNrNVW2OmzAQvcv8NhWQpN1a/bPnqFYWgSE7EtisP6JGEQfoPXqynqRjSFPKhkTZVmr5gTXYfrx572GOsG0Cdpa0B3kEKo12ID8fwdFOF0185g8dggTy2IIAXbSxqrCkCm1SmnZLuvDGQi+AdIVfQGa9uAnQmB05T2VSPqPzicWXwCNOYfL+SQBqT55wJDUUB6VDu+WVMruNJqAzjgGMjkwYNMkFHHhgjsDNemsatcXnYk/cAi8pyZaBvGpNhcrUynRoi3H/aYvGMtYurs7ibWcR9ZQfVUxenKGGsn/q+yjLrIX8mqKvyKfvNr/YV2RHJiDfX+7lBKl4rqIz55qs8+qVPXuyPvCTM6FxRfIIY9vOFzEjeZrGsu0KO3CU8P3rN95kgu/CBdjfXceGKVujo1OjOiN6d2CSQXtVW9Mq0gwF0tuA/T2ab1hkAfnifDYxINarBVNWb89V+n/Eav2mWKX/MlWnaxauT1eidQP772RqPRdc3BW52fZswa/NuYefmlw17HrWamo4ogvH+A3RQnQju+skX/qmB6iPg6XTA52cin3URePwD4yYf8v5JaHj6yJXOfnLCdizOGPA1+v8Q7ZKHx7Svv8B8iJt4w==
Notes:
  • As good as i could time it, requesting without circuits gives the same results.
  • For more than a few hundred ticks, there will be enough bots in the air to fill all requests rather soon.
  • I did not test what happens when chests are split across different networks or a lot of other options.
    update:
    • looks like this is logistic network local, making it quite annoying. A second requester chest in a different network appears to have no effect.
    • The second chest must be requesting something that is available, otherwise it does not count.
  • Related post for construction bots, reference only, does not apply to logistic bots: viewtopic.php?p=193621#p193621
  • Should these tests be correct, i am unsure if this counts as bug or just very unintuitive behavior.

Post Reply

Return to “General discussion”