TERA Server Side Proxy for patch 92.03, 92.04 and 100.02
TERA Server Proxy:
You must be registered to see links
ArbiterServer 100.02 TW patch:
You must be registered to see links
(ArbiterServer_m1.exe)
ArbiterServer 92.03 TW patch:
You must be registered to see links
(ArbiterServer_m3.exe)
ArbiterServer 92.04 TW patch: already included in the
release (ArbiterServer_m2.exe)
ArbiterServer 71.03 EME patch: already included in the
release (ArbiterServer_m2.exe)
Patch 71.03 EME protocol is currently not supported!
Network proxy program written on node.js, designed to work on the TERA server side. Based on the
You must be registered to see links
, forked by me with support for modular architecture. In addition to allowing GM (QA) commands, you can install many proxy modules on the side of the server, expanding its functionality, and also
fixes some critical server vulnerabilities. There is also support for built-in commands for managing installed proxy modules (it work only in QA mode), you need to use the "~" prefix for input.
UPD: Since the latest versions, the TERA Server Proxy no longer processes packets with the packet integrity algorithm (rehashing packet headers). This should make the program work faster. If necessary, integrity algorithm can be enabled in the config file.
Allowing GM commands for specific accounts
This method is an alternative to the
ArbiterHook used in version 92.03.
The implementation allows you to allow
GM (QA) commands to certain accounts by proxying connection to the TERA Server with the block of the
C_ADMIN packet. It will also need to replace original
ArbiterServer.exe to allow QA commands on qaServer disabled mode.
How to install (Video Guide - "Proxy Server Setup"):
- Unpack the tera-proxy-server to your server directory.
- Unpack the ArbiterServer_m1.exe (or ArbiterServer_m2.exe) to your Bin directory of TERA Server
(for patch 92.03 you need to use ArbiterServer_m3.exe included in distribution).
- Open the 1. ArbiterServer.bat file and change ArbiterServer to ArbiterServer_m1
(or to ArbiterServer_m2 for patch 71.03 and 92.04, or to ArbiterServer_m3 for patch 92.03).
- Open the DeploymentConfig.xml file, change port 7801 to 7701, and set the qaServer param to false.
- Start the TERA servers (Arbiter, World, etc.).
- Run tera-proxy-server\Start.bat.
- Go to TERA API Admin Panel and set the Privilege value for the account you want to grant commands.
- Make sure that port 7701 is not available for external user connections.
Privilege values:
- 31 - Only QA commands allowed.
- 32 - Only GM panel allowed (Alt+A).
- 33 - QA commands and GM panel are allowed.
Important note:
Since this method uses proxying, it will no longer be possible to obtain user's real IP address, so IP bans in
TERA API will not work. To resolve this problem, update TERA API to the latest version and set parameter
API_ARBITER_USE_IP_FROM_LAUNCHER as
true. When using the Launcher (Portal API) behind a proxy like nginx or Cloudflare, set parameter
LOG_IP_ADDRESSES_FORWARDED_FOR as
true.