ubergames/lilium-voyager
0
0
Fork 0
mirror of https://github.com/UberGames/lilium-voyager.git synced 2024-12-14 22:20:58 +00:00
Code Issues Projects Releases Packages Wiki Activity

Update README.md

Browse source
This commit is contained in:
Zack Middleton 2018-06-10 03:32:36 -05:00
parent 307609296c
commit 38e06ac920
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -1,10 +1,10 @@
<img src="https://raw.githubusercontent.com/zturtleman/lilium-voyager/master/misc/lilium.png" width="64"> <img src="https://raw.githubusercontent.com/zturtleman/lilium-voyager/master/misc/lilium.png" width="64">
**Lilium Voyager** is a fork of [ioquake3](https://github.com/ioquake/ioq3) for running _Star Trek Voyager: Elite Force_ multiplayer. It is based on Thilo Schulz' [ioEF engine](http://thilo.kickchat.com/efport-progress/) (also known as iostvoyHM). The focus for Lilium Voyager is to maintain Elite Force multiplayer support on newer ioquake3 versions. **Lilium Voyager** is a fork of [ioquake3](https://github.com/ioquake/ioq3) for running _Star Trek Voyager: Elite Force Holomatch_ (multiplayer). It is based on Thilo Schulz' [ioEF engine](http://thilo.kickchat.com/efport-progress/) (also known as iostvoyHM). The focus for Lilium Voyager is to maintain Elite Force multiplayer support on newer ioquake3 versions.
Differences from ioEF 1.38-rc1 (2011): Differences from ioEF 1.38-rc1 (2011):
* Player origin rounding is compatible with the original QVMs. * 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). * Fixed "read past end of server message" error after downloading a pk3 using EF 1.2 protocol (24).
* Network compatible with ioEF 1.37. * Network compatible with ioEF 1.37.
* Dedicated servers are listed on official Raven master server. * Dedicated servers are listed on official Raven master server.