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. 4. 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. 5. 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. 6. 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. 2. 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. 3. 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. 4. 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. 5. Optimize the full funnel processing. Maintain ground items directly when inventory is full to avoid ineffective absorption and repeated generation of temporary surplus entities. 6. 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. 7. 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.

WorldListTrashCan 7.5.1 → 7.5.3 Update Report Current version: 7.5.3 A total of 19 submissions were completed during this period. 【New Feature】 1. Added the logic for stacking ground items on the modern server side, with the default setting disabled. 2. Automatically determine whether the environment is supported based on API capabilities such as PDC. 3. Support independent settings for each item: - Whether to participate in stacking - Maximum stack quantity - Custom Display Name 4. Built-in Chinese, English, and Japanese product names. 5. Stack configuration is uniformly integrated into item-stacking.yml. 6. Personal Trash Bin Recycling Reminder: Supports clicking to open either the personal bin or the public bin. 7. Add an independent switch for "Intercept Generation Logs" to increase the entity quantity limit. 8. Add a unified debug switch; when disabled, it will no longer output non-essential debug information. ```Performance Optimization``` The default upper limit for Folia single-round block processing is increased to 2048, reducing the number of scheduling rounds for large-scale map sweeping tasks. 2. When item stacking is disabled, corresponding listeners, tasks, queues, and indexes are not registered. 3. Localized item names are loaded only for the currently selected language to reduce constant memory usage. 4. Debug logs employ lazy construction, avoiding unnecessary string overhead when debugging is disabled. ```[Issue Fix]``` 1. Fixed the issue where the menu must be reopened to refresh after placing items into an already opened trash can. 2. Fixed the issue where the trash can only collects some items during sweeping, and the remaining quantity does not continue routing. 3. Fix the issue where the personal trash bin prompt displays the original Material name. 4. Fix the logic for non-player entities like Piglin to pick up and stack items: - Logical quantity is not deducted - Ground quantity briefly fluctuates - Rewards can be exchanged repeatedly 5. Fixed the issue where the item quantity restoration was incorrect when the player's pickup results were delayed to the next tick. 6. Fixed the issue where players might receive the same item in both their backpack and the trash can when picking up and sweeping simultaneously. 7. If the source item becomes invalid, the quantity changes, or the deletion fails after sweeping and writing to the trash bin, the write operation will automatically roll back to avoid item duplication. Version changes: 7.5.1 → 7.5.2 → 7.5.3

7.2.0 Unify the containers, pages, layouts, sorting, and retrieval and placement logic of public and personal trash bins. - Personal trash cans support a more comprehensive menu configuration, encompassing display mode, layout, capacity, and removal strategy. - New compact display mode: - Display the actual stacking quantity of items; - The display lines of the original item's Lore can be limited; - Display ellipsis prompt for content exceeding the limit; - Support for customizing the instructions for retrieval operations. 7.3.0 - Added a conservative configuration updater. - Automatically generate a backup with a timestamp before updating the configuration. - Only migrate old configuration nodes that can be accurately identified. - Try to retain the original annotations, colors, PAPI text, and user configurations. - Continue to use the original configuration when the configuration update fails, to avoid disrupting existing settings. 7.4.0 - Added entity cleanup rules that match based on "entity type + custom name". - Supports named-whitelist and named-blacklist. - Supports wildcard, color name matching, and inclusion matching. - The whitelist takes precedence over the blacklist. - It can distinguish between normal entities, MythicMobs monsters, and Bosses within the same Bukkit entity type. - Enhanced /wtc look, allowing you to view entity custom names, decolored names, and formats that can be directly used for configuration. 7.4.0: Added entity cleanup whitelist/blacklist matching by entity type and custom name, supporting wildcards. 7.4.1: Improve configuration examples, configuration notes, and security configuration migration mechanisms. 7.4.2: Fixed the issue where the opened menu would not refresh immediately after a player manually placed items in the trash can. 7.5.0: The personal trash can recycling prompt supports clicking to open the trash can. 7.5.1： The recycling prompt has been enhanced with two separate buttons for "personal trash can" and "public trash can". Fix the menu refresh issue after restoring the old layout and manually placing items. Add a detailed log switch when the entity quantity limit is triggered. A new optional feature for logical stacking of ground-dropped items has been added, which is disabled by default. Determine whether stacking is supported based on the actual API capabilities, without relying on server names or hard-coded versions. Add mappings for item names between Chinese, English, and Japanese. Support for configuring the stack limit for each item, with a default limit of 1024. Optimize the batch processing performance of Folia cleanup. Fixed the issue where some items were not fully processed during the sorting of items for repair and cleaning. Fix the language mapping issue in the notification for personal trash can. Unify and integrate stacking-related configurations into item-stacking.yml, and add detailed comments.

