Game Graveyard
Game Graveyard keeps intentionally abandoned games out of an active backlog without erasing the decision.
The problem it solves
Game Graveyard Game Graveyard keeps intentionally abandoned games out of an active backlog without erasing the decision. A portable JSON record can retain the platform, attempts, approximate playtime, reason category, explanation, abandonment date, and an optional reconsideration date.
Who Game Graveyard is for
- Players who want practical, local tools for libraries, saves, settings, or planning.
- Users working with gaming, backlog, abandoned games who want the documented v1.1.0 behavior.
- People who prefer an open-source release with visible limitations, source, and license terms.
Intended result
Game Graveyard keeps intentionally abandoned games out of an active backlog without erasing the decision.
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.
Game Graveyard keeps intentionally abandoned games out of an active backlog without erasing the decision. A portable JSON record can retain the platform, attempts, approximate playtime, reason category, explanation, abandonment date, and an optional reconsideration date.
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
What changed in v1.1.0
Add reversible dated decisions, explicit reconsideration views and local CSV/backlog interchange while preserving original abandonment reasons.
game-graveyard examples/graveyard.json --as-of 2026-09-07 --format jsonUse --decision abandoned|reconsidering|returned with --game-id, --date, --decision-note and --decision-output new.json. --undo-last appends a reversal instead of deleting history. Dates must remain ordered and original abandonment reasons are preserved. --as-of evaluates decision state and due reconsideration dates without scheduling reminders. CSV input/output carries documented fields and JSON history; unsupported extra columns are rejected. --format backlog creates a randomizer-compatible JSON with original graveyard_record metadata for re-import. Ownership is unknown and defaults false, so review backlog rules before drawing. Generic backlog records without authored abandonment metadata are rejected. No storefront login or notification is performed.
Changelog
Release notes from the canonical v1.1.0 source tag.
- Add reversible dated decisions, explicit reconsideration views and local CSV/backlog interchange while preserving original abandonment reasons.
- Added regression coverage for the audited behavior and invalid inputs.
- Added validated abandoned-game records and reason categories.
- Added reason filtering, reconsideration visibility, and aggregate summaries.
- Added Markdown and JSON reports with safe output handling.
Quick start
The shortest documented path into the current release.
Before running these source commands, download the v1.1.0 source archive, extract it, and open a terminal in the extracted project folder containing README.md. Follow the tagged README for required runtimes and any platform-specific setup.
python -m pip install .
game-graveyard examples/graveyard.json
game-graveyard examples/graveyard.json --reason technical --format jsonReports summarize entries by reason and platform, list scheduled reconsiderations separately, and support Markdown or JSON output. Existing report files are refused.
The tool does not import platform libraries, judge whether a game is good, or calculate playtime. The owner supplies every record and can choose deliberately broad notes for privacy. Requires Python 3.10 or newer.
Part of the Logan Pendragon Forge open-source collection. Licensed under the MIT License.
Current limitations
These boundaries are part of the product and prevent the page from implying unverified capability.
The current v1.1.0 release is bounded by the behavior documented in its README and changelog. It does not claim unsupported platforms, automatic interpretation, or results beyond the evidence it produces.
Privacy and licensing
Review the actual data boundary before using a tool with sensitive inputs.
Privacy and safety
No privacy behavior beyond the current repository documentation is claimed. Review the source, security policy, and input/output behavior before using sensitive material.
License and release
Game Graveyard is published under MIT. The current cataloged release is v1.1.0, published 2026-09-07.
Related projects
Related projects are selected deterministically from shared catalog tags, category, and implementation technologies—not popularity or paid placement.
Game Graveyard 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 GitHub release tag. Fingerprint: 6600c46ffeab44e9.