Selevet Eglantine: the tuned single-machine build

Latest release

selevet-eglantine-performance-9prerelease Published 2026-11-06· 1 package below

Download latest

Copies a prompt your AI agent can run to install Selevet Eglantine.

Which package should I choose?

One Windows x86_64 zip per release, published as a prerelease. The current one is performance build 9, extracted and run as selevet.exe. Settings are built in, so setup is keys, firmware and a controller mapping. The repository's tuned README documents what every build changed.

Package Architecture Size
selevet-eglantine-performance-9-windows-x86_64.zip ↗ x86_64 24.1 MB

What this build needs

A CPU with AVX2 (the build targets x86-64-v3 and exits on older chips), the current Microsoft Visual C++ x64 runtime, and your own dumped keys, firmware and games. One machine is the tested baseline, named in the tuned README: a Ryzen 5 5500 with an RTX 3050 and 16 GB of RAM.

Getting started

  1. Match your CPU

    The build is tuned for Zen 3 CPUs. On other hardware the standard Eglantine build is the documented choice.

  2. Get a build

    Download a prerelease from the upstream GitHub releases page.

  3. Keep saves separate

    When testing a tuned build against a main install, keep save data apart so the tuned build cannot disturb it.

  4. Check for updates

    This directory records the project as no longer maintained, so verify the upstream repository for anything newer.

Common problems

How it differs

Selevet Eglantine is a single-maintainer tuning fork of the Eglantine line, built for one game on one documented PC, with no stable tag and a repository marked no longer maintained. Its later builds merged Ocarina of Time support from Lichii branches. The tuned README records what each merge cost.

Recent upstream releases

See every release on the upstream page ↗

Last checked 2026-11-22. Release data fetched 2026-11-22. A release sync refreshes metadata from upstream; it does not re-verify compatibility.

Download FAQ

Why is everything a prerelease?

The project publishes tuned builds of a fork under development and tags nothing stable, and the repository itself is marked no longer maintained.

Which build runs which game?

The tuned README walks each one: later builds merged Ocarina of Time support and its speed-ups, while an earlier build kept fixes those builds dropped. The notes name the trade in both directions.

Before installing