Prism Plinko · Buyer Guide

1 Overview and package contents

Choose a bet in demo credits, a risk level and a board of 8, 12 or 16 rows, then press DROP. The ball falls through the pins and lands in a chute; your bet is multiplied by that chute.

A return smaller than your bet is a partial return, not a win.

Demo only. Credits have no value and cannot be bought, sold or withdrawn.

10 balls · Score as many points as you can

Land 3 balls at 2× or higher to earn one bonus ball worth double points.

Choose your ball and light all seven prism facets. Ball finishes are cosmetic and never change chances or credits.

2 Requirements and subfolder hosting

The game must be opened through a web address. Opening its index.html directly from your computer (file://) is not supported. This guide is the exception: it opens by double-clicking, with no internet connection.

• A current version of Chrome, Edge, Firefox or Safari on a computer, tablet or phone.
• Any subfolder of any domain. The game uses relative paths, so the same files work wherever you upload them.
• Nothing else on the server: no database, PHP or Node.js service is needed to play.

3 Quick installation by FTP

1. Extract prism-plinko-static-2.0.0.zip on your computer.
2. Connect to your hosting by FTP or its file manager, and open the folder where the game should live, for example public_html/games/prism-plinko/.
3. Upload only the contents of the game/ folder, so that index.html sits directly inside the target folder.
4. Open https://your-domain.example/games/prism-plinko/ in a modern browser.

4 Controls and how the game works

Space or Enter: drop (hold for more balls) · ↑ ↓: bet · M: sound

Faster drops. The results are exactly the same.

5 Screens and controls explained

1 2 3

Marks on the screenshot

1. 1 Free play
2. 2 Challenge
3. 3 Collection

1 2 3 4 5

Marks on the screenshot

1. 1 Balance
2. 2 Bet
3. 3 Risk
4. 4 Rows
5. 5 DROP

1

Marks on the screenshot

1. 1 Settings

6 Map of the files

game/
game/prism-plinko.config.json
source/src/
source/src/assets/
source/public/
source/tests/
source/dist/
documentation/index.html
THIRD-PARTY-LICENSES/

7 Customizing texts, images and content

Edit game/prism-plinko.config.json to set the language, starting credits, boards, audio and features. To preserve changes in future builds, edit the copy in source/public/. Replace the local images under source/public/art/ and the ball in source/src/assets/; edit translations in source/src/locales/. Multiplier tables are in source/src/logic/round.ts. Changes to source require a rebuild.

8 Languages and audio

The game interface is available in 14 languages: English, Português (Brasil), Español, Français, Deutsch, Italiano, Nederlands, Polski, Türkçe, Русский, Bahasa Indonesia, 日本語, 한국어 and 简体中文. The game follows the browser language when it can. Players can choose another language in Settings.

The game includes synthesized collision sounds and four short local sound effects. There is no background music or recorded narration. Audio begins after the first interaction, subject to browser settings.

9 Saves and taking care of progress

• Saves belong to one browser on one device. They do not synchronise between devices or browsers.
• Private browsing or blocked storage may prevent saving. The game keeps running for the current session.
• Clearing site data for the game's address deletes the save. Clearing cached images and files does not (see Updating and clearing the cache).

Clearing the cache without losing progress

Progress is stored in this browser, not on the server. Clearing cached images and files, or doing a hard reload, keeps your progress.

Computer: press Ctrl+F5 on Windows and Linux, or Cmd+Shift+R on macOS. Phone: in the browser settings, choose the option to clear cached images and files.

Do not choose cookies and site data, or clear site data, for the game's address. That deletes the local save.

10 Optional development

This section is only for changing the code. The game/ folder already contains the built game, so installing it needs no Node.js.

1. Install Node.js. Open https://nodejs.org/en/download and choose the latest Node.js 26 LTS installer for your system (minimum 26.13). npm is included. Internet is needed to download tools and dependencies, not to run a Node.js server for this game.

Windows: run the .msi installer, keep npm and Add to PATH enabled, finish installation and reopen Command Prompt. macOS: run the official .pkg installer and reopen Terminal. Linux: follow the official download page instructions for your distribution, including npm. No global Vite installation is needed.

2. Verify installation. Run the commands below separately. Both must print version numbers; Node.js must be 26.13 or newer. If a command is not found, reopen the terminal and check the installation/PATH.

node --version
npm --version

3. Extract the complete buyer ZIP first. Open its source folder, where package.json and package-lock.json are located. Windows: type cmd in that folder's File Explorer address bar. macOS/Linux: open Terminal and use cd with the actual folder path in quotes. Do not run commands inside the ZIP or game folder.

4. Install dependencies. Run npm ci inside source/. Wait for successful completion. It downloads the exact locked packages to node_modules, including TypeScript, Vite and the fonts. Keep package-lock.json. Do not use --omit=dev: the build needs development dependencies. Never upload node_modules.

5. Check the source. Run npm test; the supplied version has 124 tests. Then run npm run typecheck. Stop and resolve errors before building. These commands do not publish anything.

6. Build the game. Run npm run build and wait for successful completion. It checks TypeScript and runs Vite. Output is source/dist/, containing index.html, modules/, assets/, audio/ and licenses/. Open prism-plinko.config.json there to confirm your branding configuration.

npm ci
npm test
npm run typecheck
npm run build
npm run preview

8. Publish the result. Back up your hosted game, then upload all contents of dist/ to your game's web folder, keeping relative paths. Do not upload the enclosing folder, source/, node_modules or the ZIP. Open the public HTTPS URL and refresh the browser cache. Rebuild and replace the complete output after source changes.

Troubleshooting: ENOENT/package.json means the terminal is in the wrong folder. EBADENGINE means Node.js is too old. If PowerShell blocks npm.ps1, use npm.cmd or Command Prompt; do not change security policy. For network/proxy errors, restore access to registry.npmjs.org and retry npm ci. If package files disagree, restore the shipped pair; npm install is for deliberate dependency changes, followed by tests/build and retaining the updated lockfile. Do not run npm audit fix --force blindly. The ready-built game/ remains usable without these developer tools.

11 Common problems

• Blank page: make sure you uploaded the contents of game/ (not source/, and not the folder itself), and that you opened the web address rather than a file on your computer.
• Missing images or sounds: check the complete upload, the spelling and letter case of file names, and any 404 errors in the browser's console.
• The files download or do not run: your host must serve .js, .webp, .woff2 and .mp3 files with normal types. Ask the host to check its MIME rules.
• Changes do not appear: reload the game after uploading the config or images. Follow the cache section if the old version remains.

12 Support and version history

Support and customization: willian@polargames.com.br. Include your purchase reference when you have it. This guide does not promise response times or a schedule of future updates.

Support request

When you write to support, include the browser and device, the game version, the page address, the steps that caused the problem, a screenshot and the first error shown in the browser console. Never send passwords, payment details or secret keys.