Project Zomboid × LibertyTalk: Talky

Talky connects your Twitch and YouTube events to your Project Zomboid game. When Bob follows your channel, a banner announces him and, two seconds later, a zombie appears about ten tiles from your character, with "Bob" written in purple above its head. Talky has two pieces: a mod for the game and a small program, the bridge, that runs on your PC.

Why a bridge? Project Zomboid's Lua can't receive network calls: it can only read and write files in %USERPROFILE%\Zomboid\Lua. The bridge receives LibertyTalk's calls on http://127.0.0.1:7420 and writes the actions into that folder, which the mod reads every second.

Part 1 installs Talky and connects it to LibertyTalk with the official widget. Part 2 explains the workflows on both sides, so you can change what happens in the game when a viewer cheers 500 bits.

What you need

• Windows 10 or 11.
• Project Zomboid Build 42, version 42.20.1 or later. This part covers single player; for a server, see part 3.
• Node.js version 18 or later, to run the bridge.
• cloudflared, Cloudflare's tool that gives the bridge a public address.
• A LibertyTalk account with your Twitch or YouTube channel connected to your community.

Node.js and cloudflared install with two commands in a PowerShell terminal:

winget install OpenJS.NodeJS.LTS
winget install --id Cloudflare.cloudflared

Get Talky

You can download Talky from two places. The Steam Workshop ships the mod only: it refuses .bat, .exe and .zip files, and rewrites its folder on every update, which would wipe the bridge's configuration. The GitHub releases contain the bridge, start-bridge.cmd that starts it, and a copy of the mod to play without the Workshop.

• Talky on the Steam WorkshopThe mod, kept up to date by Steam. Subscribe to the Talky item.
• Talky releases on GitHubThe Windows zip: the bridge, start-bridge.cmd and a copy of the mod.

Install

1. 1

   Step 1

   Extract the zip to a folder you keep

   For example Documents\Talky. Don't extract it into %USERPROFILE%\Zomboid\mods or into the Workshop folder. Steam rewrites the Workshop folder on every update, and in Zomboid\mods, removing or replacing a mod can take the bridge and its bridge\config.json file with it. At every start, the bridge reports a folder placed in Zomboid\mods.

2. 2

   Step 2

   Without the Workshop only: copy the mod

   Copy the zip's Talky folder into %USERPROFILE%\Zomboid\mods, to get %USERPROFILE%\Zomboid\mods\Talky\42\mod.info. Copy only this folder: the bridge stays in Documents\Talky. If you subscribed on the Workshop, skip this step: Steam already installs the mod.

There's nothing else to install: the bridge creates its configuration itself, on its first launch.

Start the bridge

Double-click start-bridge.cmd. A black window titled "Talky bridge" opens. It checks that Node.js 18 or later is installed, then starts the bridge. On the first launch, the bridge creates bridge\config.json from bridge\config.example.json: it draws a random 48-character token, sets the language of the examples to the one of Windows (fr when the regional format is French, en otherwise) and copies the token to the clipboard without showing it. You'll paste it into the widget at the end of this part. The window then shows these lines, each prefixed with the time:

created ~\Documents\Talky\bridge\config.json with a random token (language: en)
the token is in your clipboard and in config.json, never shown here: paste it into "Bridge token" in the LibertyTalk widget
created ~\Zomboid\Lua\talky_config.json from config.json
config loaded: 10 webhook(s), 14 workflow(s)
Talky bridge 0.4.0 listening on http://127.0.0.1:7420
game folder: ~\Zomboid\Lua
http steps allowed to: *.liberty-talk.com
  webhook  POST /hooks/follow
  webhook  POST /hooks/sub
  webhook  POST /hooks/gift
  webhook  POST /hooks/bits
  webhook  POST /hooks/raid
  webhook  POST /hooks/donation
  webhook  POST /hooks/superchat
  webhook  POST /hooks/member
  webhook  POST /hooks/command
  webhook  POST /hooks/points

At every start, the bridge can also show lines that start with warning:. It starts anyway, but each one points at a setting to fix: cloudflared missing from the PATH, Talky installed twice (a copy in Zomboid\mods on top of the Workshop), or the bridge folder placed in Zomboid\mods. The troubleshooting at the end of this part gives the fix for each.

Keep this window open for the whole session: if you close it, nothing reaches the game anymore. If the bridge stops on an error, the window shows the message, then The bridge has stopped., and waits for you to press a key. In its messages, config.json errors included, the bridge writes ~ instead of your user folder, which keeps your Windows user name off screen if the window shows up on stream.

