Simple recreation of some classic games as browser games.
Find a file
2026-03-15 13:45:21 +01:00
breakout combine common css styles 2026-03-14 01:00:23 +01:00
mines combine common css styles 2026-03-14 01:00:23 +01:00
scripts initial commit 2026-03-13 20:30:10 +01:00
snake combine common css styles 2026-03-14 01:00:23 +01:00
sokoban combine common css styles 2026-03-14 01:00:23 +01:00
styles combine common css styles 2026-03-14 01:00:23 +01:00
tetris combine common css styles 2026-03-14 01:00:23 +01:00
.gitignore initial commit 2026-03-13 20:30:10 +01:00
flowzen.webp initial commit 2026-03-13 20:30:10 +01:00
index.html combine common css styles 2026-03-14 01:00:23 +01:00
README.md corrections in README.md 2026-03-15 13:45:21 +01:00

Description

I've made some simple recreations of a few classic games. All of these games can be played in the browser.

They are programmed in PHP and JavaScript and use SQLite3 databases to store the highscores.

The games are independent from each other, sharing only one CSS file (common.css).

Installation

  • Download the zip file of this repo to your computer
  • Unpack the zip file
  • Upload the unpacked folder with a FTP program to your hoster

Requirements

  • Requires PHP > 8.0 with SQLite3 and PDO modules enabled.
  • Apache 2.x web server to make .htaccess rules work.

⚠️ Important note: ⚠️

If you are using nginx or any other web server that doesn't support .htaccess files, you have to create rules to prevent direct access to the .db files.

Development

All development work is done on this website. The included games are simple but fully working.

Note about support

This software is distributed AS IS.

I do not support it in any way. If you have issues, you have to solve them on your own.

I won't add any features on request, however you can simply fork this repo and start developing anything you need.

Changelog

v1.0.0

  • Initial release


Additional information

All my domains (flowzen.de, git.flowzen.de etc.) could have minor errors, since I am developing in my spare time. However, access is usually stable.

Note about versioning: Versions are cut in Major.Minor.Patch schema. Patch is incremental by every build. If there is a breaking change, it should be noted in the readme.