WorldListTrashCan - Refactored Version Changelog I. Public Trash Can 1. New compact compact display mode - Only one icon is shown for identical items. - Cumulative quantity is displayed in item Lore. - Maximum display lines of original Lore can be limited. - Ellipsis hint will show automatically when exceeding line limit. - Each item type accumulates up to 9999 by default. - Set to -1 for unlimited quantity per item type. - Left‑click takes out 1 item by default. - Shift + Left‑click takes out 64 items by default. - Take‑out amounts are configurable in config file. 2. Preserve stacked original stacking mode - Keep vanilla 64/16/1 item stacking behaviour. - compact and stacked use independent configuration nodes. - Capacity and sorting settings of two modes do not interfere with each other. 3. Refactored public trash can storage - GUI is no longer the real storage container for public trash can. - Real storage and menu rendering are fully separated. - Reduces extra overhead caused by menu refresh, page turning and item merging. - When shrinking capacity, existing items go to read‑only overflow page. - Overflow items remain viewable and retrievable, will NOT be silently deleted. 4. New per‑player independent sorting Each player may independently select sorting method below: - Insertion order - Quantity ascending - Quantity descending - Name sorting - Material sorting Sorting preference only persists during current player online session, will NOT be written to database. compact and stacked modes store their own separate sorting preferences. 5. Optimized menu refresh logic - Sorting executes only on menu open or manual sort switch by player. - Page turning and item taking use lightweight snapshot generated at menu opening. - Sweep‑in items will not trigger unexpected re‑sort for currently viewing page. - Different players can use different sorting modes simultaneously. 6. Extended layout buttons - New type: close close button. - New [close] action for actions node. - Layout display items support glow: true enchant glow effect. - Glow effect applies to page buttons, background, sort buttons, action buttons and close button. - 1.20.5+ uses native pure glow effect. - Older versions automatically fallback to hidden‑enchant implementation. 7. Fixed model‑id handling - Minecraft 1.14+ reads and applies CustomModelData correctly. - Minecraft 1.12.2 and 1.13 skip reading and parsing this field entirely. - Fixed issue where configured model‑id button does not take effect on modern Paper builds. - CustomModelData detection & cache runs only once at plugin startup, no repeated reflection in GUI hot path. II. Item Recognition & Sweep Routing 1. New /wtc look inspection command Shows information of item held in hand: - Material - Item display name - Lore - PDC keys - Raw NBT / Data Components keys Helps server owners write accurate item match configurations. 2. New custom‑data‑based item routing Items can be matched by: - Material - Display name - Lore - PDC keys - Raw NBT / Data Components keys Match rules support * wildcard and are case‑insensitive. 3. Available handling options for matched custom items - personal‑only: send item to personal trash can only - keep‑ground: leave item on world ground - direct‑remove: delete item directly 4. New public trash can entry whitelist Public trash can restricts incoming items by: - Material - Display name - Lore - PDC keys - Raw NBT / Data Components keys Whitelist applies to: - World sweep collection - Manual player item deposit - Third‑party plugin API calls to public trash can Swept items rejected by public trash can are configurable to: - Remain on ground - Be deleted directly 5. Optimized wildcard matching performance - Wildcard rules are pre‑compiled on config load. - Identical rules will not be re‑parsed in sweep hot path. - Extra PDC / Raw NBT checks are skipped when custom‑data routing is disabled. III. World Filter for Item Sweep 1. New include / exclude world filter Example: world-filter: include: - "*" exclude: - "*dungeon*" 2. World name supports * wildcard - Case‑insensitive. - exclude takes higher priority than include. - All worlds are allowed by default. - Worlds whose name contains "dungeon" are protected by default. 3. World filter applies to: - Scheduled world sweep - /wtc clear true - /wtc clear false /wtc clear true only skips player‑count & entity‑count guards, it does NOT bypass world filter. IV. Audit Add‑on Support 1. Precise item tracking keys added - Each real storage entry inside public trash can gets its own independent tracking key. - Homologous items in personal trash cans can also be precisely tracked. - Sorting, page turning and display mode switching will not break tracking relation. 2. WorldListTrashCanAudit provides further information: - Which trash can the item finally entered. - Who took items out from public trash can. - Whether personal‑trash‑can items have been retrieved. - Owner, world and coordinates for world‑bound trash cans. - Whether item was directly deleted. 3. Behaviour when Audit add‑on is not installed - No extra database thread will be created. - Unnecessary personal‑trash‑can identity hash calculation is skipped. - Main plugin functions work normally without side‑effects. V. Bug Fixes 1. Fixed repeated skip hint message when sweep guards conditions are not satisfied. 2. Fixed issue: after modifying personal‑trash.gui.title and running /wtc reload, already‑created personal trash cans still show old title. - New title takes effect on next menu open. - Existing items inside personal trash cans are preserved. 3. Fixed invalid public‑trash‑can model‑id on modern Paper versions. 4. Corrected low‑version compatibility boundary for model‑id. - 1.12.2 and 1.13 ignore irrelevant configuration field. - CustomModelData is only enabled starting from 1.14+. 5. Supplemented Chinese comments and function descriptions inside configuration files for different Minecraft versions. VII. Update Summary This major update refactors public trash can from fixed‑chest implementation to dedicated independent storage system. New features include dual display modes, per‑player independent sorting, stable pagination, capacity overflow protection, customizable layout buttons, cross‑version glow effect and full CustomModelData support. The sweep system is enhanced with world filtering, custom‑data item recognition, fine‑grained item routing and public‑trash‑can entry whitelist control. Besides, audit tracking capability is implemented. Multiple bugs are resolved: personal trash can title reload issue, repeated sweep‑guard hint spam, broken model‑id on modern Paper and other compatibility problems.

