Dynatrade - Dynamic Economy

DynaTrade v0.8.7 Spigot/Paper 1.21.4 · Vault + economy plugin Technical Preview​ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ TL;DR DynaTrade can now optionally trigger market cycles from real confirmed trade volume, instead of reacting only on the normal scheduled timer. Added 7 player-facing market states directly to the market GUI: Stable, Rising, Falling, High Activity, Thin Market, Volatile, and Insufficient Data. Market states include short explanations so players can understand why an item is being classified that way. Volume cycles include cooldown, coalescing and recovery handling so multiple triggers cannot create duplicate or empty market generations. Existing configurations remain compatible — the new volume trigger is disabled by default and requires no migration. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ How to Update Stop your server Replace the jar Start your server No extra migration is required. Existing servers continue using scheduled market cycles exactly as before unless the new volume trigger is explicitly enabled. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Known Limitations (Technical Preview) Volume-triggered cycles are global market cycles — they do not process individual items independently. Market states describe recent market behavior only. They are not predictions and do not affect pricing. Some display states depend on recent in-memory market history and may temporarily show a more conservative state after restart until new cycles rebuild enough history. Network-wide market synchronization, Redis/SQL backends and shared market authority are not included in this release. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ .SpoilerTarget">Spoiler: Full technical details Responsive Volume Cycles DynaTrade now supports an optional second way to start a market cycle. Previously, normal automatic cycles were primarily triggered by the configured TIME interval. 0.8.7 adds: VOLUME — start the same global pricing cycle once enough confirmed market activity has accumulated. New configuration: Code (YAML): pricing: volume-trigger: enabled : false global-threshold : 500 min-interval-ticks : 1200 Disabled by default — existing servers keep the previous behavior unless this feature is enabled. Global threshold — BUY and SELL quantity both contribute toward activity. Confirmed trades only — quotes, rejected trades, failed journal writes and unsuccessful operations do not contribute. Same pricing pipeline — VOLUME does not introduce a second pricing engine. It triggers the existing market cycle pipeline. Minimum interval — prevents extremely active markets from repeatedly cycling without a cooldown. Reload-aware — changing the volume-trigger configuration through reload updates the policy used by future cycles. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Market States The market GUI can now translate DynaTrade's existing trend, volatility, activity and participation signals into a simple player-facing state. The seven states are: Insufficient Data — there is not enough recent information to classify the market reliably. Thin Market — recent prices are based on limited market participation. Volatile — recent price behavior has been unstable. High Activity — current trading activity is above the item's normal level. Rising — recent prices have moved upward consistently. Falling — recent prices have moved downward consistently. Stable — recent prices are broadly balanced. The classifier uses a deterministic priority when multiple conditions exist: Code (Text): Insufficient Data → Thin Market → Volatile → High Activity → Rising / Falling → Stable Important: these states are completely observational. They do not modify prices, spread, calibration, VREF, momentum, risk scoring, trade admission or cycle scheduling. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Market State Reasons Item details now show not only the state but also a short explanation. Examples include: Insufficient History — recent history is limited. Thin Participation — recent prices reflect limited participation. High Volatility — recent price behavior has been unstable. High Activity — recent activity is above normal. Bullish Trend — recent prices have risen consistently. Bearish Trend — recent prices have fallen consistently. Balanced Market — recent prices have been broadly balanced. The market list shows the compact state, while the item detail view includes the explanation. English and Portuguese translations were added for the complete feature. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ High Activity Detection High market activity is now exposed separately from volatility classification. Previously, a high-volume condition could be represented only as part of broader risk/volatility information. 0.8.7 keeps the existing risk model intact while exposing a dedicated read-only activity signal for the GUI. This allows an item to be shown as: High Activity without requiring it to also be classified as volatile. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Volume Trigger Safety The new automatic trigger includes several protections for busy markets. Busy-cycle coalescing — if the market is already processing a cycle, repeated volume triggers collapse into one pending request. Revalidation — once the active cycle finishes, DynaTrade checks the live buffer again before starting another VOLUME cycle. If another cycle already consumed the qualifying activity, the stale request is dropped. TIME + VOLUME serialization — scheduled and responsive cycles share the same cycle state and cannot run concurrently. MANUAL compatibility — manual cycles continue using the existing administrative behavior. Cooldown after successful cycles — rejected or failed cycle attempts do not incorrectly consume the automatic-cycle interval. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Transaction Buffer Improvements The transaction buffer now maintains an O(1) active-volume counter. This means the plugin does not need to rebuild or scan the full pending transaction map after every trade just to decide whether the volume threshold was reached. The counter: Counts BUY + SELL quantity Resets with buffer rotation Restores correctly after failed cycle persistence Rejects numeric overflow before mutating the buffer Preserves exact volume across concurrent record/drain operations ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Recovery & Exactly-Once Hardening Several edge cases were found while certifying the responsive cycle path and were fixed in this release. Fixed: restoring the same drained snapshot more than once could duplicate recovered market activity. Fixed: repeated persistence callbacks could attempt to apply the same market cycle again. Fixed: stale pending volume requests could remain marked after they were no longer eligible. Fixed: the runtime could return to IDLE before cycle cleanup had actually completed. Fixed: a repeated durable trade callback could publish/count the same confirmed volume more than once. Changed: cleanup now remains part o