Stables & contracts
Stables let a manager build an RP identity and recruit boxers under contract. Everything is managed from the tablet (/boxing or the item, depending on your configuration).
Create a stable
From the tablet, a manager creates their stable and gives it a name (e.g. "The Golden Lion Stable"). This name is the stable's public identity.
Recruit boxers
The manager proposes a contract to a boxer. The contract specifies, among other things, the terms and the down payment paid on signing.
Contract lifecycle
| Step | Description |
|---|---|
| Proposal | The manager sends a proposal to the boxer. |
| Signing | The boxer accepts; the down payment is paid. |
| Rejection | The boxer declines the proposal. |
| Termination | The manager or the boxer ends the contract. |
Paper contract (optional)
On signing, each party can receive a paper contract in their inventory. Using this item opens a page showing the contract as it was signed.
To enable this option:
- The
josk_item_contractitem must exist in the framework's inventory (see Installation). ServerConfig.Contracts.issueOnSignmust betrue.
If the item does not exist, signing continues without error — the contract then stays purely digital.
Next step
- Tournaments & leagues — have your stable's boxers compete.