# ReelGrove

> Independent development tools for studios building slot games for Engine (engine.io), also known as Stake Engine. Existing-project imports, preserved Lab work across builds, scoped CI uploads, Art, Sound, Motion and Animation Labs, test-credit previews, exact saved outcomes, studio release reviews and portable exports.

ReelGrove is operated by Mac Graver sp. z o.o. and is independent of Stake and Engine. Engine here is the game-development platform, separate from the Engine.IO networking library used by Socket.IO. Studios submit games through their own Engine accounts; ReelGrove does not grant submission approval. Previews use simulated credits without deposits, withdrawals or redemption. Source editing uses your local tools. Hosted math experiments and isolated browser observations require enabled workers; tool discovery alone does not confirm availability.

The Markdown pages below are generated from the same public HTML shown to visitors. Private account, studio and project content is excluded. Pricing and feature availability are described in the current product pages.

## Product and guides

- [Stake Engine development tools](https://reelgrove.net/stake-engine-tools/index.md): Product fit, supported workflow, AI agents, common questions and plan details.
- [ReelGrove overview](https://reelgrove.net/index.md): Creative Labs, product demonstrations, math and frontend reports, collaboration and pricing.
- [Getting started](https://reelgrove.net/docs/getting-started/index.md): Create a project, replace artwork and sound, animate rigs with keyable tint and flash-to-white colour and sprite blend modes, bind exact saved rigs to declared game events, preview, review, export and copy saved work where cloning is enabled.
- [Existing Engine games](https://reelgrove.net/docs/existing-games/index.md): Prepare an independent game, validate and activate later builds, create or copy projects through scoped tools, find exact published or generated outcomes, archive saved expectations, expand complete profile matrices, inspect readiness evidence and recover editable work. Imported history grants no new approval. Native build receipts distinguish one observed execution from two matching normalized runs.
- [MCP guide](https://reelgrove.net/docs/mcp/index.md): Connect compatible AI assistants through 122 project tools for scoped creative work, QA archival, complete profile matrices, readiness assessment, verified exports, project creation, restoration, cloning, reviewed kit installation and exact native math evidence.
- [Downloads](https://reelgrove.net/downloads/index.md): Verified bundlepack and studioctl binaries for packaging, CI uploads, portable recovery, reusable kits, local Chromium replay with its runtime and source packages, and math experiments, with read-only hosted build receipt CLI examples.
- [Combined public documentation](https://reelgrove.net/llms-full.txt): All product and guide pages as one readable text document.

## Optional

- [Support and contact](https://reelgrove.net/support/): Product support and operator details.
- [Terms](https://reelgrove.net/terms/): Service and project-use terms.
- [Privacy](https://reelgrove.net/privacy/): Personal data and cookie information.

- [Scoped new owned-project creation](https://reelgrove.net/docs/mcp/#new-project) and [CLI workflow](https://reelgrove.net/downloads/#new-project). Seven tools use an existing project key as a fixed authorization anchor, reserve a distinct destination, and require explicit validation and registration. No destination key is delegated; later automated editing needs a separately issued key.

- [Saved QA archival](https://reelgrove.net/docs/existing-games/#qa-history), [scoped archive tools](https://reelgrove.net/docs/mcp/#qa-history) and [CLI access](https://reelgrove.net/downloads/#qa-history). Active/archived views preserve exact evidence and separate working capacity from retained storage.

- [Scoped portable restoration](https://reelgrove.net/docs/mcp/#project-restoration) and [explicit CLI plan review](https://reelgrove.net/downloads/#machine-restoration). Five tools restore a validated creation admission into its reserved destination with an explicit plan digest. Original-key effects, same-actor read recovery and no destination-key delegation.

- [Scoped project cloning](https://reelgrove.net/docs/mcp/#project-cloning) and [durable CLI copies](https://reelgrove.net/downloads/#machine-cloning). Five tools preserve the original captured source and reserved destination across exact retries. Original-key create/import/export authority controls new effects; replacement read recovery never delegates a destination key.

- [Native animation file commands](https://reelgrove.net/downloads/#animation-files) and [local build checks](https://reelgrove.net/downloads/#development-checks). Transfer native animation files up to 24 MiB with a project key while inline MCP retains its 4 MiB limit. Prepare seekable books, check preview disk requirements and validate tile assets with the matching tools and preview worker. Storage and preflight results do not establish playability.