ET: Legacy

ET: Legacy - free open source multiplayer fps game
ET: Legacy - free open source multiplayer fps game
ET: Legacy - free open source multiplayer fps game

ET: Legacy Team Blog

ET: Legacy on Android

This has been few days passed since our newest release yet and this post should be released way earlier Yes I know. I am here shed some light on Android Port of this game to those are keen to know more about its origin how it started and explain a bit more about control sheme to those who are still not familiar with it or looking for such explaination.

PRE-STORY:

Before we begin our small story talk there is known issue with server list browser not showing servers. Disable ui_disableOssFilter 1 in game console and just a warning only legacy mod is compatibble. How to open console Bellow GENERAL

STORY TIME:

It has been year of 2018 almost the end of it. I found out that SDL has added support for Android Devices and in my head "An Idea has started to show up" to start porting / adding support for ET Legacy for Android. I had basic support for Android in 2019 nothing fancy just run a game and connect to a server thats all I had in a back, more of the stuff has been added for getting the experience better for players up to Official Support for Android with 2.78 ET: Legacy.

GENERAL:

Latest Release of Android Version of game gives you all you need to get you on the server with minimal input as possible for user side so to speak it does download required files to your Phone Internal Storage. For Android Systems is is usually 'PhoneInternalStorage/Android/data/org.etlegacy.com' and all your cfgs/etkey You can also upload those required pak's by yourself to your Phone Internal Storage to: 'PhoneInternalStorage/Android/data/org.etlegacy.com` may vary depends on Android versions.

USAGE:

How to use the Buttons on your screens.

As shown above all those Buttons has their purpose. Buttons Binding are hardcoded in App code with their default counterparts in Game exept Shoot N and Alternate Weapon / Rifle Granade B due too lack of good mouse support at this moment.

As we did get to the end of this post. Let plan ahead Roadmap of this app:

  1. Better contolls alike Beloko
  2. Better support for mouse/keyboard/joystick

For better discussion/suggestions/bug reports visit our @discord or @github page


written by RaFaL 1 year ago

3 comments

ET: Legacy 2.81 - Incoming!

It's happening, everybody! We are kicking off the year 2023 with a massive release and there is so much MORE on the horizon!

20th Anniversary LAN

Initially released in 2003, we have the 20th anniversary of ET incoming in May. For a proper celebration, the wonderful folks of ET: Legacy Competitive are organising an on-site LAN event during the anniversary weekend based on ET: Legacy. After some showcase matches during the '2021 QuakeCon At Home' and several 'smaller' cups and tournaments, this is going to be the first 'major' e-sport appearance using ET: Legacy. For more information, please head over to the info channel in their Discord.

Release cycle

We are aware that we aimed for smaller quarterly releases and we are doing our best to get back to that! Nonetheless, we are even more happy to now bring you 8 months of hard work with this release. With the cooperation of the dev team and the comp scene admins growing closer and closer over the last few months and in preparation of this year's LAN event, there is a multitude of changes and features dedicated to improving the e-sports experience of ET: Legacy.

HUD Editor

One of the biggest features is the improved in-game HUD editor reachable by using the menu UI "Menu -> Options -> View -> HUD Editor" or by typing in console the /edithud command. For more information on this, please refer to this (WIP) page.

Changelog

You can find the comprehensive list of changes here, but we have compiled a list of the most notable changes in our Discord server, if you want to have a look. It's also the best place to give feedback, ask for support and discuss anything related to ET: Legacy (or ET/RTCW in general)


written by Kemon 1 year ago

No comments

ET: Legacy Competitive Ladder

ET: Legacy 3on3 Ladder is here!

The long-awaited ladder system is now ready and waiting for you to join in! Head over to https://reddal.gg/ to sign-up, create your team and challenge others to score points and get a position on the ladder. https://reddal.gg/


RULES

To avoid confusion and misunderstandings, it's recommended to read the ladder's rules before your first game. You can find them on the Reddal website or on the ET: Legacy Competitive Discord in the #ladder-3on3-rules channel.


FEEDBACK

To assure constant improvement of the ladder system, you are encouraged to provide feedback and suggestions on the ET: Legacy Competitive Discord in the #ladder-feedback channel.


HOW TO

1 The team captain needs to create a team on the website.

On the Reddal website navigate to your profile section and select 'Create Team'. On the team page, navigate to 'Administration' and invite at least 3 players to your team.

2 All players must add their GUIDs to their profiles before joining the ladder

On the Reddal website navigate to your profile section and select 'Edit Profile'. To check your Legacy GUID simply type /players in the in-game console. The GUID is the number on the right side of your nick.

3 Once a team has at least 3 players, the team captain can join the ladder.

On the Reddal website navigate to the 3on3 ladder and select 'Join this ladder'. You've now joined the ladder.


In case of any doubts about the above, please open a thread in #ladder-feedback on the ET: Legacy Competitive Discord.

We hope you will all enjoy the oldschool clanbase-like Legacy competitive experience in 2022. The ladder will last for at least a year, depending on the activity.

A massive thank you goes out to the organisers! To everyone joining: Good luck and have fun!


written by Kemon 1 year ago

No comments

ET: Legacy Scrims

Any FPS game with e-sports ambitions requires a dedicated competitive scene, so for this blog post we want to thank the 'ET: Legacy scrims' community for their long-standing commitment. The 'ET: Legacy scrims' community was created and is organised by eMMiel, Bystry and n'papo?, is powered by TeamMuppet with dedicated server infrastructure and facilitated by Kimi with the Gathermaster bot, so all in all a wonderful example of community commitment. Therefore, we plan to officially support and integrate this community into the ET: Legacy Discord, making it easier for the interested players among you to join in and get to know the more competitive side of ET: Legacy. While this integration still has to be ironed out here and there, we are happy to already announce this partnership to help grow the emerging competitive scene on ET: Legacy. scrims.jpg The current format are daily matches for 3on3 or 6on6, depending on the amount of online members. There are no skill brackets for now. Everyone is welcome to join and play a few test matches to see whether it's a fit. For further information, please visit their #rules channel which contains extensive info regarding the organisation and gameplay of the played scrim matches.

Depending on the reception among you, the playerbase, future plans range from experimenting with other scrim formats to organising one-day-cups or tournaments as was successfully done in the past. All that's left to say is, go check out their Discord server and play a few matches to get accustomed!


written by Kemon 2 years ago

No comments

Container System

You may have noticed that since a few weeks your main menu looks wonderfully clean. This is due to the container system which was initially introduced in ET: Legacy 2.77 and fixed in the 'Recapture the City!' 2.77.1 hotfix. In short, this system isolates all paks downloaded from an ET server and ensures your client looks clean and most importantly, remains usable on launch.

clean_menu.jpg

This is a major change addressing a long-standing issue, which we probably all are familiar with. After playing on a server the main menu has been tampered with in one form or another. This raises several issues for regular players. For example could it be that the main menu was translated by the previous server (quote6.png below), it also raises security concerns (quote7.png below) as those modifications to the game client happen without permission, but in general, it's probably simple annoyance (quote3.png below) by the constant alterations. Unfortunately, @stealth6 (quote2.png below) put it quite well, as the ET community lost the battle. However, Radegast, our founder, indicated plans to fix this issue (quote4.png below) once and for all and we finally did! 8 years later, but we got you Radegast! Your plans and vision for this project are in good hands. At least we hope so!

isolation.jpg

Short backstory

"Players. Admins. PK3s. Developers. Long ago, the four parties lived together in harmony. Then, everything changed when the Admins discovered the tilde ~. Only Radegast, founder of ET: Legacy, could stop them, but when the Players needed him most, he rightfully took a well-deserved retirement. Eight years passed and the current ET: Legacy dev team developed a new way to protect Players, the dlcache container system. And although our motives were good, we botched the early tilde block attempt in 2.76. But, We believe the dlcache container system can save the Players."

Long backstory

When connecting to a server, the pk3 get downloaded to your fs_homepath. Historically, all files from all the servers you connect to, get put either into etmain or the mod directory (e.g. legacy, silent,...), which are the same directories the game pulls the content from when launching the game. This enabled server admins to force players to download pk3 containing the aforementioned custom menu files, which the game then uses to initialise the main menu on launch. Because all the files from all the servers got put into the same respective directory, a war broke out between servers for who can put more Z or tilde ~ characters in front of their custom menu pk3. This was done because the game goes through the respective directory on launch alphabetically and overwrites previously loaded files with whatever comes after it. In other words, the game loads pak0.pk3 and finds a menu file. It then loads z_custom_menu.pk3 and finds a menu file which it uses to overwrite the one from pak0.pk3. Then zz_custom_menu.pk3 comes along and even after all the Zs the tilde (~~custom_menu.pk3) pk3 come along overwriting everything ones again. Hence, in 2.76 we tried to implement an early measure against all of that, by blocking the pk3 with the tilde ~ character from being downloaded. This, however, prompted righful backlash by our community as it also prevented you from joining those servers even if you understood and accepted the risk. Another solution was required and here we are.

Functionality

Now, pk3 get downloaded into a new sub-directory called dlcache rather than the base directories (e.g. etmain, legacy,...). This means that for example maps get downloaded into fs_homepath/etmain/dlcache instead of fs_homepath/etmain and server pk3 get downloaded into fs_homepath/legacy/dlcache instead of fs_homepath/legacy. These new sub-directories do not get initialised on game launch, which means that custom paks do not get loaded. This is different to the initial plan of the per-server container system described in the initial proposal here as that would have required players to always download all pk3 when connecting to a new server, because even maps would have been stored in each per-server container separately. That would have presented an immense inefficiency for your required disk space, which is why we are even more happy with the current implementation.

Things to keep in mind

  • Third-party mods Exception to this are third-party mods (e.g. silent, nq,...) as changing the folder structure is very likely going to break functionality of those mods. Therefore, it is recommended to keep legacy as the default mod on game launch (+set fs_game legacy).

  • Manual work-around The good news is that you can still manually install custom menu files for quick access to your favourite server. Simply check the pk3 from your favourite server or ask your server admins which of them contains the custom menu and move that to fs_homepath/etmain. Ideally, to minimise any risk, that pk3 should only include the necessary menu files, so please double check with your server admins if you have any concerns.

  • Local host When trying to host a game locally or when simply using /map or /devmap the contents of dlcache are not considered. You will have to manually pull those maps that you wish to test/play locally from fs_homepath/etmain/dlcache and put them into fs_homepath/etmain.


For further questions as well as if you, dear player, server admin, interested follower or else, are interested in contributing to this project, we are always looking for helping hands to speed things up, so please don't hesitate to reach out to us on Discord.


Quotes:


written by Kemon 2 years ago

No comments