Lightman's Currency:Claim Economy

[4.2.0]

Added

• Player-to-player chunk marketplace (FTB Chunks only). MarketService and its command frontend, /lc_claim_economy market sell|cancel|buy|browse:
  • All commands are position-based - sell <price_copper> lists whatever chunk you're currently standing in, cancel delists it, buy purchases the listing on the chunk you're standing in, browse prints all active listings (position, dimension, price, seller) sorted cheapest first.
  • Ownership transfer is sequenced safely: the seller's chunk is unclaimed and the buyer's claim is confirmed successful before any money moves, with an automatic rollback (reclaiming for the seller) if the buyer-side claim fails, so a failed transfer never charges the buyer or strands the chunk unclaimed.
  • Transfers run through a new ClaimBatchContext.runAsInternalTransfer suppression so ChunkClaimHandler doesn't also charge the buyer the normal claim price or pay the seller an unclaim refund on top of the agreed sale price.
  • Scope note: the buyer receives a freshly-claimed chunk with default protection/force-load state - land/build classification and per-player chunk permissions are not carried over from the seller.
• Transaction ledger and economy statistics, tracking upkeep charges, claim purchases, unclaim refunds, the pioneer bonus, and market sales/ purchases:
  • Every player/team account now keeps a capped (50-entry), newest-first history (LcClaimEconomySavedData.LedgerEntry), viewable in-game via a new History button on the Bank Dashboard, opening TransactionHistoryScreen - a scrollable, ftblibrary-free list showing each entry's description, timestamp, and signed amount.
  • Server-wide aggregate counters (total upkeep charged/missed, claim spend, unclaim refunds, market volume) are now shown on the web dashboard under a new Economy Activity panel - answers "is offline upkeep actually being charged, how often, and how much" at a glance, without exposing any individual account's history over the unauthenticated web server.
  • Wired into both backends: ChunkClaimHandler/ClaimBatchContext (FTB single and bulk claims/unclaims), OpcClaimEconomyListener (OP&C claims/ unclaims), and UpkeepSettlementService/OpcUpkeepService (periodic upkeep, on both a successful charge and a missed/frozen payment).

Fixed

• Free-allowance chunks paid out an unclaim refund they were never charged for, on both backends:
  • OP&C (OpcClaimEconomyListener.handleUnclaim) refunded on every unclaim unconditionally - it never checked the free-chunk allowance at all, unlike the claim side right above it which does. A chunk claimed for free within freeChunks still paid out a refund when unclaimed, manufacturing money from nothing.
  • FTB Chunks (ChunkClaimHandler) had a subtler version of the same bug: ChunkTeamData.getClaimedChunks() caches its result, and FTB Chunks' own unclaim() only invalidates that cache after firing the AFTER_UNCLAIM event this mod listens on - confirmed by decompiling the installed FTB Chunks jar. Reading the team's claimed-chunk count from inside that listener could return a stale, pre-removal count, tipping the free-allowance comparison the wrong way. Fixed by counting from the claim manager's own live (uncached) chunk collection instead of the per-team cached one.