Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Library:PlayCanvas

From ReverseEngineering.wiki
Library
On this wiki Facts · Code · Notes · Topics

PlayCanvas engine (MIT): open-source WebGL/WebGPU runtime of the PlayCanvas web editor; build/playcanvas.js exposes the global pc.

PlayCanvas is an MIT-licensed JavaScript game engine (playcanvas/engine) and a hosted editor that exports projects as web builds.

Identification

  • package.json main is build/playcanvas.js; source version at the pinned commit is 2.24.0-beta.15. The UMD build is created with globalName 'pc' (utils/esbuild-build-target.mjs; the wrapper is factory(global.pc = {})), so the global is pc, and src/index.js re-exports version and revision from src/core/core.js, giving pc.version and pc.revision (core.js holds the placeholders '$_CURRENT_SDK_VERSION' and '$_CURRENT_SDK_REVISION' that the build replaces; the revision is the short git hash). Application start also logs 'Powered by PlayCanvas <version> <revision>' (src/framework/app-base.js) when the version string has been substituted.
  • Unverified: editor-exported builds contain config.json, scene JSON files and a __start__.js with a __settings__.js beside the engine script; check a real export before relying on this.

See Technique:Identifying HTML5 game engines.

Code & repositories

  • https://github.com/playcanvas/engine @ 40854828f51deaf53221093403114e9490e8da04 · license: MIT (read from LICENSE; GitHub's API was busy)
    PlayCanvas engine (MIT): package.json main build/playcanvas.js.
    Tested on: source read, not run: source read, not run · checked 2026-10-18