etpub_client - optional ET client mod for use on etpub servers

Documentation

English

WTF D00dZ?!!! etpub is a server-only mod!

Settle down. etpub will continue to be a server-side mod. We have no intention of breaking compatibity with the stock Enemy Territory client. If the idea of a etpub client mod frightens you, stop reading. You can ignore the fact that etpub_client exists.

What's the point?

1. There are bugs in the stock ET client that could be fixed.
2. There are some features added to etpub that will only work for modified clients. (e.g. the forcecvar command).

Why would I want to use it?

• It integrates many of Chruker's "Project: Bug Fix" fixes.
• It adds support for the 'forcecvar' server command.
• It uses etpub's player movement code, so client prediction will better match the server.
• If you use ETPro's etpromapscripts, you won't see the message "You are near the Back Door" on battery unless you use it. (support for EF_FAKEBMODEL).
• When playing dead, you don't see the text about being wonded and waiting for a medic.
• On servers with the g_weapons flags 2 or 4, you won't hear the predicted 'click' sound when using syringe or pliers underwater.
• '+lookdown' and '+lookup' commands are disabled to prevent scripted anti-recoil cheats.
• The editable HUD (see /edithud /loadhud and /dumphud client commands)
• Includes menu options for votes that have been added to etpub.
• It has a clock and menu options for enabling other HUD elements like the lagometer and drawFPS.

How do I install it?

If you DO NOT administer an etpub server, don't worry about it. This client mod is not intended to be installed by end-users.

If you DO administer an etpub server, then simply copy the etpub_client .pk3 file to your fs_game directory (usually named 'etpub') then restart your server. Note that this requires the client to download the pk3 when they connect so if you have never offered downloads before, now is the time to learn about ET's download settings.

What's with the lame versioning number?

etpub_client is offered as a .pk3 file with the name

etpub_client-YYYYMMDD.pk3

The date is used instead of the version of etpub it was built for a couple of reasons.

First, each release of etpub will not require a new etpub_client. For example, if there was an etpub_client-20050516.pk3, you would be able to use it for etpub versions 0.5.1, 0.5.2, and 0.6.1.

Second, the etpub_client could be updated between etpub releases so if you're running etpub_client-20050516.pk3 with etpub 0.5.1, etpub_client may be updated and you would run etpub_client-20050517.pk3 with etpub 0.5.1.

Why the date instead of a seperate versioning system? Most of our work is spent on etpub. etpub_client is more of a companion to that work than a seperate project. Therefore we don't need a versioning scheme to aid in development. Adding a seperate versioning scheme would also confuse admins about compatibility between etpub and etpub_client.