Enable the mod and open the menu

1. 1

   Step 1

   Enable the mod

   In Project Zomboid's main menu, open Mods and tick Talky - LibertyTalk Live Events.

2. 2

   Step 2

   Start a game

   A new single-player game or a saved one.

3. 3

   Step 3

   Open the Talky menu with F8

   You can change the key in Options > Keybinds > Talky, "Open the Talky window" line.

4. 4

   Step 4

   Check the Status page

   At the bottom left, the pill must show "Bridge connected" in green, and the top of the page "Bridge connected on port 7420 - 0 job(s) waiting", followed by the bridge version, then the "Single player: the jobs run in this game." line. A red "Bridge offline" pill comes with the message "Bridge offline: run start-bridge.cmd (or node bridge/bridge.js) on this PC." In that case, see troubleshooting at the end of this part.

The window has five pages, listed on the left under "TALKY". Status shows the connection, the public address and the latest events received. Webhooks lists the /hooks/<id> addresses LibertyTalk calls. Workflows holds what the game does for each event. Game events links the death of a named zombie or of the player to a workflow. Settings sets the caps, for example "Max zombies per action" at 60. The Save button, bottom right, turns into Save * while a change isn't saved.

Test without LibertyTalk

Before plugging in Twitch, check that the bridge and the mod talk to each other. In the F8 menu, Workflows page, select new_follower in the list on the left, type Bob in the "Test with the name" field and click Test now. The game confirms the test was sent with a notice, and the bridge window writes a line such as [test] new_follower -> 3 game step(s) (job #1) user=Bob, whose job number goes up with each run.

You can also run the test from a second terminal opened in the Talky folder, while the bridge is running:

node bridge\bridge.js fire new_follower user=Bob

In the game, the "Bob joins the horde!" banner shows ("Bob rejoint la horde !" with the French examples), then a zombie named "Bob" appears between 8 and 14 tiles from your character. If nothing shows up, check that the game isn't paused: the mod runs nothing while paused, in the main menu or when your character is dead. Test now also sends bits at 500, viewers at 10 and tier at 1000: on the bits workflow, it spawns 5 zombies.

Open the tunnel

LibertyTalk refuses to call a local address such as 127.0.0.1, to block requests to private networks. The cloudflared tunnel gives the bridge a public https address. In a new terminal, run:

cloudflared tunnel --url http://127.0.0.1:7420

Optional: also paste this address in F8, Status page, "Public URL (Cloudflare tunnel)" field, then click Save. The webhook list then shows their public addresses, token masked. Copy command copies node bridge\bridge.js url <webhook> for the selected webhook: run in a terminal opened in the Talky folder, this command puts the full URL, token included, in the clipboard and prints it masked. The game never sees the token. The widget doesn't need it: this command is for when you build a LibertyTalk workflow yourself.

Install the official widget

The official "Project Zomboid · Talky" widget already holds the ten LibertyTalk chains that call the bridge: follow, subscription, gifted subs, bits, raid, channel points, chat command, Streamlabs donation, Super Chat and new YouTube member. You fill in the tunnel address and the token, then you activate it.

1. 1

   Step 1

   Install it in your community

   Select your community in the sidebar. On the widget's page in the Marketplace, click Install. The same button is on its card in the Official library of Widgets. LibertyTalk adds the widget to the selected community, switched off, then opens its page.

2. 2

   Step 2

   Keep the Global scope

   On the widget's page, keep the Global scope, selected by default: the widget will listen to every Twitch and YouTube account of the community. To come back to this page later, open Widgets and click the Project Zomboid · Talky card, under "Workflow widgets".

3. 3

   Step 3

   Fill in its configuration

   In the Widget configuration tab, open the "Talky bridge connection" section and fill in "Talky bridge public URL" and "Bridge token". The table below details each field. Click Save: the "Widget configuration saved." message confirms it.

4. 4

   Step 4

   Activate it

   In the Activation block, click Activate: the "Inactive on Global." line turns into "Active on Global." and the Listening to block lists the accounts it listens to. The page won't activate while a configuration change isn't saved. If only your Twitch channel is connected, the YouTube triggers stay silent; they plug in when you connect YouTube to the community.

Check end to end

Ask someone to follow your channel, or follow it from a second account. A few seconds later, the bridge window writes a [hook:follow] new_follower -> 3 game step(s) line, the zombie appears, and in F8, Status page, the "Latest events received by the bridge" list shows hook:follow -> new_follower (Name) after the time. On the LibertyTalk side, open the Executions tab of the widget's page and click "Load last run" to see the same run.

Troubleshooting

Two engines, one model

A LibertyTalk workflow starts from a trigger, an event such as "New follower", then runs its nodes in order and passes them the event's data. The Talky bridge has its own, smaller engine: each /hooks/<id> webhook runs a bridge workflow, a list of steps the mod carries out in the game.

Keep this boundary in mind: LibertyTalk decides which events go to the game and with which data, the bridge decides what happens in the game.

What the official widget does

The widget holds ten chains built on the same pattern: a trigger, an "If (classic)" node that tests the event's box, then a "Webhook / API call (background)". Each call sends a POST to {talky_bridge_url}/hooks/<id> with the {"X-Bridge-Token":"{talky_token}"} header. The call runs in the background so a slow tunnel doesn't delay your community's other events. The subscription chain also tests is_gift: it only relays subscriptions that aren't gifts, the gift chain handles the rest.

The bridge workflows in the last column are the ones shipped with Talky. You edit them in F8, Workflows page, without touching the widget. For example, Super Chats and donations share donation, which draws either a shotgun with shells, a heal with canned food, or a pickup truck.

For a viewer to get a zombie named after them, use an event that provides a name outside the chat: a follow, bits, or a channel points reward whose title contains "zombie". That last one runs points_zombie, which names the zombie after the viewer who redeemed the reward.

Variables

In LibertyTalk, a variable is written between single braces. Each trigger declares its own: "Bits received (cheer)" provides {bits}, {user_name} and {is_anonymous}, and "Channel points reward" provides {reward_title} and {reward_cost}. The editor's variable picker offers them in the nodes that follow.

The widget variables, {talky_bridge_url}, {talky_token} and {talky_command}, are filled in at install time and read again on every run. They carry the talky_ prefix because the event's data takes priority: a widget variable named user_name would be hidden by the trigger's. {talky_token} is declared secret: its value is masked in execution traces.

A misspelled variable stays as it is: with {user_nmae}, the bridge receives that text and your zombie is called "{user_nmae}". A variable the trigger declares but the event lacks becomes empty, like {user_name} for an anonymous cheer; the bridge then uses its default name.

The bridge has its own templates, between double braces, with filters: {{bits | div:100 | floor}} gives 4 for 450 bits. {{user}} takes the first filled field among user_name, author_display_name, donor and a few others, which lets the same new_sub workflow serve Twitch subscribers and YouTube members. When none of these fields is filled, {{user}} is the name of anonymous events.

Decide in LibertyTalk or in the bridge

The two engines don't do the same things. LibertyTalk has no loop or math node: a node can't repeat itself "once per 100 bits". The bridge, for its part, only sees what LibertyTalk sends it. This table shows where each need belongs.

In practice, let LibertyTalk route and filter, and hand the bridge the raw numbers. The widget follows this rule: it sends {bits} as is and the bridge works out the size of the horde.

Example 1 · A follow, a named zombie

When Bob follows the channel, the widget sends {"user_name":"Bob"} to /hooks/follow. The bridge runs new_follower, which holds three steps:

1. notify: a banner with the name, in purple #b388ff.
2. wait: a 2-second pause in the game.
3. spawn_zombie: a zombie named {{user}}, between 8 and 14 tiles from the character, with its name shown in the same colour.

To change this zombie, open F8, Workflows page, new_follower, and double-click the zombie step in the step list. Tick "Crawler" to make it crawl, or set "Count" to 3: three zombies appear, named "Bob #1" to "Bob #3", or all "Bob" with "Same name for all". Click OK, then Save: the bridge reloads the configuration without restarting.

Example 2 · Bits, a horde to match

The widget passes {bits} on unchanged, because LibertyTalk can neither divide a number nor repeat a node. The bridge's bits workflow does the math:

"bits": {
  "steps": [
    { "if": { "bits": { "gte": 1000 } },
      "then": [ { "action": "helicopter" } ],
      "else": [
        { "if": { "bits": { "gte": 100 } },
          "then": [
            { "repeat": "{{bits | div:100 | floor}}", "max": 20, "steps": [
              { "action": "spawn_zombie", "name": "{{user}}", "sameName": true, "distance": 18 },
              { "action": "wait", "seconds": 1 }
            ] }
          ],
          "else": [ { "action": "noise", "radius": 25 } ] }
      ] }
  ]
}

• 450 bits: 450 / 100 rounded down gives 4 zombies named after the viewer, one per second, at most 18 tiles away.
• 1,000 bits or more: the helicopter comes over, with no named zombie.
• Under 100 bits: a noise draws the zombies within 25 tiles.

The max: 20 cap protects the game if you remove the helicopter branch: 5,000 bits would otherwise give 50 zombies. To test without spending bits, Test now on bits sends 500 bits, which makes 5 zombies.

Example 3 · A points reward, an event of your choice

The widget sends every channel points reward to the same webhook, points, with user_name and reward_title. The bridge picks the workflow with routes: the first one whose condition is true wins. The routes shipped with Talky look for a word in the title, in English unless the bridge was first started with settings.language set to fr:

• "helicopter" runs points_helicopter: the helicopter comes over, at most once every 10 minutes.
• "heal" runs points_heal: full heal and floating text with the viewer's name.
• "storm" runs points_storm: 3 in-game hours of storm.
• "zombie" runs points_zombie: a zombie whose name, in light blue, is the name of the viewer who redeemed the reward.

The bridge's contains comparison ignores case: "Call the Helicopter" matches, but "Call the chopper" doesn't, and a bridge first started in French looks for hélico, soin and tempête. Routes using matches accept several spellings and both languages. A reward that matches no route runs nothing: the Status page shows it with "skipped: no matching route".

[
  { "when": { "reward_title": { "matches": "h[ée]lico" } },        "workflow": "points_helicopter" },
  { "when": { "reward_title": { "matches": "soin|heal" } },        "workflow": "points_heal" },
  { "when": { "reward_title": { "matches": "temp[êe]te|storm" } }, "workflow": "points_storm" },
  { "when": { "reward_title": { "contains": "zombie" } },          "workflow": "points_zombie" }
]

The same logic in LibertyTalk

Would you rather see the routing in the workflow editor? Untick "Send channel point rewards" in the widget to avoid duplicates, then build your own workflow:

1. 1

   Step 1

   The trigger

   "Channel points reward" on your Twitch account.

2. 2

   Step 2

   An exclusive Switch

   "Switch" in "Exclusive (first match)" mode, one case per reward, for example reward_title "~ matches regex" /h[ée]lico/iu.

3. 3

   Step 3

   One variable per case

   In each branch, "Set a variable" named talky_hook, with the value helicopter, heal or storm.

4. 4

   Step 4

   A single call

   Connect every branch to the same "Webhook / API call (background)": URL https://your-tunnel.trycloudflare.com/hooks/{talky_hook}, method POST, headers {"X-Bridge-Token":"your token"}, body {"user_name":"{user_name}","reward_title":"{reward_title}"}. Since this workflow isn't the widget, its address must be updated with every new tunnel.

5. 5

   Step 5

   The bridge-side webhooks

   In F8, Webhooks page, create helicopter, heal and storm with + New, then Rename, and link them to points_helicopter, points_heal and points_storm.

A single final call rather than one call per branch: beyond 5 HTTP calls reachable from one trigger, the editor shows a warning when you save.

Limit the frequency

Each bridge workflow has two delays, set in F8, Workflows page: "Global cooldown (s)" blocks the workflow for everyone, "Cooldown per viewer (s)" for the same name. By default, points_helicopter waits 600 seconds between two helicopters, and chat_zombie 20 seconds between two zombies.

chat_zombie has no "Cooldown per viewer (s)": the chat command arrives without a name, so every viewer carries the same default name, and a per-viewer delay would act as a global one. To space out !zombie, raise its "Global cooldown (s)".

On the LibertyTalk side, no node is meant for this, but the "Detect spam (repeat / flood)" moderation node can act as a delay: scope network_id, a constant value to compare (helico), a 600-second window, "Flood: max messages in the window" set to 2, then "If (classic)" on is_flood false. The first pass goes through, the next ones are blocked until the window ends, and a window can't exceed one hour.

From the game back to LibertyTalk

The mod sends three events back to the bridge: zombie_killed with name and byPlayer when a named zombie dies, player_died with hoursSurvived and zombieKills, and game_started. F8, Game events page, links each one to a bridge workflow. Example: post "Bob's zombie is down." in your Twitch chat, with the disabled report_to_libertytalk workflow Talky ships for this.

1. 1

   Step 1

   Create the incoming webhook

   In LibertyTalk, create a workflow with the "Incoming webhook" trigger and save it: the "Webhook URL & secret" field shows the address, ending in /webhooks/workflow/<token>, and the secret.

2. 2

   Step 2

   Read the zombie's name

   In "Variables from the payload", add the target variable name with the key name.

3. 3

   Step 3

   Post in chat

   Add the Twitch "Send a message" action with the content {name}'s zombie is down., then activate the workflow.

4. 4

   Step 4

   Fill in the bridge target

   Off stream, open bridge\config.json in a text editor. In httpTargets > lt_report, replace PASTE_THE_TOKEN_OF_YOUR_INCOMING_WEBHOOK with the token at the end of the incoming webhook's address and PASTE_THE_SECRET_OF_YOUR_INCOMING_WEBHOOK with its secret, save, then restart the bridge. This file stays out of reach of the game and its mods; while a PASTE_ value remains, the bridge refuses the step.

5. 5

   Step 5

   Turn on the bridge workflow

   In F8, Workflows page, select report_to_libertytalk, tick "Enabled", then click Save. Its http step only says "target": "lt_report": the address and the secret don't go through talky_config.json. If your talky_config.json comes from Talky 0.3.0, this step still carries url and headers: replace them with "target": "lt_report" ("Workflow as JSON" button), otherwise the bridge sends the call with a warning.

6. 6

   Step 6

   Link the game event

   On the Game events page, pick report_to_libertytalk for "A named zombie dies", then click Save.

"httpTargets": {
  "lt_report": {
    "url": "https://api.liberty-talk.com/webhooks/workflow/PASTE_THE_TOKEN_OF_YOUR_INCOMING_WEBHOOK",
    "headers": { "X-Webhook-Secret": "PASTE_THE_SECRET_OF_YOUR_INCOMING_WEBHOOK" }
  }
}

"report_to_libertytalk": {
  "enabled": false,
  "steps": [
    { "action": "http", "target": "lt_report",
      "body": { "event": "{{event}}", "name": "{{name}}", "hoursSurvived": "{{hoursSurvived}}", "zombieKills": "{{zombieKills}}" } }
  ]
}

The api.liberty-talk.com host is in httpAllowedHosts by default, so the step goes through without any setting. It runs in the background: it delays neither the game nor the other events. Linking "A named zombie dies" to report_to_libertytalk replaces on_zombie_killed, which spawns two "cousins" of the dead zombie 30% of the time. To keep both, copy the http step into the steps of on_zombie_killed instead.

The body also sends event, hoursSurvived and zombieKills. Link "The player dies" to the same workflow, also declare the event and hoursSurvived variables in "Variables from the payload", and a "Switch" with a case where event equals player_died can post another message when you die, for example Died after {hoursSurvived} h of survival.

Test and debug

Test the bridge alone first, with Test now or node bridge\bridge.js fire. To test the path from LibertyTalk to the bridge without waiting for a real follow, create a workflow with the "Manual trigger" and, in "Simulated variables", user_name set to Bob. Add a "Webhook / API call" to https://your-tunnel.trycloudflare.com/hooks/follow, with the {"X-Bridge-Token":"your token"} header and the {"user_name":"{user_name}"} body. The manual trigger button works even when the workflow isn't activated.

The execution console shows what each node received and produced. For the widget, open its Executions tab, then click "Load last run". Each step shows its input and output, and the "Variables" button shows every variable available at that point, with secrets masked, {talky_token} included.

Known limits

• The quick tunnel's address changes every time cloudflared starts: copy it into the widget at each session, or switch to a named tunnel.
• The chat command arrives without a name or text, because of Twitch's rule on redistributing chat messages: the !zombie zombie carries the name of anonymous events.
• An event waits 15 minutes at most: if the game stays closed or paused longer, it's dropped.
• The bridge caps every workflow: a wait step lasts 600 seconds at most, notify, say and halo texts are cut at 200 characters, a banner stays 60 seconds at most, and a repeat never goes beyond 100 rounds, whatever its max.
• YouTube Super Chats and members only arrive during a live stream, and donations only if Streamlabs is connected.
• Talky 0.5.0 was tested on Build 42.21. A game update can change the functions it uses: update the mod and the bridge together.

On a server, dedicated or hosted from the main menu of the game, the bridge does not run on the streamers' PCs: the admin runs it on the machine of the server and adds the streamers from the game. Each streamer gets an address and a token, to paste into their LibertyTalk widget. The events of their live happen around their character, and every player sees them.

• The admin of the server installs the mod on the server, runs the bridge next to it, opens a port and adds the streamers.
• Each streamer joins the server, installs the LibertyTalk widget and pastes the address and the token they got. Nothing to install on their PC but the mod, which the server asks for anyway.

For the admin: setting up the server

1. 1

   Step 1

   Add Talky to the mods of the server

   Dedicated server: in Zomboid/Server/<server name>.ini, set Mods=Talky and WorkshopItems=3830066321, the id of Talky on the Steam Workshop. The server downloads the mod when it starts, and each player gets it when joining. Hosted game: Host > Manage settings..., Mods page, then Steam Workshop page.

2. 2

   Step 2

   Set the limits

   The options of Talky are on the Talky page of the sandbox options: limits for zombies, items and weather, one switch per category, cooldowns, distance from the other players. Fire and the helicopter are off by default on a server.

1. 1

   Step 1

   Install Node.js 18 or later on the machine of the server

   On Windows: winget install OpenJS.NodeJS.LTS. On Linux: the nodejs package of the distribution if it is version 18 or later, otherwise the one from nodejs.org.

2. 2

   Step 2

   Extract the Talky zip

   Download Talky-0.5.0.zip from the GitHub releases and extract it to a folder of the account that runs the server.

3. 3

   Step 3

   Start the bridge in server mode

   With the account that runs the server: sh start-bridge.sh on Linux, start-bridge.cmd server in a terminal opened in the Talky folder on Windows. Hosted game: start-bridge.cmd server on the host's PC. The bridge window shows listening on http://0.0.0.0:7420 (server mode).

4. 4

   Step 4

   Start the server

   Its console shows [Talky] server ready (Talky 0.5.0), then [Talky] inbox ready on the first read of the jobs.

1. 1

   Step 1

   Open the TCP port 7420

   In the firewall of the machine (on Linux, for example sudo ufw allow 7420/tcp; on Windows, an inbound TCP 7420 rule) and in the one of the hosting provider, if any. Hosted game: also forward the TCP port 7420 of the router to the host's PC.

2. 2

   Step 2

   Note the public address of the bridge

   http://<public IP of the server>:7420. A private address (192.168.…, 10.…) does not work: LibertyTalk must reach the bridge from the internet.

1. 1

   Step 1

   Become admin

   The Webhooks page of F8 is reserved to admins and moderators. Dedicated server: type setaccesslevel "<username>" admin in the console of the server, or log in with the admin account created on the first start. Hosted game: see the box below.

2. 2

   Step 2

   Save the public address

   In game: F8 > Webhooks > Streamers tab. Type the address noted above in Public address of the bridge, then Save. The IP alone is enough: Talky adds http:// and the port of the bridge.

3. 3

   Step 3

   Add each streamer

   Type their username at the bottom left, then + Add streamer. A second later, the bridge has drawn a token for them and they show in the list.

4. 4

   Step 4

   Send them their address and token

   Select them, then Copy URL and token: the clipboard holds the two values of their widget, one per line. Send them in a private message.

For the streamer: connecting your live

1. 1

   Step 1

   Join the server

   The Talky mod comes with the mod list of the server: the game downloads it when you join.

2. 2

   Step 2

   Install the widget

   In the LibertyTalk dashboard: Marketplace > Project Zomboid · Talky > Install, then open its page in Widgets, as in part 1.

3. 3

   Step 3

   Paste the address and the token

   Widget configuration tab: Talky bridge public URL = the address from the admin, Bridge token = your token. Save, then Activate.

4. 4

   Step 4

   Check in game

   F8 > Status shows "You are a streamer of this server: the events of your live happen around your character."

Ports and security

• One port to open: TCP 7420 (port of bridge/config.json), to the machine that runs the bridge. The game server keeps its own ports.
• The calls from LibertyTalk arrive in http, in clear text: the token of the streamer travels in clear between LibertyTalk and the bridge. Someone who intercepts that traffic could reuse it until the next New token.
• The token of a streamer only triggers effects around that streamer, within the limits of the sandbox options of the server.

Limits

• The machine of the server must be able to run Node.js and be reachable from the internet on the port of the bridge. A rented server without command-line access, managed only through a web panel, does not fit.
• One set of workflows for the whole server: every streamer gets the same effects, around their own character. Cooldowns count per streamer.
• Weather and time of day are the same for every player, and their cooldowns count for the whole server.
• The helicopter flies to a random player: it is off by default and, when on, only leaves while one player is online (unless an option says otherwise).
• The jobs of a streamer who is offline wait for them, 15 minutes at most; past that, they are dropped.
• Effects around a streamer keep away from the other players (15 tiles by default) and from the safehouses the streamer may not enter.

Troubleshooting