Skip to main content

OSRS Bot Development SDK with game-native structure

Project description

ShadowLib

A Python SDK for Old School RuneScape (OSRS) bot development with an intuitive structure that mirrors the game's interface.

Features

  • Game-Native Structure: Directory layout based on OSRS client interface (world, tabs, interfaces)
  • Type-Safe: Full type hints for better IDE support and fewer runtime errors
  • Well-Tested: Comprehensive test coverage with pytest
  • Clean Code: Enforced coding standards with Ruff and custom naming convention checker
  • Easy to Use: Intuitive API that matches how players think about the game

Installation

From Source

git clone https://github.com/shadowbot/shadowlib.git
cd shadowlib
pip install -e ".[dev]"

For Development

# Install with development dependencies
pip install -e ".[dev]"

# Install pre-commit hooks
pre-commit install

Quick Start

from shadowlib import Client

# Create and connect to the client
client = Client()
client.connect()

# Check connection status
if client.isConnected():
    print("Connected to OSRS client!")

# Your bot logic here...

# Disconnect when done
client.disconnect()

Project Structure

shadowlib/
├── world/              # Game viewport entities (NPCs, objects, players, ground items)
├── tabs/               # Side panel tabs (inventory, equipment, skills, prayers)
├── interfaces/         # Overlay windows (bank, GE, shop, dialogue)
├── navigation/         # Movement systems (walking, teleports, webwalking)
├── interactions/       # Interaction systems (menu, clicking, hovering)
├── input/              # OS-level input (mouse, keyboard)
├── types/              # Type definitions, enums, models
├── utilities/          # Helper functions (timing, calculations, geometry)
├── resources/          # Game data (varps, objects, items, NPCs)
└── _internal/          # Bridge implementation (transport, protocol, cache)

Placement Rules

  1. Visible in the 3D worldworld/
  2. Side-panel tabtabs/
  3. Overlay windowinterfaces/
  4. Pathing/movementnavigation/
  5. Interaction primitivesinteractions/

Development

Code Style

This project uses camelCase for function names (e.g., getFoo(), doSomething()), following the convention:

# ✅ Correct
def getPlayerName():
    pass

def isInventoryFull():
    pass

# ❌ Incorrect
def get_player_name():
    pass

def is_inventory_full():
    pass

Running Tests

# Run all tests
pytest

# Run with coverage
pytest --cov=shadowlib

# Run specific test file
pytest tests/test_client.py

# Run tests matching a pattern
pytest -k "test_client"

Linting and Formatting

# Run Ruff linter
ruff check .

# Auto-fix issues
ruff check --fix .

# Format code
ruff format .

# Check naming conventions
python check_naming.py

Pre-commit Hooks

The project uses pre-commit hooks to ensure code quality:

# Install hooks
pre-commit install

# Run manually
pre-commit run --all-files

Naming Conventions

  • Functions/Methods: camelCase (e.g., getItem, moveToPosition)
  • Classes: PascalCase (e.g., Client, QueryBuilder)
  • Constants: UPPER_CASE (e.g., MAX_HEALTH, DEFAULT_TIMEOUT)
  • Private functions: _camelCase (e.g., _internalHelper)
  • Dunder methods: __method__ (e.g., __init__, __repr__)

Contributing

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/amazing-feature)
  3. Make your changes following the code style
  4. Run tests and linting
  5. Commit your changes (git commit -m 'Add amazing feature')
  6. Push to the branch (git push origin feature/amazing-feature)
  7. Open a Pull Request

Code Quality Checklist

Before submitting a PR, ensure:

  • All tests pass (pytest)
  • Code follows naming conventions (python check_naming.py)
  • Linting passes (ruff check .)
  • Code is formatted (ruff format .)
  • New features have tests
  • Documentation is updated

Architecture Decision Records (ADRs)

See docs/adr/ for architectural decisions, including:

  • ADR-003: OSRS-Native SDK Structure

License

MIT License - see LICENSE file for details

Acknowledgments

  • Inspired by OSBot, TRiBot, and other OSRS botting frameworks
  • Built with love for the OSRS botting community

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

shadowlib-2.2.1.tar.gz (140.6 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

shadowlib-2.2.1-py3-none-any.whl (164.8 kB view details)

Uploaded Python 3

File details

Details for the file shadowlib-2.2.1.tar.gz.

File metadata

  • Download URL: shadowlib-2.2.1.tar.gz
  • Upload date:
  • Size: 140.6 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.12

File hashes

Hashes for shadowlib-2.2.1.tar.gz
Algorithm Hash digest
SHA256 e0a9f7ca5ee42291ad20ab3d169d8881d9a137bb4c42d9838fe88342b2ff6573
MD5 58512feeb0a8b9da7e134b6b25093edb
BLAKE2b-256 4da5d0c6c29e48c42fae08fe83ad6e59688e2cae5a3449ab480945efe5440b93

See more details on using hashes here.

File details

Details for the file shadowlib-2.2.1-py3-none-any.whl.

File metadata

  • Download URL: shadowlib-2.2.1-py3-none-any.whl
  • Upload date:
  • Size: 164.8 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.12

File hashes

Hashes for shadowlib-2.2.1-py3-none-any.whl
Algorithm Hash digest
SHA256 7895b2990c000a71155c2d59261521ada4f869b2fe3b9f7317de59f0962dbf73
MD5 3015733ffeea531088d2f32856b61ab9
BLAKE2b-256 626ba59b2f1b5398843e468ca383d40e7eb728fe5f5f413c2c173c01066209ba

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page