| Search |
|---|
| ID | Rating | Category | Description | Screenshot | Date |
|---|---|---|---|---|---|
| 727 | 😟 | General | It would be great if the `Get First Locked Id` respected the current requests, or there is a block that allows us to know how many requests are open for a given item. The attached behavior would be great to have. It would allow a frame to keep all it's currently locked slots full. The behavior here will request all the locked slots ... unfortunately when it re-runs the `Get space for item` does take into account requests and then returns '0' and then the behavior requests 0 of the item, thus clearing all the requests. I have tried using a compare block to only make the request if it is not 0 ... but then this runs into the issue where it would ping-pong between values. For example: 1. Lock 100 metal bars worth of slots 2. Behavior requests 100 metal bars 3. Behavior re-runs, and calculates 0 free space for bars, so we don't request 0. 4. Bots deliver 60 bars. 5. Bots take away 10 bars. 6. The behavior re-runs. At the start we still have 40 bars requested and we have 50 bars in the inventory. 7. The behavior calculates how many bars we can hold => 50 bars in inventory - 40 bars requested = 10 bars 8. The behavior requests 10 bars, clearing the 40 bars requested. 9. The behavior re-runs. At the start we now have 10 bars requested and we still have 50 bars in the inventory. 10. The behavior calculates how many bars we can hold => 50 bars in inventory - 10 bars requested = 40 bars 11. The behavior requests 40 bars, clearing the 10 bars requested. 12. The behavior re-runs, we have 40 bars requested, so GOTO step 6. So above you can see that we will bounce between 10 and 40 bars requested. I am getting around this by just having a script per frame that just requests a hard-coded amount of resources but I'd love to be able to automate this into a behavior. | 2023-08-19 20:24:19 |
| ID | Reply | Author | Date |
|---|