Bulk loading items saves time cost for generic "pick up(g)" process #69244
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Balance "Bulk loading items saves time cost for generic pick up(g) process"
Purpose of change
Follow up #68214
Describe the solution
Apply same solution as #68214 to "pick up" action
Additionally, in #68214 there was an issue where the cost of moving large items was underestimated.
This time I will address this issue to some extent by placing a limit on the capacity that can be loaded in bulk. Although not implemented in this PR, we plan to backport it later to the Insert action as well.
Describe alternatives you've considered
I think it would be better to review the conventional "pick up" processing and redirect it to "insert" processing, but I gave up because the "pick up" processing is very complicated.
Please let me know if there is a better way
Testing
Pick up items from adjacent tiles
1000 salts (5 L)
Before: 30:00
After: 00:54
100 apples (23 L)
Before: 3:11
After: 3:11
Additional context