WorldListTrashCan is a cleanup and trash-can plugin for Bukkit, Spigot, Paper, and Folia/Luminol. It keeps the legacy world trash can, public trash can, personal trash can, item blacklist, entity cleanup, dense entity cleanup, drop protection, and cleanup notifications. The refactored version also addresses the legacy configuration sprawl, Folia lag, forced chunk loading, accidental item loss, and inconsistent cross-version behavior. ### Changes administrators will notice #### New user-facing features | Feature | Legacy version | Refactored version | | --- | --- | --- | | Public trash-can layout | Fixed layout | Configurable 1-6 row content area, page buttons, background, and display items | | Public trash-can buttons | Fixed material and position | Material fallbacks, CustomModelData, name, Lore, and replacement items | | Smaller public trash-can capacity | Items could become inaccessible | A read-only overflow page keeps items visible and retrievable instead of silently losing them | | Public trash-can actions | Only fixed button behavior | Supports `[console]`, `[command]`, `[message]`, and PlaceholderAPI variables | | Personal trash-can notifications | Incomplete single-item and batch messages | Individual notifications for single items and grouped notifications for cleanup batches, showing up to 3 types by default | | Cleanup guards | Cleanup ran when its timer elapsed | Automatic cleanup can be skipped when online-player or entity-count thresholds are not met | | Manual cleanup | One fixed execution mode | `/wtc clear true/false` chooses whether cleanup guards are ignored | | Cleanup status | Mainly exposed through countdown variables | `/wtc stats` shows the latest recovery, deletion, entity, inventory, and remaining-time status | | Console details | Mostly showed totals | Shows the top 10 entity categories with display name, type, actual count, and remainder count | | Entity protection | Limited protection rules | Protects saddled entities and Bukkit `Tameable` owners while avoiding shooter/source/drop-owner false positives | | Direct deletion by world | No dedicated setting | Selected worlds can delete items directly without routing them to any trash can | | Moving-item protection | Not available | Cleanup can skip moving dropped items; disabled by default | | Filled shulker-box item protection | Not available | Cleanup can skip dropped item stacks containing filled shulker boxes; disabled by default | This table lists changes directly visible to server administrators and does not count internal implementation details as separate features. #### Compatibility and stability improvements - `WorldListTrashCan-universal.jar` runs across supported server versions, including Folia/Luminol; lightweight version-specific JARs are also available. - Compatible implementations are provided across the 1.12.2-1.21.x version line. RGB is supported on 1.16.5 and newer, with automatic downgrade on older versions. Legacy `&a` and `&c` color codes remain supported. - Folia/Luminol uses region-safe, segmented cleanup tasks instead of running ordinary Bukkit repeating tasks in a Folia environment. - Unloaded chunks are not force-loaded by default for world trash cans, preventing sudden cleanup lag spikes. - Player-drop ownership is stored on the dropped entity rather than inside the item stack, so normal item stacking is not affected. - Legacy configurations are detected and isolated in `old-version-config` instead of being used directly by the new implementation. - Missing default configuration entries are restored, and default configuration files include Chinese comments. - bStats is built in and has no plugin-level enable/disable switch; the plugin version is `7.0.0`. ### Estimated performance improvements The figures below are estimates based on old and new execution paths, default batch settings, and entity-count models. They are not a Spark benchmark guarantee. Actual results depend on loaded chunks, entity counts, player activity, and the server core. | Scenario | Estimated improvement | | --- | ---: | | Periodic dense-entity checks across 1,000 loaded chunks | About `96%` less checking pressure | | Periodic dense-entity checks across 4,096 loaded chunks | About `96.6%` less checking pressure | | 5,000 entities with 20 restricted entities generated per second | About `99.98%` less repeated traversal pressure | | Automatic cleanup with no players online | Skipped directly; near `100%` reduction for that cycle | | World trash can in an unloaded chunk | Plugin-initiated forced loading reduced by `100%`; defaults to skip and fallback routing | | Folia peak dispatch for a 4,096-chunk cycle | Theoretical instantaneous dispatch peak reduced by about `98.4%` | #### Overall estimate - Servers using only ordinary scheduled cleanup: typically about `0%-30%` improvement in the related path. - Large servers with dense-entity limits enabled: estimated related main-thread pressure reduction of `80%-99%`. - Servers previously affected by synchronous world-trash-can chunk loading: estimated single-cleanup lag-spike reduction of `90%+`. - The refactored version adds a bounded entity index and candidate queue; estimated additional memory usage is about `5-10MB`, with limits to prevent unbounded growth. These percentages describe estimated reduction for the specified scenario, not a fixed reduction for the entire plugin. For server-specific numbers, compare the legacy and refactored versions with Spark or server monitoring under the same map, player count, and entity count. ### Recommended configuration The new protections are disabled by default and do not change legacy behavior until enabled: ```yaml # cleanup.yml guards: # Skip automatic cleanup when online players are below this value. min-online-players: 1 # Skip automatic cleanup when the target entity count is below this value. min-total-entities: 150 # Disabled by default. When enabled, moving dropped items are skipped. moving-items: enabled: false minimum-speed: 0.01 # Disabled by default. When enabled, dropped item stacks containing filled # shulker boxes are skipped. filled-shulker-boxes: enabled: false ``` “Shulker-box items” means an `ItemStack` carried by a dropped-item entity, not a shulker-box block placed in the world. When enabled, dropped filled shulker boxes remain on the ground; empty shulker boxes are still cleaned normally. ### Common commands ```text /wtc help Show help /wtc reload Reload configuration /wtc stats Show the latest cleanup status /wtc clear true Run manual cleanup and ignore cleanup guards /wtc clear false Run manual cleanup while respecting cleanup guards ``` The formal long command is `/worldlisttrashcan`, with `/wtc` as its short alias. Permissions use the `WorldListTrashCan.*` namespace. ### Which JAR should I use? - For seamless switching between supported server types and versions, use `WorldListTrashCan-universal.jar`. - For a smaller package and fewer runtime branches, use the lightweight JAR matching the server version. - Put only one WorldListTrashCan JAR in a server's `plugins` directory. Do not install both the universal and lightweight JARs together.

1.When the plugin is overloaded, the public trash bin page that the player has already opened will be closed. 2.Now, when an entity is not a monster but a living being, it is considered an animal.

Optimized the logic of intensive entity cleaning function in servers under non paper branches. If you are not a beneficiary, there is no need to update

Fixed the logical fallacy of adding items first and then cleaning up items when cleaning up public trash cans on the "folioa" server

Fix bug where 'EveryClearGlobalTrash' still prompts to clean up the public trash bin when configured as -1

- "Blacklist and whitelist entity configuration" and "Support fuzzy matching" when cleaning entities - Fix the issue of mismatched cleaning quantities displayed after using the command "/wtc clear" on the "folia" server - Refactored some of the logic