Scene Entrance/Exit Tracker
Track character presence, entrances, exits, first and last scenes, and scene-to-scene transitions in story outlines.
The problem it solves
Scene Entrance/Exit Tracker [](https://github.com/loganpendragonmultiverse/scene-entrance-exit-tracker/actions/workflows/ci.yml)
Who Scene Entrance/Exit Tracker is for
- People who need a small, purpose-built utility instead of a broad platform.
- Users working with writing, scenes, characters who want the documented v1.1.0 behavior.
- People who prefer an open-source release with visible limitations, source, and license terms.
Intended result
Track character presence, entrances, exits, first and last scenes, and scene-to-scene transitions in story outlines.
This summary is reconciled from the current catalog and repository documentation.
Features in v1.1.0
Capabilities below come from the current project README and release documentation.
[](https://github.com/loganpendragonmultiverse/scene-entrance-exit-tracker/actions/workflows/ci.yml)
Build a scene-by-scene character presence matrix and explicit entrance and exit transitions. The command runs locally, uses explicit UTF-8 JSON input, and produces deterministic JSON or Markdown reports without modifying the supplied source material.
Verified examples
Screenshots are shown only when the current README references a local source image. Otherwise, repository example files are linked directly.
Platforms and implementation
The public release claims only the cataloged platforms and technologies.
Supported platforms
- Windows
- macOS
- Linux
Built with
- Python
Quick start
The shortest documented path into the current release.
python -m pip install .
scene-presence examples/sample.json
scene-presence examples/sample.json --format json --output report.jsonThe example documents the complete input shape. Version 1.1 adds per-character scene/transition summaries, a total transition count, and explicit warnings for empty scene rosters. Markdown is intended for immediate review; JSON preserves structured evidence for scripts and later comparison. An existing output file is never overwritten.
Current limitations
These boundaries are part of the product and prevent the page from implying unverified capability.
The tracker uses supplied scene rosters. It does not infer physical presence from prose or decide whether off-page characters count.
Privacy and licensing
Review the actual data boundary before using a tool with sensitive inputs.
Privacy and safety
All scene data stays local.
Python 3.10 or newer is supported on Windows, macOS, and Linux. The package has no runtime dependencies, telemetry, account, or hosted service.
License and release
Scene Entrance/Exit Tracker is published under MIT. The current cataloged release is v1.1.0, published 2026-07-27.
Related projects
Related projects are selected deterministically from shared catalog tags, category, and implementation technologies—not popularity or paid placement.
Scene Entrance/Exit Tracker v1.1.0
Use the tagged release for downloads and release notes. Use the repository for source, issues, contribution guidance, security reporting, and complete documentation.
Page source: current Forge catalog plus README and CHANGELOG from the canonical local repository. Fingerprint: 9402b229471a9616.