SnDTC changelog

Changes

SnDTC is rebuilt from the ground up as a SnLib consumer. Config, language, text and colour, the command tree, tab completion, the scheduler, PlaceholderAPI, boss bars, holograms, cron and update checks are all SnLib's now, so the plugin's own code is only the parts that are actually about cores.

Cores are protected properly

Breaking a core used to be the only way its block was supposed to leave the world, but nothing ever checked. An explosion, a piston or a fluid removed it unnoticed: the core stayed active forever with a boss bar over open air, the removal dropped its material while the next regeneration painted a fresh one in, and any block put in the hole could be mined for core damage

• which bypassed block hardness, the entire difficulty model.

There are now twenty handlers covering explosions, pistons and their destinations, entity block changes, burning, fading, leaf decay, liquid flow, sponges, dispensers, buckets, placement (including the second half of a bed or door), and every way a block can grow, spread or form into a core's coordinate. Each one exits on the world first, so a server whose worlds hold no cores pays a single hash probe.

Schedules

• Interval schedules run on a fixed grid instead of counting from the moment the core died, so 4h means 00:00 / 04:00 / 08:00 whenever it was destroyed.
• Intervals of a day or more work. They previously re-anchored to today's midnight on every boot and receded a day per restart, so 1d12h - the plugin's own shipped example - never fired.
• Daylight saving is handled in local-clock terms, so a 4h core stays on 00:00 / 04:00 / 08:00 local all year rather than sliding an hour for half of it.

Rewards

• The damage board is snapshotted before the core is taken down, so the players who fought for it are the players who are paid.
• A core part-way through a fight is refilled on restart or reload, and the console says so. Leaving it damaged handed the whole top reward to whoever landed the next hit.
• Bedrock players are paid. A Java-username rule previously announced every Floodgate gamertag as "Unknown" and paid it nothing.
• rewards.max-paid bounds the payout burst a 200-player raid can schedule. Anyone skipped is named in the console, never silently dropped.

Configuration is honest about itself

A value SnDTC cannot read is named rather than silently replaced by a default. A quoted max-health: "5000" used to become the config default of 100, so the full top-three payout fired fifty times more often than configured, with nothing on any surface to say so. A single value written where a list belongs, a reward position that can never pay, a schedule that will never fire, a health pool that is not a number - each is reported by name, once, with what to do about it.

A core's active-block must now be a block players can break. BEDROCK is the shipped inactive default and passes every "is this a block" test, so putting it in the wrong key gave a core that could never be destroyed and never paid.

Display

• Boss bar, action bar and holograms are range-based and rendered per viewer, so PlaceholderAPI resolves against the player reading the text.
• Holograms are native TextDisplay entities through SnLib. No external hologram plugin.
• A malformed colour tag in an owner-edited template costs that one line and says which value to fix, instead of taking the plugin down with it.

Also

• New %sndtc_<core>_next%, _percent, _status and _damage placeholders, matched case-insensitively.
• Cores in WorldGuard-protected regions work with no setup and no dependency.
• /sndtc reports a change that could not be written to dtcs.yml instead of showing a success the owner will lose on restart.
• Obfuscated with SnObfuscator and structurally verified at build time.