Finally, we flip it to get item count iron-plate = 0 AND time passed = 145s. Next, we take the condition where time passed = 145s AND item count iron-plate = 0. First, we take our basic time passed condition, still at 145 seconds. There are 3 specific condition cases we need to test. We will take out biggest magnitude difference case, item count. We will remove all unloading/loading inserters and infinity chests.ДЄs a dependency for other attributes, we need to first establish the AND condition behavior. It is here that we will modify the attributes important to our test. If the wait condition cost is based on changes to the condition, testing these attributes won't be viable (due to the highly dissimilar nature of a requisite un/loader for fluids/solids).ДЇor testing, we will take a 5x paste of our previous test. Such tests are dependent on the first part of this test. (or item count on a train with no cargo wagons). Another possibility is to test fluid count on a train with no fluid wagons. This could yield an interesting performance conclusion. In terms of the number of slots needing to be checked, a fluid wagon would have 1/40 as many 'slots'. It was theorized to cost as much as item count at that time, though that is baseless speculation. There are two possibilities, either all wagons are checked for their item count every tick, or the check only occurs whenever a wagon's content changes (like when an inserter grabs some items).ДЄnother possibility we did not test is the fluid count wait condition. An example of this would be the item count condition. If a performance difference is measurable, it also serves as proof that a cost to a particular wait condition is based on continuous checks, rather than checks performed when the attribute changes. Since we are ANDing our conditions, we will no longer need to have any actual loading/unloading performed. This will be one of the things we aim to test. In theory, wait conditions joined by the AND operator would not perform any further checks if the first condition was not true. One such case is where multiple wait conditions are applied. However, there are more possibilities that were not covered there. Our previous testing conducted in test-000019 covered the basic cases where a single wait condition is applied. If not using the time passed or inactivity wait conditions, you should put a time passed AND condition preceding the condition you want to check. Test-000030 : Part 2 of testing train wait conditions Factorio Version 0.16.51 The TLDR

Fluid wagon factorio