By <b>Kamel</b>
This document is intended only for those who own servers that run the ETPro modification. If you are not the owner of a server, please consult the client FAQ.
<b>Q</b>: I just finished uploading ETPro to my server and it isn't working, what should I do?
<b>A</b>: A common mistake when installing the ETPro mod on servers is forgetting to add the command +set fs_game etpro to the command line. This tells ET to run the mod, and MUST be done through the command line that is used to execute the game exe file, as opposed to using a configuration file to change this.
<b>Q</b>: When I start my server, everyone gets the yellow message "Server installed improperly, Multiple client PK3's detected." how do I fix this?
<b>A</b>: This means that you have one or more etpro.pk3 files in your /etpro directory. Go into your ETPro directory and delete all but one .pk3 file. I would personally suggest deleting all of them then placing the .pk3 back in the foler that came with the newest release you installed.
<b>Q</b>: I am afraid of hackers and/or my archive integrity, what are the md5 hash values of them?
<b>A</b>: ETPro 1.0: 94f4bc5b3092ce6f12c36d77afff9e89
ETPro 2.0: bbd0c203237fab3d0bc45f69a3b54f23
ETPro 2.0.1: aebf39a49c6fb6da7cd0f6fc260ccd9a
ETPro 2.0.5: 82bb0374c5ec8bbec31952dac49199f0
ETPro 2.0.7: 9a255b96836b03ea374ed4fa058fda66
ETPro 3.0.0: 8e9a331ccb2dfe021a82e99b2b0b12ae
ETPro 3.0.1: d3bd03987230049fcf81c973d6b43d62
<b>Q</b>: I hear that the new ETPro version (3.0.1) sucks, is it "really" better that I get an older version?
<b>A</b>: This is entirely done with the disgression of the person. Most likely the reason why the people suggest an older version is because they do not like hitsounds, they were affected by the demo playback bug of 3.0.0 (fixed in 3.0.1), or they are not pleased with the ability to dynamite the back door of battery. These are all settings that the server admin can change, so I feel there is no reason to go with an older version. If you insist, however, all versions less than 2.0.7 (and including) are depreciated with bugs and exploits clients can use to cheat.
<b>Q</b>: I have this stats program (any) that is designed for regular Enemy Territory. It works fine but not on ETPro.
<b>A</b>: ET has some awkward logs to parse. To make it better and more dynamic, there has been features added to modify that. In order to turn off these features, simply set the following variables and your stats program will work fine (no, really, I'm not kidding).
Code: Select all
b_logrealtimestamps 0
b_brokenlogtimestamps 1
<b>Q</b>: What does impure client pk3's detected mean?
<b>A</b>: When your server has sv_pure set to 1, that means the client must be using the exact same files that the server is using. The system ET uses for checking the files is not always perfect, so it will sometimes have problems with this. Likely this will happen after a client has downloaded, the only known fix is to have the client completely exit et and reconnect.
<b>Q</b>: My friend says when connecting to my server he gets some error complaining about hunk megs, is this my fault?
<b>A</b>: No, this is an entirely client side setting that is not set properly on his side. Tell him to try increasing his com_hunkmegs value. (default 54)