ported2browserTHE INDEPENDENT FIELD GUIDE

BROWSER PORTS / SOURCE NOTES

Open engine, original game data: check both licences.

A freely licensed engine can still require separately copyrighted levels, sprites or music. The download and the licence need to describe the same material.

Open engine, original game data: check both licences.
Original OpenLara waterfall screenshot from its README. Credits: XProger / OpenLara; original game rights remain with their owners.

KEEP IN MIND

  • Identify the code and the data separately.
  • Read asset-level notices.
  • Keep required credits with a distributed copy.
  • Do not infer a licence from public source alone.

Identify what the repository implements

OpenLara describes an open-source reimplementation of a classic Tomb Raider engine. Its BSD licence applies to that implementation. PrinceJS likewise implements a classic game in JavaScript. Naming the engine or reading its source does not establish that every file from the original commercial release has received the same licence.

Read the notices beside the assets

BananaBread uses zlib terms for code and different Creative Commons notices for artwork. Its README points to the relevant directories and attribution. A top-level repository badge can summarize the code while leaving sound, textures, fonts and third-party libraries under separate terms. Check those notices before reusing an asset.

A play link is different from a redistribution grant

You can follow a developer’s browser demo without being given permission to publish a separate copy of all its data. This guide links the project’s host and credits editorial images. It does not offer a commercial game archive or infer permission from the fact that a demo can be reached in a browser.

For a local copy, keep the actual obligations

The two games hosted directly on this site have different licences: Hextris uses GPL terms and original 2048 uses MIT terms. Their player pages retain notices and describe modifications; the Hextris player also offers corresponding source. Copying a screenshot or changing a filename does not remove the licence obligations attached to a distributed program.

Keep source visibility and open licensing separate

Some projects publish readable source without identifying a reuse licence. Digger’s checked repository is an example in this collection. That source is useful evidence about its implementation, but this guide does not label it MIT or call every project freely redistributable. Follow the project’s actual notice if you plan to build on it.

Read the originals.

PUT IT INTO PRACTICE

Open a game.

The full collection
PrinceJS project imageAdventure

Learn the edge before taking the jump

Browser recreationKeyboard / touch documented