RPGJS Studio
Choose a playable world, customize maps and events visually, then press Play. Start free in your browser and export your RPGJS source.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證The installation website for the Midnight Club 3: Dub Edition port
翻譯準備中
正在載入完整 README。
檢視完整 README ↗A static web page that provides a guided experience to build the Nintendo Switch package of mcdub3-nx from the player's own copy of Midnight Club 3: DUB Edition or DUB Edition Remix (USA and Europe each). The player picks a disc image (Redump or XISO) or an extracted folder, and the page:
reads the disc's file system in the browser (lib/xdvdfs.js, a port of the toolkit's tools/xiso);
checks default.xbe the way the game does at boot (size + FNV-1a 64, lib/xbe.js) to tell the edition;
streams a zip named after the edition's NRO to the downloads folder (worker.js + lib/zip.js, served by
sw.js). Each game is its own app on the SD card:
switch/mcdub3-nx/mcdub3-nx-<usa|eur>.nro DUB Edition
switch/mcdub3-nx/mcdub3_env.example.txt
switch/mcdub3-nx/game/ or game-eur/ the disc
switch/mcdub3remix-nx/mcdub3remix-nx-<usa|eur>.nro DUB Edition Remix
switch/mcdub3remix-nx/mcdub3remix_env.example.txt
switch/mcdub3remix-nx/game-usa/ or game-eur/ the disc
Each NRO looks for its disc in game-<edition>/ first, then in game/, so editions and games can share one SD
card.
scripts/fetch-release.sh # stages the latest release into release/ and writes release/manifest.json (needs gh, jq)
python3 -m http.server 8000 # then open http://localhost:8000
Service workers need localhost or HTTPS, so opening index.html as a file does not work.
.github/workflows/pages.yml publishes the site on GitHub Pages (Settings > Pages > Source: GitHub Actions). It
runs on every push to main, by hand, on a mcdub3-release repository dispatch, and hourly; the hourly run deploys
only when the latest release isn't the one the live site serves, so a new release is live within the hour. Each
deploy copies the release's NROs into release/: GitHub's API allows browsers, but the release files themselves
come from a host without CORS headers, so the page can't fetch them itself.
To redeploy right after a release, the game's release workflow can send the dispatch (with a token that can write to this repository):
gh api repos/<owner>/<this-repo>/dispatches -f event_type=mcdub3-release
release/editions.json lists every edition the page knows, per game: the xbe_size and xbe_fnv64 of its
default.xbe, its NRO, where it installs (install_dir, game_dir), the name of its settings template, its cover,
and where mcdub3-nx lists its XBE (xbe_lists, newest layout first: config/<game>/xbe_editions.h, then the older
paths; xbe_id is its name there).
scripts/fetch-release.sh writes the release/manifest.json the page reads (generated, not committed), marking each
edition released when the release has its NRO. The page packages only released editions; a disc of another known
edition is recognised and told its build is not in the release yet. So a new edition becomes installable with the
first release that has its build. The script refuses to deploy a released edition whose hash that release's game
does not accept.
img/background.jpg is the source of img/background.webp, cropped below the artwork's own logo:
magick img/background.jpg -crop 1200x655+0+305 +repage png:- | cwebp -q 82 -o img/background.webp -- -