Outer Wilds Mod Database
Uses the mod list in mods.json of the source branch, fetches the required data for each mod. That data is then added to database.json in the master branch. The process happens automatically every once in a while.
Click here to add your mod to the database
Or, if you want, you can edit the mod list yourself and open a PR
How it works
GitHub Actions are used to periodically update the database. Check the Update Releases workflow and the TypeScript code that fetches the data about each mod and generates the database.
Repository secrets
If you fork this repository, you'll need to add a few secrets for everything to work.
GH_TOKEN
GitHub token with repo permissions. Format:
ghp_XXX
DISCORD_HOOK_URL
Discord web hook URL where all the notifications are sent. Format:
https://discord.com/api/webhooks/XXX/YYY
DISCORD_MOD_HOOK_URLS
JSON object where keys are the uniqueName of a mod, and the values are the Discord hook urls of the channel where update notifications should be sent to. Format:
{
"uniqueNameA": "https://discord.com/api/webhooks/XXX/YYY",
"uniqueNameB": "https://discord.com/api/webhooks/WWW/ZZZ"
}DISCORD_MOD_UPDATE_ROLE_ID
ID for the Discord role to ping when there's a mod update.
DISCORD_NEW_MOD_ROLE_ID
ID for the Discord role to ping when there's a new mod added to the database.
GOOGLE_SERVICE_ACCOUNT
Base64-encoded JSON object. Credentials of a Google service account with permissions to get the outerwildsmods.com view counts from google analytics. JSON format (before base64 encoding):
{
"type": "service_account",
"project_id": "XXX",
"private_key_id": "XXX",
"private_key": "XXX",
"client_email": "XXX",
"client_id": "XXX",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://oauth2.googleapis.com/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_x509_cert_url": "XXX"
}