Lilium Voyager is an engine compatible with Star Trek Voyager: Elite Force Holomatch (multiplayer).

The goal is to maintain the original Star Trek Voyager: Elite Force: Holomatch gameplay, visuals, and audio experience while also providing a reliable code base for derivative projects and continued support for Windows XP+, macOS 10.5+, and GNU/Linux.

Lilium Voyager defaults to displaying the game as 4:3 letterbox with console/notify text at the same relative size as 640x480 resolution for an authentic Voyager experience on modern displays in high resolution.

Lilium Voyager includes ZTM's Flexible Display; the successor to ZTM's Flexible HUD mod for ioq3. Flexible Display offers aspect correct widescreen but with various new enhancements, including support for mods and joining pure servers.

There are six widescreen presentation modes (controlled by cl_flexibleDisplay cvar):

1. Original 4:3 view/HUD (default).
2. Expanded view with 4:3 centered HUD.
3. Expanded view/HUD (not compatible with all mods, still under development).
4. Expanded view with stretched HUD.
5. Original stretched view/HUD.
6. Original widescreen view/HUD.

Expanded view respects dmflags 16 (fixed fov) set by a server and switches to stretched view. There are flexup and flexdown commands that can be bound to conveniently switch modes while playing. You can optionally replace the original view sizedown / sizeup keys using bind - flexdown; bind = flexup; bind + flexup;.

Flexible Display is compatible with mods based on the original Q3 SDK and ioquake3 by running the mod logic at a fake 640x480 resolution and applying widescreen adjustments in the engine to match the window's resolution. cl_flexibleDisplay 0 disables Flexible Display to access the mod's original resolution dependent behavior. Flexible Display can also be disabled at compile time if one wants to create a derivative project without this feature.

Additional enhancements in Flexible Display:

• Fixed player model being stretched in setup menu in widescreen when using the original pk3 files / ui.qvm.
• Fixed notify message position for Team Arena voice head in top-left in widescreen when using the original Team Arena pk3 files / cgame.qvm.
• Support for absolute mouse movement in the menu to make mouse movement sensitivity match desktop movement and move to the location touched on a touch screen. (Various iOS and Android ports have shipped a custom ui.qvm to add this, lacking support in mods.)
• Support for the mouse cursor leaving the window while in the menu.
• Support for resizing the window without reloading the game content (opengl1 renderer only).
• The console background and loading level image are aspect correct in "expanded view/HUD" mode; great for mods that add a logo to the console or level images.

General enhancements (usable independent of Flexible Display):

• Console text defaults to scaling to match 640x480 size; this can be overridden using con_native 1; con_scale 2 to draw at native font resolution like the original Quake 3 with a custom scale factor to make it readable in 4K.
• The game window defaults to resizable.

All the changes for Flexible Display can be disabled by opening the console using Shift+Escape and pasting the following using Ctrl+V and pressing enter:

cl_flexibleDisplay 0; con_native 1; r_allowResize 0; vid_restart;

and re-enabled using:

cl_flexibleDisplay 1; con_native 0; r_allowResize 1; vid_restart;

Differences from ioEF 1.38-rc1 (2011):

• Player origin rounding is compatible with the original QVMs (x86, x86_64).
• Fixed "read past end of server message" error after downloading a pk3 using EF 1.2 protocol (24).
• Network compatible with ioEF 1.37.
• Dedicated servers are listed on official Raven master server.
• Client and server use separate config files (from ioq3).
• Better compatibility with newer operating systems (from ioq3).
• VoIP uses Opus codec instead of Speex (from ioq3).
• Support for ioquake3's OpenGL2 renderer.

Lilium Voyager is based on Lilium Arena. Lilium Voyager code commits: compare/lilium-arena...master

The source code for the Elite Force Holomatch game, cgame, and ui code is not included as it remains under a non-free license.

Lilium Voyager is based Thilo Schulz' ioEF engine (also known as iostvoyHM) that reimplemented the Star Trek Voyager: Elite Force: Holomatch engine on the Quake 3 GPL source code by id Software that was further developed in ioquake3. ioEF began development in 2005 and left off in 2011.

zturtleman picked up updating ioEF to newer ioquake3 in 2014 under the name Lilium Voyager. In 2025, Lilium Voyager moved to using Lilium Arena as it's based instead of ioquake3.

The ioEF code changes were distributed as diff patches for ioquake3's Subversion repository at the ioEF website. These are available as complete source code at zturtleman/ioef-archive. Thilo Schulz updated ioEF in 2016 at thiloschulz/ioef; this did not see a formal release and it does not include the past ioEF source code.

Lilium Voyager is licensed under the GNU GPLv2 (or at your option, any later version). The Elite Force Holomatch data files are not under a free license and must be purchased in order to play Elite Force Holomatch.

• Website
• Discussion / Technical support

Lilium Voyager is compiled using GNU Make (make) and requires a C compiler. Most dependencies are included in the repository. Compiling for Linux requires installing SDL 2 library and headers.

High quality code contributions are more helpful than rushed contributions. LLM ("AI") contributions are not desired.

Reviewing pull requests is sometimes more work than a reviewer doing the work in the first place so pull requests may be disregarded.

Lilium Voyager is maintained by Clover.moe at https://github.com/clover-moe/lilium-voyager.

• John Carmack
• Robert A. Duffy
• Jim Dose'
• Jan Paul van Waveren

• Tim Angus
• James Canete
• Vincent Cojot
• Ryan C. Gordon
• Aaron Gyes
• Zack Middleton
• Ludwig Nussel
• Julian Priestley
• Scirocco Six
• Thilo Schulz
• Jack Slater
• Tony J. White
• ...and many, many others!

• Thilo Schulz

• Zack Middleton (zturtleman)

If you create a derivative project that you plan for others to use, it would be preferred to give it a different title such as "Lilium Voyager (your name ver.)" to make it easier to discuss and reduce confusion with the project maintained by Clover.moe.

If you're going to pick a different title, it would be preferred that you pick a different song title to build on rather than use the word Lilium. (Lilium is the title of the opening song of the 2004 anime series Elfen Lied.)