Fixer: the contract board

Fixers post contracts, runners take them and get paid. Three Night City fixers keep a board: Rogue at the Afterlife, Wakako Okada in Japantown and Regina Jones in the Kabuki market. Their own contracts are always up, and players with the fixer job post more from their own pockets. Every reward waits in escrow from the moment the contract is posted, so it can always be paid, and it goes back to the poster in full when nobody finishes in time.

The board ties the other roleplay jobs together. A job order asks for work another job reports, such as a netrunner's breach, an implant installed at the ripperdoc or CHOOH2 refined at Petrochem, and pays when that job says it is done.

The job is the rp_fixer resource, version 2.0, from the Open2077/open77-resources repository. It is built on the world-interaction libraries and is experimental like them.

How the board plays#

The fixer points#

Each fixer point has a contact standing beside the board and a pin on the map. Walk up to it and press E on Contract board. The same card also hands over the goods of a retrieval on F (Hand over the goods).

Every board lists every open contract in the city: what it pays the runner, the fixer who posted it, the time left and the reputation it needs. Your own contracts come first, then the ones posted at this fixer point. A contract above your reputation is greyed out and shows the tier it needs, for example trusted (8+). /contracts opens the board when you stand within 4 m of a fixer point. Anywhere else it lists the board in chat and tells you how far the nearest fixer is:

Nearest fixer: Regina's corner (Regina Jones), 120 m away.

Runners: take a contract and do it#

Pick a row to read the brief, what it pays and what the fixers keep, then press Take the contract. You can hold two contracts at once. /contract lists yours with their progress and the time left, and the map shows a pin for each, with the route to the first.

Contract taken: #25 Noodle Row pickup: pick it up at Kabuki Market, Noodle Row, 1 h 59 min left.

A carried crate is dropped at your feet if you get into a vehicle, draw a weapon, fall, die or disconnect: pick it up again from where it lies. The board tells you so:

The crate of #25 fell from your hands, at your feet. Pick it up again.

When the contract is done, the runner's share lands in cash in one operation, the fixers' cut goes to the fixer society, your reputation rises and the poster is told:

Contract #25 done: 450 eddies in cash. Reputation 4 (known).

To walk away from a contract, open its row and press Abandon it, or type /contract drop <n>. It goes back on the board and you lose 1 reputation point. A taken contract that runs out costs 1 point too.

Bounties: open or claimed#

• Open bounty. Nobody takes it. Its cyberpsycho is out as soon as the contract goes up, and whoever kills it is paid. The poster is never paid for their own bounty: if they kill it, it comes back a minute later.
• Claimed bounty. The cyberpsycho appears when a runner takes the contract, and only that runner is paid. When someone else kills it, the contract decides: refund voids the contract and returns the reward to the poster, nobody is paid; respawn sends another cyberpsycho a minute later.

The cyberpsycho guards its sighting within 12 m and attacks the nearest player within 25 m. A kill is credited to the player the platform names as the killer, or else to the last player who hit it within 30 seconds. The body stays 30 seconds, then goes. A cyberpsycho never appears with a player standing within 4 m of the sighting: it waits until the spot is clear.

Fixers: post a contract#

You need the fixer job and must be on duty: type /service to clock in. Stand at any fixer point and pick Post a contract at the bottom of the board.

1. Pick a type. The list shows each contract type with its reward range and the reputation it needs from runners.

2. Fill the form. Set the reward with the slider (in steps of 50 eddies, within the type's range), the time to expiry (1, 2, 4, 8 or 24 hours, or the type's own), an optional brief of up to 120 characters, and for a bounty who gets paid: Only the runner who takes it or Whoever kills it.

3. Confirm the escrow. A last card shows what leaves your wallet now, what the runner gets and what the fixers keep. Post it takes the reward from your cash, then your bank, into escrow:

   Contract #26 is up at Regina's corner: Noodle Row pickup, 500 eddies escrowed (450 eddies to the runner, 50 eddies to the fixers).

You are told when a runner takes it, walks away from it, completes it or lets it run out. While nobody holds it, you can cancel it from its row (Cancel, refund me) or with /contract cancel <n>. The whole reward comes back:

Contract #26 cancelled: the refund is on its way.
Contract #26 cancelled: 500 eddies back in your wallet.

A runner on a contract cannot be cancelled out of it. You can have four live contracts posted at once, and you cannot take your own.

Your drop box. The goods of a retrieval you posted go into your drop box. When it holds something, Collect your drop box appears on the board, and picking it (or typing /contract box at a fixer point) moves everything into your pockets in one operation.

