Open-source project
XProger/OpenLara avatar
XProger/OpenLara

OpenLara: two builds, one moving release tag, and a roadmap filed as an issue

Classic Tomb Raider open-source engine

5,155 stars436 forksCBSD-2-Clause

At a glance

What is it?
OpenLara is a C reimplementation of the classic Tomb Raider engine, published as BSD-2-Clause with a browser build and a standalone download. The repository is four entries deep, the newest tagged build is from 2019, and everything a newcomer needs is four links away.
Who is it for?
OpenLara is a reasonable pick if you want to read or extend a classic Tomb Raider engine in C and can compile it yourself, and the wrong pick if you need a current binary or a documented build process. Before you start, decide whether the 2019 standalone release is enough or whether you need the source, because the repository and its newest download point at different generations of the code.
Can I use it commercially?
Yes. BSD-2-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 112 days ago.
What is it written in?
Mainly C, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • XProger/OpenLara5,155 ★ · +47
Star history
Repository2026-09-232026-11-15
XProger/OpenLara5.1k5.2k

47 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The README is one sentence and four links

There is very little text here. The heading is the project name, and the single descriptive line calls it a classic Tomb Raider open-source engine. Everything else is a link: a WebGL build with demo level pointing at the project homepage, a standalone version pointing at the releases page, a roadmap pointing at issue 353 on the tracker, and a BSD-2-Clause licence badge. Below that a Links section collects a Twitter account, a Discord invite, a Telegram group, a YouTube channel and a thread on the Tomb Raider forums. No prerequisites, no compiler version, no build command, no list of what the engine does or does not implement, no mention of which game data it expects. Everything you need in order to start is therefore a click away, and nothing about the engine itself is written down.

Two builds are offered and only one has a release page

The two runnable options are described in the link text and nowhere else. The first is a WebGL build with a demo level, hosted on the project homepage, which means it runs in a browser and already ships something to look at. The second is a standalone version, delivered as a GitHub release. That is the entire distribution story: one hosted demo and one download. The README does not say what platforms the standalone build targets, what the demo level contains, or how large either download is. The only platform hint anywhere comes from the release list, where one release title names the Nintendo Switch, which suggests platform specific work happens outside the single standalone tag. Anyone choosing between them is reduced to opening the release assets and reading the file names.

Release tags name platforms and stages, not versions

There is no version numbering to hold on to. The three most recent releases are tag `latest` (titled OpenLara), dated 2019-01-11; tag `20190109`, titled OpenLara Nintendo Switch; and tag `20181026`, titled OpenLara beta. Two tags are dates and one is a moving pointer, while the release titles name a platform and a maturity stage. The consequence is that `latest` cannot be pinned: it resolves to whatever was last pushed to it, so a build you archived and tested may not match what the same tag serves later, and there is no way to express the difference between two `latest` downloads other than by date. Meanwhile the roadmap is not a document or a milestone list but issue 353, so planned work and its status live in a discussion thread that a reader has to go and read.

The tree is four entries deep

The whole repository, at the top level, is:

text
LICENSE
README.md
bin/
src/

Two of those are documents. The other two are directories, one for sources and one for binaries. The primary language is C. What is not visible at this level is a build description of any kind, along with any continuous integration configuration, test directory, documentation tree or example project. That is a small tree for an engine, and it has a direct effect on a first attempt: the build definition, if there is one, is somewhere inside `src/` or `bin/`, so a contributor has to read the source layout before compiling anything. The same sparseness means there is no in repository guide to the file formats or the module boundaries you would need in order to change anything.

The newest binary predates the newest commit by years

The repository is not archived, and the last push to the `master` branch is dated 2026-07-26. The newest release, `latest`, is dated 2019-01-11. Those two dates are the most important facts for anyone deciding what to use. Source work has continued for years after the last tagged build, so the code you read in `src/` is not what the downloadable standalone version contains. In practice that splits the audience in two. Someone who wants a working binary is running code from 2019, whatever the repository looks like today. Someone who wants the current state has to compile it, and the README gives them no build instructions. Neither group is served well by the four links, because the links describe the older artifact more accurately than the newer source.

Licence is BSD-2-Clause and the licence file is one file

The licence is stated twice, once in the repository metadata and once as a badge linking to the BSD-2-Clause text, and the tree carries a single `LICENSE` entry rather than the pair of licence files a dual licensed project usually keeps. There is nothing further about licensing in the README: no note about game assets, no separate terms for the data files from the original games, no contributor licensing paragraph and no mention of how contributions are handled. If you intend to redistribute a build, or to ship something built with this engine, the licence of the code is the easy half to answer and the assets are the half you will have to raise with the project directly through one of the channels below.

Support runs through chat channels and one forum thread

The Links section is the contact map: a Twitter account, a Discord invite, a Telegram group, a YouTube channel, and a thread on the Tomb Raider forums. Five destinations, all conversational, none of them an issue template or a support process. The only tracked item named anywhere is the roadmap issue. Bug reports have no documented destination at all, which for a project whose binaries stopped in 2019 is the gap most likely to matter to you.

Editorial conclusion

OpenLara is a reasonable pick if you want to read or extend a classic Tomb Raider engine in C and can compile it yourself, and the wrong pick if you need a current binary or a documented build process. Before you start, decide whether the 2019 standalone release is enough or whether you need the source, because the repository and its newest download point at different generations of the code.

Frequently asked questions

what is open lara

OpenLara is described as a classic Tomb Raider open-source engine, written in C and released under BSD-2-Clause. The repository offers a WebGL build with a demo level, a standalone version as a GitHub release, and a roadmap kept in issue 353.

how to use openlara

The README carries no build or run instructions. It points to a WebGL build with a demo level on the project homepage and to a standalone version on the releases page, so using either means taking the download as it is offered rather than compiling from source.

openlara vs tomb raider remastered

The repository makes no such comparison. It presents itself as a classic Tomb Raider open-source engine in C under BSD-2-Clause, with a browser build that includes a demo level and a standalone download, and says nothing about any commercial release.

openlara vs opentomb

No alternative engine is named anywhere in the repository, so there is nothing to compare against in the documentation itself. What is stated is that OpenLara is a classic Tomb Raider engine in C, BSD-2-Clause licensed, with sources in `src/` and binaries in `bin/`.

Official sources

  1. License: BSD-2-Clause
  2. Project website
  3. README
  4. Releases
  5. XProger/OpenLara on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/xproger-openlara.svg)](https://hysenlabs.com/projects/xproger-openlara)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/xproger-openlara.svg)](https://hysenlabs.com/projects/xproger-openlara)

Was this useful?