How kris-dreemurr-dev/mosssafes works
MossSafes is a Spigot/Paper plugin for password-protected chest safes. Players create safes with a command and chat input, then authenticate by interacting and entering a password; successful access authorizes them, while incorrect passwords trigger an electric shock. The README also documents double-chest expansion and persistence of safe details. Source excerpts do not include runtime classes, so implementation-level connections are shown as unverified rather than asserted.
Main entry points: MossSafes.java Plugin Entrypoint · InteractListener.java Interaction Events · SafeManager.java Safe Manager · SafeCommand.java Safe Command
Components 9
Plugin Runtime
- Plugin Entrypoint
src/main/java/org/example/mosscrafts/mossSafes/MossSafes.java - Plugin Manifest
src/main/resources/plugin.yml
Safe Lifecycle
- Safe Command
src/main/java/org/example/mosscrafts/mossSafes/commands/SafeCommand.java - Block Events
src/main/java/org/example/mosscrafts/mossSafes/listeners/BlockListener.java - Safe Manager
src/main/java/org/example/mosscrafts/mossSafes/managers/SafeManager.java
Access Control
- Interaction Events
src/main/java/org/example/mosscrafts/mossSafes/listeners/InteractListener.java
Safe Storage
- Safe Records
src/main/resources/safes.yml
Other components
- Player
- Minecraft Server
Connections 13
- Player → Safe Command: creates safe
README.md - Player → Interaction Events: requests access
README.md - Player → Interaction Events: enters password
README.md - Interaction Events → Player: grants or shocks
README.md - Block Events → Safe Manager: expands safe
- Safe Command → Safe Manager: registers safe
- Interaction Events → Safe Manager: checks authorization
- Safe Manager → Safe Records: persists records
- Minecraft Server → Plugin Entrypoint: loads plugin
- Plugin Entrypoint → Safe Command: registers command
- Plugin Entrypoint → Block Events: registers listener
- Plugin Entrypoint → Interaction Events: registers listener
- Plugin Manifest → Plugin Entrypoint: declares plugin