The NPC fixers#

Rogue, Wakako and Regina each keep two of their own contracts on the board at all times. When one closes, another of their types goes up within five minutes. Their rewards are drawn in the type's range, and their cut is 15%. A new contract is announced in chat to the players whose reputation lets them take it, and to everyone for an open bounty.

What everyone nearby sees#

The contacts at the boards, the fixer pins on the map, a runner carrying a crate through the market, the cyberpsycho fighting whoever comes close, and its body for 30 seconds after the kill.

<template> is a template id from the contract table, for example regina_noodle_drop.

Reputation#

Each player has one reputation score, saved in SQL and kept across restarts.

A completed contract adds its repGain (1 to 4 points). Walking away from a contract or letting it run out takes 1 point. The score never drops below 0. A contract asks for a minimum score (minRep); below it, the row is greyed out and taking it is refused.

Contracts and rewards#

The board ships 16 contract types. The reward is the gross amount held in escrow; the runner receives it minus the fixers' cut.

Rewards are in eddies. Players can post every type; the NPC fixers post the types listed in their own offers, which covers all of them except junkyard_psycho. A player fixer posts at whichever fixer point they stand at.

Money and what can go wrong#

All money moves through rp_economy, and goods through open77_transactions. Each step is one operation whose id is derived from the contract, so a retry, a double press or a restart replays the first receipt instead of paying again.

Nobody withdraws from fixer_escrow: it is not a job. Its balance should equal the rewards of the contracts that hold escrow, and fixer.status prints both so an operator can compare them.

A payout or refund that the economy does not answer in time is sent again every 15 seconds with the same operation id until it settles. A posting whose escrow answer never came is settled after 30 seconds: opened if the money moved, dropped if it did not. The poster is told while it waits:

The escrow is still settling: the contract goes up as soon as it clears.

After a disconnect or a restart#

• The runner disconnects. The contract stays theirs, and its time keeps running. A crate they carried is left where they stood; after they reconnect, the board tells them about each contract they hold, and the pins come back.
• The poster disconnects. The contract stays on the board. Payouts, refunds and drop-box deliveries do not need the poster online.
• The server restarts. Contracts are saved in SQL and reloaded at start, in their state and with their runner. A delivery crate is placed again where it was last set down, a bounty's cyberpsycho is out again at its sighting, and a payout, refund or hand-over that was under way is settled from the economy's and the coordinator's records. Contracts that ran out while the server was down are refunded on the first pass. Reputation is saved per change, each change once.

Set up the board#

Requirements#

• A MySQL or MariaDB database. Contracts and reputation are stored in SQL; without a database, the board stays closed.
• The platform libraries open77_transactions, open77_actions, open77_uikit and open77_notifications, with the libraries open77_actions depends on (open77_animations, open77_props, open77_interactions).
• The RP pack resources rp_jobs, rp_inventory, rp_economy and rp_bank. rp_identity is optional: with it, the board names players by their character.
• For the job orders and the boxed-implant retrieval, the jobs they name: rp_netrunner, rp_ripperdoc, rp_chooh2, rp_techie, rp_trauma and rp_nomade. Without rp_ripperdoc, the NPC fixers skip the Gorilla Arms retrieval. The other job orders stay on the board but nobody can complete them.

Load the resources#

In server.jsonc, add the resources to resources.load after the ones you already have, libraries first (Lua resources):

"resources": {
  "load": [
    // ...your existing resources...
    "open77_animations", "open77_props", "open77_interactions",
    "open77_transactions", "open77_actions", "open77_uikit", "open77_notifications",
    "rp_jobs", "rp_inventory", "rp_economy", "rp_bank", "rp_identity",
    "rp_fixer"
  ]
}

In the same file, make pockets, stashes and wallets accounts of open77_transactions:

"convars": {
  "rp_inventory_backend": "transactions"
}

Let the board write#

Two open77_transactions settings decide which resources may change which accounts and who may create value (who may write). Set them once in the server console:

tunable.set open77_transactions writers rp_fixer:char+stash, rp_economy:cash+bank+soc, rp_inventory, <your other writers>
tunable.set open77_transactions mint1 rp_economy sys:* money 2000000

