I ran into the issue again (on a complete different server), did some testing and found more info that might help you to reproduce this.
I used both a primitive bin and a primitive dump that NEVER had their waste pickup configured.
First step:
Pickup bounty tab -> i did NOT set the default price per item, left it at 0, did not even touch the dropdown.
I added something it had in its storage to "priced items" and set a price of 0.1.
The UI will diplay the "at least one priced item or a non-zero default price must be set" error message on top, which honestly seems more like a warning than an actual active error.
At this moment, the container is correctly configured, but it's not possible to pick up garbage from it.
The error message it displays is incorrect.
Second step:
The next step seems to force an update on the container.
Set a default price per item (i used 1).
It is now possible to pick up garbage from the container, with all items set in "priced items" to used their own override value (which works as intended).
Final step:
The final step is to set the default price per item back to 0. The container will now only allow configured items to be picked up.
My guess is that you tried to reproduce this with a container that had already been used or that you touched the "default price per item" dropdown.
Expected behavior would be for the container to update itself after adding an item to "priced items" and not need the manual update by changing the default price per item 0 -> 1 -> 0.
I ran into the issue again (on a complete different server), did some testing and found more info that might help you to reproduce this.
I used both a primitive bin and a primitive dump that NEVER had their waste pickup configured.
First step:
Pickup bounty tab -> i did NOT set the default price per item, left it at 0, did not even touch the dropdown.
I added something it had in its storage to "priced items" and set a price of 0.1.
The UI will diplay the "at least one priced item or a non-zero default price must be set" error message on top, which honestly seems more like a warning than an actual active error.
At this moment, the container is correctly configured, but it's not possible to pick up garbage from it.
The error message it displays is incorrect.
Second step:
The next step seems to force an update on the container.
Set a default price per item (i used 1).
It is now possible to pick up garbage from the container, with all items set in "priced items" to used their own override value (which works as intended).
Final step:
The final step is to set the default price per item back to 0. The container will now only allow configured items to be picked up.
My guess is that you tried to reproduce this with a container that had already been used or that you touched the "default price per item" dropdown.
Expected behavior would be for the container to update itself after adding an item to "priced items" and not need the manual update by changing the default price per item 0 -> 1 -> 0.