Dan's Spawn System

Dan's Spawn System 2.1.0 For a server running v2.0.0, this is a drop-in upgrade. /resetspawn now also works when typed as /dansspawnsystem:resetspawn, and the plugin has been checked against Minecraft 26.3. Usage reporting changes in two ways when it is on. It creates a random server ID and stores it in plugins/trace/config.yml. It also sends that ID and the plugin version with every event. The ID does not identify any person, account or IP address. No player data is sent. Your existing settings and data files are unchanged, and turning reporting off works exactly as before. Changes Commands · /resetspawn now works the same way when typed in its namespaced form /dansspawnsystem:resetspawn. Before, that form was not handled (#93). Compatibility · Checked against Minecraft 26.3, alongside 1.19.4, 1.21.11 and 26.2 (#101). Usage reporting · Every event now includes a random server ID, so servers can be counted instead of raw events. The ID is created once and saved as the server-id line in plugins/trace/config.yml, and all plugins on the server that use this reporting share it. Delete the line to get a new ID. No ID is created or saved while reporting is off (#99). · Every event, including command events, now carries the plugin version (#96). · plugins/trace/config.yml accepts an optional tags: block, and those tags are added to every event from the server. For example, set ci: "true" on a test server so its events are left out of real-server figures (#95). · The startup message and the comments in config.yml now mention the server ID (#100). Download: https://github.com/Dans-Plugins/Dan...s/download/v2.1.0/D… Full release notes: https://github.com/Dans-Plugins/Dans-Spawn-System/release…

Dan's Spawn System 2.0.0 A server on 1.2.0 upgrading to this release gets a set of long-standing bug fixes to spawn selection, sign detection and /resetspawn, and a new opt-out usage-reporting feature that is enabled by default. The permission nodes declared in plugin.yml have been renamed to the spawnsystem.* names the plugin actually checks, so any grants written against the old dansplugins.* names need updating. The plugin now ships a config.yml, which is created on first start and gains a usage-reporting block on upgraded installations. Changes Spawn selection and signs · A player's chosen spawn is now kept once set; previously every click on a [Spawn] sign silently overwrote it. Use /resetspawn to pick a new one. (#63) · Spawn signs are only activated by right-clicking; left-clicking or stepping on a pressure plate next to one no longer sets a spawn. (#80) · A [Spawn] sign whose coordinates cannot be read now tells the player to see an admin and logs a warning through the plugin logger with the sign's location, instead of failing silently. (#80) · All sign types added after 1.15 (crimson, warped, mangrove, bamboo, cherry, hanging signs) are now recognised as spawn signs. (#74) · Saved spawns with a 0 on any axis are no longer discarded on load; only missing or unreadable values are skipped. (#74) Commands · /resetspawn now tells the console it is player-only, reports when a named player cannot be found instead of claiming success, and only notifies the target if they are online. (#73) Permissions · Declared permission nodes are now spawnsystem.reset.self, spawnsystem.reset.others, spawnsystem.placeSpawnSign, spawnsystem.breakSpawnSign and the new spawnsystem.admin (all default to op), matching the nodes the plugin checks. The dansplugins.* nodes are no longer declared. (#62) Usage reporting · The plugin now sends a small usage event on startup (plugin name and version) and on each command (command name) to https://trace.danielstephenson.dev. Nothing about players or the server is included; sending happens off the main thread and is dropped if the server cannot be reached. (#81) · A startup log line states whether reporting is on and, if off, why. Reporting can be turned off per plugin with usage-reporting.enabled: false in config.yml, server-wide with enabled: false in plugins/trace/config.yml, or via the TRACE_USAGE_REPORTING=off / DO_NOT_TRACK=1 environment variables. (#81, #86) · On upgraded servers the usage-reporting block is written into config.yml so the switch is visible on disk; an existing block is left untouched. (#86) Upgrade notes · If your permissions plugin grants any dansplugins.spawnsystem., dansplugins.placeSpawnSign or dansplugins.breakSpawnSign nodes, change them to the spawnsystem. names above. · Usage reporting is on by default. To opt out before the first report is sent, set usage-reporting.enabled: false in plugins/DansSpawnSystem/config.yml, or create plugins/trace/config.yml containing enabled: false, before starting the server with the new jar. · Players who relied on re-clicking a sign to change their spawn now need to run /resetspawn first. Download: https://github.com/Dans-Plugins/Dan...s/download/v2.0.0/D… Full release notes: https://github.com/Dans-Plugins/Dans-Spawn-System/release…

What's Changed · Moved away from the Singleton pattern. by @dmccoystephenson in #58 Full Changelog: v1.1...1.2.0

Changes in Dan's Spawn System v1.1 · Refactored the structure of the plugin to be more consistent with my other plugins. · Implemented the Singleton pattern instead of passing references everywhere. · Integrated the plugin with bStats. · Refactored the plugin to use an EventRegistry class. · Abstracted out the Reset Spawn command into its own command class. · Put all of the permissions of the plugin in the plugin.yml file and designated which ones should be default. · Abstracted out the functionality of the Utility Subsystem into other classes. · If a player has a bed spawn, they will no longer get teleported to their custom spawn upon death. · Made sure that the plugin worked on 1.17.