WorldListTrashCan

7.5.4 Restore the statistical standards for the quantity of old versions to be cleaned up. %DealItemSum% is the count of successfully processed entities. For example, three groups of 64 cobblestones each on the ground would display "3" instead of "192.". 2. Rectify the statistics on the source quantity of public trash bins. %GlobalTrashAddSum% Statistics on the number of entities dropped by source into the public bucket. Even if the same dropped item is added in batches, it is only counted once.. 3. Add two new precise quantity variables.

• %DealItemAmount%: the actual number of items processed, with the aforementioned cobblestone counted as 192.
• %GlobalTrashAddAmount%: The actual number of items added to the public trash can.

1. Standardize the default prompt specifications for manual and scheduled cleaning. The default recycling quantity for /wtc clear has been changed to %DealItemSum%, aligning with scheduled cleanup; the {routed} in existing custom messages still represents the actual number of items routed.
2. Maintain internal precise quantity statistics. Only the notification variables are adjusted according to the specifications, while the trash bin storage, personal bin notifications, Audit, console items, and anti-copying processing still use the actual counts.
3. Synchronous Configuration Instructions and Multilingual Copywriting. Update the statistical variable comments in cleanup.yml, synchronize the manual cleanup prompts for Simplified Chinese, Traditional Chinese, English, and Spanish, and add variable explanations to the README in Chinese and English. 7.5.5 Fixed the issue where the hopper comparator signal does not update after enabling item stacking. Remove the implementation of "manually writing inventory after intercepting and absorbing events" from the normal path, and instead have the server-side native funnel handle absorption, while retaining comparator updates and native absorption cooldown.
4. Correctly protect the remaining stock of items exceeding the original set. For example, with a logical quantity of 256, first protect 192, then pass the 64 valid units to the funnel for processing, and settle based on the actual amount absorbed.
5. Properly handle the capacity of the funnel section. When the funnel can only absorb 10 at a time, the ground will ultimately have 246 remaining, without deducting the entire group incorrectly.
6. Compatible with other plugins to cancel absorption. Even if other listeners cancel the event at a later stage, the original quantity will be restored, ensuring no loss or duplication of items due to temporary splitting.
7. Optimize the full funnel processing. Maintain ground items directly when inventory is full to avoid ineffective absorption and repeated generation of temporary surplus entities.
8. Strengthen competition protection during the absorption period. Temporarily prevent the same item from being merged, picked up, naturally disappearing, or submitted via sweeping. The protection will be lifted after the duration.
9. Improve the thread handling of Folia. Finalize by using physical scheduling and verify regional affiliation; when the source and remaining quantities belong to different regions, do not forcibly merge across regions and retain the correct quantities.