Player Containers

not a major update by any means, but adds lol_us, en_ud, en_pt, and enws support (thanks MeeperCreep!)

Somehow I completely missed the basic and loose player containers completely not working from 0.2.3 onwards??? Anyway, that's fixed now.

another quick bc25 fix - this time it's making sure data is stored internally in a thread-safe way (plus hopefully fixing a related issue around spectator mode collisions)

quick bc25 fix to hopefully make the mod work with anshar

More BC25 fixes:

• Emergency fix to make sure that it doesn't try to do stuff with containers that don't exist
• Adventure mode behaviour fix that I had done before the emergency fix anyway

Some bug fixes and tweaks for BlanketCon:

• Fixed crash on attempting to stop spectating a container's owner
• Fixed various issues around breaking cages
• Somewhat fixed contained spectators being jittery near the edge of their allowed range
• Added more failsafes to disallowing changing dimensions with a container
• Made the playercontainer:restrict area always work regardless of gamerule

this version is still for BlanketCon '25, it just has some tweaks:

• contained players (which previously had collisions with all blocks as in any other gamemode) now can pass through blocks that are non-opaque or that have blockentity-based rendering
• item rarities fixed (singularity container -> epic, self container -> rare)
• contained players now properly collide with the container radius (as opposed to before where they were teleported back every tick)
• command outputs tweaked slightly (release now outputs whether the release was successful or not, op-exclusive commands now log their outputs)

This is the BlanketCon '25 showcase version! The main additions are cages, loose players and self containers. Note that:

• players being contained while offline is disabled because it's still a bit buggy
• there is a new gamerule (playercontainer:restrictToBooth) - when enabled, you can only capture players in the arealib area named playercontainer:booth
• (similarly, players are force-released if their container enters an area named playerconatiner:restrict)

This is a simple proof-of-concept version released because Chromonym will be unable to work on the mod for a few weeks after its uploading.