The loot-split ledger for ironmemes.
A drop lands on one player, the split says who else was on the kill, and the debt is live from that second.
Everything is amendable, nothing is ever deleted, and the whole thing runs on 9 slash commands.
/split
creates S#
Record a drop. The receiver immediately owes every other player on the kill an equal share; the rounding dust stays with the receiver.
/split item receiver player2 [value] [player3 … player9]
item
required
The item that dropped. Autocompletes against the OSRS Wiki item table.
receiver
required
Who the drop landed on. Always counts as a participant too.
player2
required
A teammate on the kill — a split needs at least one besides the receiver.
value
optional
GP value: 1.2b, 340m, 500k, 1,234,567. Defaults to the live wiki guide price; correct it with /edit once it sells.
player3 … player9
optional
The rest of the team, up to nine players on one split.
Example
/split item:Twisted bow receiver:@Vic player2:@Sam player3:@Kai
/balances
reads
Suggested payments based on each player’s net balance across the clan. Chains and cycles cancel out, reducing transfers while preserving everyone’s total.
/balances [player]
player
optional
Only the balances that involve this player.
Example
/balances player:@Sam
/allbalances
reads
A table of everyone’s payments and net GP. Positive means receives, negative means pays. The clan net total is zero.
/allbalances [view] [page]
view
optional
simplified (default) or original pairwise debts.
page
optional
Page number, starting at 1. Shows up to 12 payments and 12 player nets per page.
Example
/allbalances view:original page:1
/settle
creates P#
Record a payment you made, including a suggested payment to someone you did not originally owe. The clan’s suggested payments update automatically.
/settle to amount [note]
to
required
Who you paid.
amount
required
GP you handed over, e.g. 340m. Partial payments and overpayments are ordinary.
note
optional
Anything worth remembering about the payment.
Example
/settle to:@Kai amount:340m note:traded at GE
You record your own payments. The payee sees the message and can void it if it never happened.
/charge
creates C#
Record a debt outside a split — a tab from before the bot, or the difference on a cut that wasn't even. Owed to you, or to someone else if you name them. The options are named for the way the GP will travel: it comes from whoever owes, and goes to whoever is owed.
/charge from amount note [to] [from2 … from8]
from
required
Who owes it — the GP will come from them.
amount
required
GP each named player owes.
note
required
Why. A charge has no drop behind it, so the reason is the only evidence of why it exists — it is shown on every screen. Put the date of an old debt here.
to
optional
Who is owed — the GP goes to them. Defaults to you. Naming someone else lets you log a debt between two other players while neither is around; the page then shows that you recorded it.
from2 … from8
optional
More players who owe. Each gets their own charge for the full amount — this is shorthand, not a group tab.
Example
/charge from:@Sam amount:50m note:CoX supplies, 3 Aug
Charges are bookkeeping, not loot: they move balances, but never count towards splits recorded or all-time split value.
/owe
creates C#
The other direction: record a debt you owe. Useful for backfilling a tab while the person you owe is offline — you do not have to wait for them to charge you.
/owe to amount note [to2 … to8]
to
required
Who you owe — the GP goes to them.
amount
required
GP you owe each named player.
note
required
Why. Same rule as /charge — it is the only evidence of why the debt exists, and it is where the date of an old debt goes.
to2 … to8
optional
More players you owe. You owe each of them the full amount — the embed states the running total, since fanning out multiplies it.
Example
/owe to:@Sam to2:@Kai amount:50m note:Vorkath tab, 12 Aug
Identical to /charge with the sides swapped, and it writes the same C# rows. There is no from — on /owe it is always you. A debt you record against yourself needs nobody else to confirm it.
/history
reads
Recent activity — splits, payments and charges interleaved, newest first.
/history [player]
player
optional
Only the entries that involve this player.
Example
/history player:@Vic
/edit
amends S#
Amend a split — usually swapping the guide price for what it actually sold for. Balances recompute retroactively, including for pairs that already settled.
/edit id [value] [add_player] [remove_player]
id
required
The split to amend, e.g. S12 (a bare 12 works too).
value
optional
The corrected GP value, e.g. 950m.
add_player
optional
A teammate who was missed off the kill.
remove_player
optional
A player who wasn't actually there.
Example
/edit id:S12 value:950m
Participants of that split, whoever recorded it, or a server admin. Only splits are amendable — a wrong payment or charge is voided and re-recorded.
/void
retires S# P# C#
Mark an entry as never having happened. It stays in the ledger struck through and stops counting towards balances — nothing is ever deleted.
/void kind id
kind
required
Which ledger it is in: split, payment, or charge.
id
required
The entry, e.g. S12 / P7 / C3. If the prefix disagrees with kind, the command refuses rather than guessing.
Example
/void kind:charge id:C3
Parties to the entry — a split's participants, a payment's payer or payee, a charge's two players — plus whoever recorded it, or a server admin.