Kzeroko KTM2

Party Payment Integration

The IsekaiTweaks bridge between Expansion payments and Open Parties and Claims savings.

Updated Oct 28, 2026 2 min read

Expansion services call IsekaiCore’s Numismatic payment facade. IsekaiTweaks supplies the optional party-savings bridge; Party payments describes the player rules. This page records an external integration, not a new Expansion API.

What it does

In IsekaiTweaks, NumismaticCompatMixin wraps Core’s NumismaticCompat.canAfford and tryPay. ITMixinPlugin enables it only with IsekaiCore, Numismatic Overhaul and Open Parties and Claims present. Core source is unchanged, and getTotal continues to mean personal inventory currency plus wallet balance.

Expansion’s TradeTransaction, BlacksmithService and StructureSpaceService use these payment entry points. LodgingDialogue also uses canAfford when displaying room offers, so its preview follows the same payment policy. The bridge does not patch Numismatic wallet balances or all third-party currency operations.

Runtime model

Tweaks’ internal integration service PartyPayments resolves the payer’s current party. PartyPaymentPlan calculates the personal portion and shortfall by subtraction, avoiding a combined-balance overflow. The existing scoreboard component stores party assets; no new persistent field or migration is introduced.

The original Core payment method debits the personal portion, using inventory coins before wallet funds. Only after success does the bridge debit and synchronise party assets. PartyMessageUpdater sends a translated spender, debit and remaining-balance message to other online party members. Ordinary party chat still includes its sender.

Contracts

Run the bridge on the server thread. Personal funds that cover a payment use the original method directly. Insufficient combined funds fail before mutation; a rejected personal debit leaves savings untouched. The debit uses the payer’s current party without requiring party ownership.

OpacCompat.Server.donateAssets first requires personal funds for the entire donation. Personal balance reads stay personal, so donations cannot recycle savings. Other access, quote, delivery and ownership checks belong to the calling Expansion service.

These details were checked against the IsekaiTweaks working tree with IsekaiCore 0.4.0-build69 and Numismatic Overhaul 0.2.18+1.20-fabric. The external anchors record their owning sources.

Extending it

Expansion code should continue using Core’s NumismaticCompat.canAfford and tryPay. Do not duplicate party lookup or treasury mutation in a merchant, commission or room service. A personal balance display is not a combined-funds affordability check.

Verifying

Compile both repositories with ./gradlew.bat compileJava. In a running pack, check personal-first allocation, mixed funds, treasury-only payment, insufficient funds, overflow and a rejected personal debit.

In a running pack, test these cases with a party owner and an ordinary member. Check that successful treasury spending notifies each other online member once, never the payer, an offline member or an unrelated party. Reopen the party UI and restart the server to check the remaining balance. Reject an underfunded donation even when savings could cover it; a fully personal donation must still succeed. Repeat without a party to check the original payment path.

See Trading API, Structure spaces and Party payments.