dOPa's Random Utilities

IMPORTANT: I still recommend waiting for version 1.0.0

Added:

• Added the Just Dire Things name in the credits and mentioned that it has an MIT License (I forgot!)
• Implemented an advancement when successfully unpacking a block with a cardboard box, to indicate that it is one-time use only
• Implemented a config option for the cursed lasso to prevent bosses pickup and spawner rewrites (default = true)

Changed:

• /dopa reset_ui command it's no longer permission gated (security)
• Made the cursed lasso deny messages red

Fixed:

• Cleaned up some dead code (never used)
• Both /dev/null/ not rendering the item inside them
• Transfer nodes extract from inventories with no claim check (claim bypass)
• Cursed lasso can turn a spawner into a boss spawner (grief / lag)
• Lasso capture/deploy ignores claims, owners, and tamed pets (grief)
• Item collector / magnet can take other players' drops (SMP theft / grief)
• Cardboard unwrap is weaker than wrap (not a pack blacklist, grief, claim bypass)
• Cardboard box can relocate vanilla-immovable / high-value blocks (SMP economy / griefing)
• 256 maximum transfer pipe was never applied (performance)
• FTB Chunks integration fails open (security)
• FTB present: vanilla spawn protection skipped; API fail-closed (compat)
• Generator / lasso JSON uses throwing Identifier.parse (robustness)
• Ghost filter packets only strip CUSTOM_DATA (packets)
• Access transformer makes Slot x/y and screen origin fields writable (compat / crash)
• The One Probe owner tooltip loads client Minecraft on dedicated servers (crash)
• Creative resource generators are survival-mineable and drop themselves (admin blocks / no drops)
• Ghost sanitizer leaves mod components and large vanilla components (save bloat / identity matching)
• Common block entities reference client-only WorkingVolumeOverlay (sidedness smell)
• Malformed items/lasso.json can throw NullPointerException on reload (robustness)
• Advanced breaker drop-filter simulates Block.getDrops while scanning (performance)
• Config integers have no upper bound (robustness / disk is trusted)
• Magnet tick: full inventory scan + optional particle spam (performance)