Skip to main content

Screen Stocks Python Bridge

The screenstocks-bridge package is a Python client for the local API exposed by the Screen Stocks Bridge BepInEx plugin. It requires the plugin to be installed in the game and the game to be running. The package itself does not install or contact the game backend; it connects to the plugin on loopback.

Install

python -m pip install screenstocks-bridge

Install the matching BepInEx plugin from the GitHub releases, then launch Screen Stocks. The default bridge address is 127.0.0.1:48721. The plugin port can be changed under [Bridge] as Port in BepInEx/config/screenstocks.bridge.cfg; close and relaunch the game after editing it. Pass the same value to BridgeClient(port=...) when it differs from the default. The example scripts also read SCREENSTOCKS_PORT. Read the token from BepInEx/config/screenstocks.bridge.cfg or the BepInEx log.

Connect

from screenstocks_bridge import BridgeClient

with BridgeClient(token="YOUR_TOKEN") as bridge:
    state = bridge.snapshot()
    print(state["ready"], state["cash"])
    print(bridge.upgrades())

The client supports state reads, activity reads and subscriptions, explicit single-stock activity-focus controls, trades, upgrade purchases, and auto-action controls. Activity focus can be set with set_human_activity_focus(stock_id) and cleared with clear_human_activity_focus(); the in-game overlay shows the active stock, and bridge-driven focus changes have a five-second minimum. See the bridge usage guide for the full API and its online behavior. Activity history reads page through only the samples the game currently retains in memory; they do not fetch older history from the game's server, and the bridge makes no guarantee about the retained history's total depth or time span.

Use offline_summary() to read the latest welcome-back summary captured during the current game session. The plugin captures it in memory before automatically closing the screen; set AutoCloseOfflineSummary = false in the BepInEx config to leave the screen open while retaining API access.

Metadata

Release files for screenstocks-bridge 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for screenstocks-bridge 0.4.0
File Size Uploaded Provenance Actions
screenstocks_bridge-0.4.0.tar.gz 9.5 kB With provenance Details for screenstocks_bridge-0.4.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for screenstocks-bridge 0.4.0
File Interpreter ABI Platform Actions
screenstocks_bridge-0.4.0-py3-none-any.whl Python 3 none any Details for screenstocks_bridge-0.4.0-py3-none-any.whl

Total release size: 18.9 kB

Release files / screenstocks_bridge-0.4.0.tar.gz

Download URL screenstocks_bridge-0.4.0.tar.gz
Size 9.5 kB
Tags Source
SHA-256 checksum
How to use checksums
0e5b41798c48fc51c6cf96f1bae3d6738ee5d8bf20e1d09f659dfb2fec77e3d3
BLAKE2b-256 checksum
How to use checksums
33dc2b84fd8aad650137352350abda3567b9e9cde96d645b4112ece1d596d5db
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.

Transparency log

Release files / screenstocks_bridge-0.4.0-py3-none-any.whl

Download URL screenstocks_bridge-0.4.0-py3-none-any.whl
Size 9.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2d083c1ee0c3c2e5ee58e8c9b0fd945c5b1de6b22cd9dbde48767f725d91255d
BLAKE2b-256 checksum
How to use checksums
377289bba9f79980b66f0dd37d7c3c887e6d7daad8a3fc4131c484adcc4be3c9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.

Transparency log

Security for screenstocks-bridge 0.4.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for screenstocks_bridge-0.4.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page