• writers. The default * lets every resource write and needs no change. If your server uses a list, add these entries to it and keep your other jobs' entries. rp_fixer:char+stash lets the board take a retrieval's goods out of the runner's pockets and put them in the poster's drop box (stash:fxbox.<subject>), then empty that box into the poster's pockets.
• mint rule. rp_economy creates the NPC fixers' rewards. The mint1 rule above is rp_economy's usual ceiling: use it if your server does not have it yet, in any free mint1 to mint6. Goods handed to an NPC fixer are destroyed, which needs no mint rule.
• rp_economy's allowance. The NPC rewards also count against rp_economy's own hourly allowance for rp_fixer, 200 000 eddies by default (EconomyConfig.mint.callers.rp_fixer in rp_economy/server/config.lua). A refunded NPC contract gives its amount back.

Start the board#

ensure open77_transactions
ensure open77_actions
ensure rp_fixer

These three declare auto_start false. To start them with the server, put the same lines in server.jsonc:

"startup": {
  "commands": [
    "ensure open77_transactions",
    "ensure open77_actions",
    "ensure rp_fixer"
  ]
}

The server log then shows:

[rp_fixer] loaded 0 live contracts (), next number 1
[rp_fixer] ready: 3 fixer points, 16 templates, escrow society fixer_escrow, cut society fixer

A few seconds later the NPC fixers post their first contracts. The board creates the SQL tables rp_fixer_contracts, rp_fixer_reputation, rp_fixer_rep_log and rp_fixer_gigs (one history row per settled contract). Reputation saved by an earlier version of the board is kept.

Staff the board#

Runners need no job. The fixer job ships with rp_jobs and is not joined at the employment agency: a boss or an admin hands it out. In the server console:

setjob 12 fixer 3            # player 12 becomes the fixers' boss

The boss then hires fixers with /embaucher <playerId> [grade], or by ALT+clicking a player and picking Hire into Fixer, and they clock in with /service. The cut of every contract goes to the fixer society, which also pays the fixers' salaries.

Console and ACL#

These commands are restricted: run them from the server console, or grant them to admins.

To let an admin use them in game, add the permission to their entry in your ACL file (server ACL):

"permissions": [
  "command.fixer.*",
  "command.setjob"
]

The player commands (/contracts, /contract) need no ACL: the board checks the fixer job and duty itself when a player posts.

Configuration#

Everything is in the resource's server/config.lua (FixerConfig). Rewards are in eddies, durations in milliseconds unless the key says hours, and positions in metres. After an edit, run restart rp_fixer. Contracts already posted keep their reward, cut and expiry.

Add a contract template#

A template is one entry of C.templates. Its id must be lower-case letters, digits and _, at most 32 characters. Common fields are kind, title, brief, reward = { min, max }, hours, minRep, repGain and posters (npc, player). Then, by kind:

This example adds a delivery from Vik's clinic to Regina's corner and a job order for two successful breaches, lets Regina post both, and lists them in the players' post menu:

-- server/config.lua, after the shipped C.templates
C.templates.regina_vik_parcel = {
    kind = "delivery", title = "A parcel from Vik", posters = { npc = true, player = true },
    brief = "Vik has something for Regina. Walk it over from the clinic, no detours.",
    from = "vik_clinic", to = "regina",
    reward = { min = 700, max = 1000 }, hours = 2, minRep = 0, repGain = 1,
}
C.templates.regina_double_breach = {
    kind = "job", title = "Two clean breaches", posters = { npc = true, player = true },
    brief = "Regina wants two systems cracked before the NCPD notices. Any successful breach counts.",
    job = "netrunner", kinds = { "breach_success" }, count = 2,
    reward = { min = 1800, max = 2600 }, hours = 6, minRep = 3, repGain = 2,
}
-- Regina's NPC board posts them too (it keeps two of its offers open).
table.insert(C.hubs.regina.offers, "regina_vik_parcel")
table.insert(C.hubs.regina.offers, "regina_double_breach")
-- Players see them in the post menu.
table.insert(C.templateOrder, "regina_vik_parcel")
table.insert(C.templateOrder, "regina_double_breach")

After restart rp_fixer, the start line counts 18 templates. A template with a mistake is left out and the log says why, for example template regina_vik_parcel left out: unknown_drop. fixer.post regina_vik_parcel regina posts one at once to try it.

Change the cut and the reputation tiers#

-- server/config.lua
C.cutRate = { npc = 0.20, player = 0.05 }   -- the fixers keep 20% of NPC contracts, 5% of players'

C.tiers = {
    { name = "street", min = 0 },
    { name = "known", min = 5 },
    { name = "trusted", min = 12 },
    { name = "legend", min = 30 },
}
C.reputation = { floor = 0, abandon = -2, expire = -2 }   -- walking away costs more

-- A template's own gate: the Northside bounty now needs the new "trusted".
C.templates.regina_psycho_northside.minRep = 12

