Player-set future payments and repeating standing orders that send on their own.
Scheduled payments let players tell the bank to move money later, set up from inside the bank app. A scheduled payment is one-off - dated for a single future day, with the money held aside straight away and refunded if cancelled before it sends. A standing order repeats on a schedule (weekly wage, regular contribution); each run is charged when due and skipped if the account is short. Everything is player-driven; you just set the limits in config/scheduled.lua.
Config.Scheduled = { enabled = true, maxPerPlayer = 25, -- max active standing orders + scheduled payments per player maxDelayDays = 90, -- furthest out a one-time payment may be scheduled}
Option
What it does
Default
enabled
Turns the whole feature on or off. false hides scheduled payments and standing orders from the app.
true
maxPerPlayer
Most active items a player can have at once, standing orders and scheduled payments counted together. At the cap they must cancel one to add another.
25
maxDelayDays
How far ahead a one-time scheduled payment can be dated. Does not apply to standing orders, which repeat until cancelled.
In the bank app’s scheduled payments section they pick the type, enter who to pay, how much, and when, then confirm. One-time payments hold the money immediately (refunded if cancelled); standing orders take nothing until each run is due.