BeamNG.Earth
A 1:1 scale streamed Earth for BeamNG.drive: real elevation and satellite imagery, floating origin, LOD streaming from a companion server
Metagame analytics, an Elo leaderboard, and decklist validation for the Planar Standard format.
GamesTypeScript · PLpgSQLGitHub @PlanarStandardMTGOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Community site for the Magic: The Gathering format Planar Standard.
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
A community site for the Magic: The Gathering format Planar Standard.
Full context lives in docs/ once copied in — see planar-standard-master-plan.md
and backlog.md for the plan this scaffold implements (start at epic E1).
Only the Discord webhook needs a real secret. Sign-in does not — local
Supabase takes an email and a password and catches its own mail — and neither
does anything else, including legality and metrics.
Dependencies point left only, enforced by pnpm depcruise — see
.dependency-cruiser.cjs.Read the full README ↗A community site for the Magic: The Gathering format Planar Standard.
Full context lives in docs/ once copied in — see planar-standard-master-plan.md
and backlog.md for the plan this scaffold implements (start at epic E1).
pnpm install
pnpm --filter @ps/core test # works immediately, zero setup
pnpm --filter @ps/adapters test # works immediately, zero setup
pnpm db:start # supabase start (local Docker)
pnpm db:reset # migrations + seed
pnpm dev # http://localhost:3000
Only the Discord webhook needs a real secret. Sign-in does not — local Supabase takes an email and a password and catches its own mail — and neither does anything else, including legality and metrics.
packages/
├── contracts/ types only, zero runtime dependencies
├── core/ pure functions, depends on contracts ONLY
├── adapters/ source parsers, depends on contracts + core
├── cards/ loads data/cards/ — the only package that reads a file
└── db/ schema, migrations, repositories
apps/
├── web/ Next.js app (scaffolded in E16)
└── jobs/ scheduled scripts, run by GitHub Actions
data/ data/sets.json (PR-reviewed) + data/cards/ (generated, E4)
content/pages/ MDX info pages
fixtures/ shared test fixtures
docs/adr/ architecture decision records
docs/modules/ one page per module
Dependencies point left only, enforced by pnpm depcruise — see
.dependency-cruiser.cjs.
This is the E1.1 workspace skeleton: empty packages that install, build, and test cleanly. Next up per the backlog: E1.2–E1.9 (strict TS config already included, project references, lint, CI already wired — remaining: module scaffold generator, fixtures conventions), then E2 (contracts).