The tiers only name ranges of the score; each template's minRep is what gates it. Raise the minRep of the templates you want behind a new tier.

Move a sighting#

A cyberpsycho needs room to fight and a line of fire. To move one:

1. Stand where it should appear, outside any safe zone. Type /pos to copy your position, and /rot for your yaw.
2. Paste them into the sighting, mark it as walked, then restart rp_fixer.

-- server/config.lua, in C.sightings
northside = {
    label = "Northside industrial",
    position = { x = -1914.454, y = 2739.485, z = 10.899 },   -- from /pos
    yaw = -47.0,                                              -- from /rot
    measured = true,                                          -- walked in game
},

Keep the key (northside) so the templates still find it. A bounty already on the board moves with the sighting at the next restart. If you rename a key, saved bounties fall back to their template's current sighting.

For resource authors#

Report work a job order can count#

A job order counts the server event rp:job:completed. Fire it once a step of your job is saved, with the player who did it and a reference that is unique for that step:

-- server, after the step is committed
TriggerEvent("rp:job:completed", {
    job = "chooh2",            -- your job's name in the event
    kind = "refine",           -- the step
    playerId = 3,              -- who did it
    ref = opId,                -- unique per step: the same ref is counted once
    data = { canisters = 2 },  -- anything a template's match or countField reads
})

An event counts toward a contract when the contract is taken by that player, its job and one of its kinds match, every match field equals the event's data field, and its ref was not counted before for that contract. With countField, the event counts the number in that data field; otherwise it counts 1. The shipped job orders read:

Events and exports#

-- server: fired by the board once a contract is paid
AddEventHandler("rp:job:completed", function(e)
    -- e.job == "fixer", e.kind == "contract_completed"
    -- e.data = { contract, seq, contractKind, template, hub, reward, net, cut, poster }
end)
AddEventHandler("rp_fixer:contract", function(id, state, playerId, summary)
    -- state: open, taken, abandoned, completed, expired, cancelled, spoiled
end)

exports.rp_fixer:reputation(playerId)     -- integer score, 0 when unknown
exports.rp_fixer:contract(idOrNumber)     -- a summary, or nil
exports.rp_fixer:heldBy(playerId)         -- the contracts the player holds

-- An NPC fixer posts on your resource's behalf (asynchronous), funded like any NPC contract.
local summary, why = Open77.exports.call("rp_fixer", "postContract",
    { template = "regina_psycho_kabuki", hub = "regina" }):await()

rp:job:completed is a server event: any server resource can fire it, clients cannot. The board trusts the jobs running beside it and counts each ref once.

When something is refused#

The board explains every refusal in words. The ones a player or an operator can act on:

When the NPC fixers cannot post because of a missing rule, the log says so and they wait 30 minutes before trying again.

Limits#

• Deliveries are on foot. A crate cannot ride in a vehicle; getting in drops it.
• Placed points. Only the Kabuki sighting is marked as walked in the config. Stand on the other fixer points, pickups and sightings on your server and correct them with /pos before opening the board.
• Contacts. The NPC at each board is a generic passive civilian. Character records for Rogue, Wakako and Regina are listed in the config to try.
• Kill credit. A kill is credited through the platform's hit pricing. On a host that refuses it, the cyberpsycho still appears, no kill is credited and the bounty runs out and is refunded.
• Spawns near players. A body that appears on top of a player can be credited to that player for hits nobody fired, which is why a cyberpsycho never appears within 4 m of a player.
• Cyberpsycho records. The cyberpsycho uses the Maelstrom combat record players already fight; the dedicated cyberpsycho records are listed in the config to try.
• CHOOH2 retrieval. "Two cans of CHOOH2" asks for the rp_inventory fuel can (chooh2). The canisters refined at Petrochem are a different item and are not accepted.
• Nomad job order. "A nomad run" counts one deliver event, and the nomad job reports one per crate delivered or sold: the first crate completes it.
• Trauma job order. "Keep them breathing" counts stabilise or revive; the Trauma Team job reports stabilisations, so two stabilised patients complete it.
• Other jobs' renames. A job order matches the job, kind and data names in the table above. If a job renames them, change the template with it.
• Missing jobs. A job order whose job is not running stays on the board until it runs out and is refunded.
• Board size. 48 live contracts on the server, 2 per runner, 4 per player fixer; the board shows 56 rows at most.
• Other crates. A crate carried for another resource also sees Deliver the crate at a fixer point. Putting it down there is that resource's business.
• One event after a payout. The board's own rp:job:completed is fired once, after the payout is saved. A crash in that instant loses the event, never the payment.