Admin

Loading builds...

Add a Companion

New companions added to the game can be registered here so they appear as selectable options for Martial Artist in the Build Editor.

Name

Gender

Portrait Image URL

Paste the image URL ending in .png or .jpg. If you copied it from Fandom and it has /revision/latest?cb=... at the end, that's fine — it's stripped automatically.

Weapon Mastery

Tick every weapon (and Lightness / Cultivation) this companion can use. This only affects which checkboxes start ticked for them in Character Config — it isn't wired into the Build Editor's restriction logic anywhere else yet.

Custom weapon

Current Companions

Character Configuration

Select a character to configure which weapons, equipment, and skills are available to them in the Build Editor. Checked items are allowed; unchecked items are hidden. After making changes, click Save Character — no redeploy needed.

Loading characters…

How the Site Works

Wandering Sword Builds is a fan-made build-sharing tool hosted on Cloudflare Pages with a D1 SQLite database on the backend. All builds, reactions, companions, and game-data flags are stored in D1. Static game data (the full skill, weapon, and equipment lists) lives in the public/assets/ JSON files shipped with the deployment. The admin panel controls which of those items are visible to users.

Moderation Tab — Edit & Delete

Every build submitted to the site appears in the Moderation list. Each row shows the build title, disciple name, martial artist, weapon path, and submission date.

View Opens the public Reaction Scroll for that build in a new tab. Use this to read the full build before deciding to keep or remove it.
Edit Opens the Build Editor pre-filled with that build's data. The URL includes both the build ID and the admin key so the editor's save button performs an admin update (bypassing the usual edit-token check). Any admin can edit any build — there is no ownership restriction from this panel.
Delete Permanently deletes the build from the database including all its skills and reactions. A confirmation dialog appears first. This cannot be undone.

Deleting a build is irreversible. There is no recycle bin or soft-delete. Always use View first to confirm you have the right build.

Companions Tab

The initial companion roster is seeded from public/assets/companions.json and is part of the deployed build. To add a companion that was patched into the game after the last deployment, use the Add a Companion form here — no redeploy needed. These admin-added companions are stored in the admin_companions D1 table and merged with the seeded list at runtime.

To remove a companion added via this panel, click Remove on their card. Seeded companions (from the JSON file) cannot be removed from this panel — they require a code change and redeploy.

Character Config Tab

The Character Config tab lets you configure which weapons, equipment pieces, and skills are available to each character in the Build Editor. Select a character from the ribbon at the top, then switch between the category tabs (Weapon, Headgear, Garment, Shoes, Accessory, Skills) to see and toggle individual items.

Checked items are allowed — they appear in the Build Editor dropdowns for that character. Unchecked items are hidden. By default (before any restriction is saved) all items are allowed.

Click Save Character after making changes. Only the currently displayed character is saved — switch to another character and save again if you need to update multiple characters in the same session. Changes are stored per-character in the database and take effect immediately on the next page load of the Build Editor.

Adding New Skills or Equipment (Patch Updates)

When a game patch adds new skills, weapons, or equipment pieces, they need to be added manually to the static JSON files before they appear in the editor:

public/assets/skills.json — all learnable skills
public/assets/weapons.json — all weapon items
public/assets/equipment.json — headgear, garments, shoes, accessories

Each entry needs at minimum a unique id, a name, and a category matching the existing values. After editing the JSON and redeploying, new items appear in all characters' allowed lists by default. You can then use the Character Config tab to restrict which characters have access to specific new items.

Reactions

Reactions (heart, fire, thumbs-up) are counted server-side using the build_reactions table. Each reaction is tied to an anonymous client ID (a UUID stored in the browser's localStorage) and the build ID, with a unique constraint on the combination — so one client gets one vote per reaction type per build. Reaction counts cannot be manipulated client-side.

Build Ownership and the Edit Token

There are no user accounts. "Owning" a build means knowing its edit token — a private UUID generated when the build is first saved and shown only once in the redirect URL. Anyone with that token URL can edit the build. The admin panel bypasses the token check entirely, so admins can edit any build without needing the creator's token.

Deployment

The site deploys to Cloudflare Pages via Wrangler. To deploy, run npx wrangler pages deploy public from the project root. Database migrations in migrations/ must be applied manually to the D1 database using the Wrangler CLI when a new migration is added.

Admin Access