Threadbare

A story-driven, collaborative game where players don’t just explore a world—they co-create it. In Threadbare, players rebuild a world unraveling at the seams by recovering knowledge, crafting stories, and designing characters, quests, and cultures drawn from their own lives.

Threadbare is currently in pre-alpha and being used in select learning programs as a scaffolded learning experience. Learners create non-canon StoryQuests that live alongside the canon narrative. In the future, contributors will be able to contribute canon LoreQuests to the core narrative of Threadbare.

Play the current pre-alpha release of Threadbare, or play development versions. New pre-alpha releases are published every 2–3 weeks.

Help Build Threadbare!

Threadbare is open source! We invite interested learners, educators, or game developers to follow along with its development and get involved where possible. The core team determines the overall game design and direction (ensuring it serves both players and learners), but anyone can join the community to find a place to help out:

Share playtest feedback
Ask and answer questions
Browse good first issues to find something to tackle
Join our Discord to discuss the project with the team in real-time

Threadbare's code, comments, and development discussion are written in English. If English is not your first language, don't worry: it's not the first language for about half of the core team at Endless Access either, and we will be happy to hear from you.

(We hope to add translations for the game itself in the medium term.)

Getting the Source Code

Threadbare uses Git Large File Storage (LFS) to store large assets, such as music and artwork. You must install and configure Git LFS before you clone the Threadbare repository.

License

Threadbare's original source code in Threadbare itself is covered by Mozilla Public License Version 2.0.

Threadbare's original assets are covered by Creative Commons Attribution-ShareAlike 4.0 International.

Threadbare includes third-party assets and addons that are covered by different licenses. Using the REUSE specification, all files in the repository are labelled with their license in a machine-readable way, through a combination of comments in the files themselves, supplementary .license files, and REUSE.toml.

Name		Name	Last commit message	Last commit date
.github		.github
LICENSES		LICENSES

Latest commit

History

Folders and files