Skip to main content

Steam Scheduled Download Killer pipeline-badge

This tool makes it possible to set the auto-update behavior for all installed Steam games found in specified Steam Library Folders. This is done by setting the value for the AutoUpdateBehavior key found in the appmanifest of each installed games to a specified value. For more details see usage of entry point ssdk.

This tool also provides a second entry point ssdk-lib for writing, removing, adding and listing all Steam Library Folder(s) whose games are affected by the main tool.

Installation

Install using pip:

pip install steam-scheduled-download-killer

Recommended install using pipx

pipx install steam-scheduled-download-killer

Entry Point: ssdk

usage: ssdk [-h] [-c CONFIG] [--update-priority PRIO]

Ensure all Steam Games have high priority auto updates.
Manage Steam Library Folder(s) with entry point 'ssdk-lib'

optional arguments:
  -h, --help                  show this help message and exit
  -c CONFIG, --config CONFIG  path to config file containing Steam Library Folder(s)
  --update-priority PRIO      value the update priority should be set to (default: 2)

priority values:
  0                           always keep this game updated
  1                           only update this game when I launch it
  2                           high priority - always auto-update this game before others

NOTE: If you want to run the programm without a console window opening (e.g. when running from Task Scheduler) use the ssdk-background executable. It behaves the same as the ssdk entry point described above.

Entry Point: ssdk-lib

usage: ssdk-lib [-h] [-c CONFIG] [--ignore-existing] COMMAND [LIBRARY ...]

Manage file listing Steam Library Folders.
Use 'ssdk' entry point for managing Steam Applications.

positional arguments:
  COMMAND                     action to be executed (see allowed commands for details)   
  LIBRARY                     path(s) to Steam Library Folders (not needed for 'list')   

optional arguments:
  -h, --help                  show this help message and exit
  -c CONFIG, --config CONFIG  path to config file containing Steam Library Folder(s)     
  --ignore-existing           set this to overwrite existing file for 'make' command     

allowed commands:
  make                        create a config file with all given Steam Library Folder(s)
  list                        show a list of all Steam Library Folder(s)
  rm                          remove the given Steam Library Folder(s) from config file  
  add                         add given Steam Library Folder(s) to config file

Metadata

Release files for steam-scheduled-download-killer 0.0.3

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

Source distribution (sdist)

Source distribution for steam-scheduled-download-killer 0.0.3
File Size Uploaded Provenance Actions
steam-scheduled-download-killer-0.0.3.tar.gz 14.3 kB Without provenance Details for steam-scheduled-download-killer-0.0.3.tar.gz

Release files / steam-scheduled-download-killer-0.0.3.tar.gz

Download URL steam-scheduled-download-killer-0.0.3.tar.gz
Size 14.3 kB
Tags Source
SHA-256 checksum
How to use checksums
454fc0418f014c4b5f51b7742cfd212d462cdf1580676c55937ba926eea7d003
BLAKE2b-256 checksum
How to use checksums
5222ccfba341907bbfb0eb96718562a01f81ff7ac64fd36d31cf81d3cc855fc2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7

Security for steam-scheduled-download-killer 0.0.3

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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.

Release history Release notifications | RSS feed

This release

0.0.3 This release

1 release file No provenance

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