Load Quest Data

SkillAI & models

Loads quest definitions from GRADIENTBANGQUESTDATADIR (data/quests/ by default) into Supabase.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Load Quest Data skill

About this capability

Gradient Bang is an online multiplayer universe where you explore, trade, battle, and collaborate with other players and with LLMs

What this skill tells your AI

The instructions your AI receives, as published by pipecat-ai/gradient-bang in .claude/skills/load-quests/SKILL.md and read by ahel’s review.

Loads quest definitions from GRADIENTBANG_QUEST_DATA_DIR (data/quests/ by default) into Supabase.

Ask the user for:

set -a && source .env.supabase && set +a

Upsert mode (default — updates existing quests, inserts new ones):

uv run -m gradientbang.scripts.load_quests_to_supabase

Force mode (wipes all quest definitions and reloads from scratch):

uv run -m gradientbang.scripts.load_quests_to_supabase --force

Dry run (validate JSON files without writing to database):

uv run -m gradientbang.scripts.load_quests_to_supabase --dry-run

Confirm the output shows "Success!" and check the stats summary for expected quest/step/subscription counts.

Each .json file in GRADIENTBANG_QUEST_DATA_DIR represents one quest chain. The loader picks up all *.json files in the directory.
The loader upserts by quest code, so it's safe to re-run after editing quest data.
--force deletes ALL quest definitions (cascades to steps and subscriptions) before reloading. Player quest progress (player_quests, player_quest_steps) is NOT affected — but orphaned progress rows will reference deleted step IDs.
If you get a PostgREST schema cache error, run: docker exec supabase_db_gb-world-server psql -U postgres -d postgres -c "NOTIFY pgrst, 'reload schema'" then retry.

Advanced