I just updated the tera-crypto library for the new version of node.js, no other changes were made.Quote:
Originally Posted by sasha5434
Thanks for the explanation and the link.
I just updated the tera-crypto library for the new version of node.js, no other changes were made.Quote:
Originally Posted by sasha5434
Thanks for the explanation and the link.
Tera Server Proxy has been updated.
Download: https://github.com/justkeepquiet/tera-proxy-server
Now it is based on TeraToolbox with support for modular architecture.
The fork was made by me, based on the well-known Tera Private Toolbox, which supports patches 92 and 100. 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.
Thanks to @sasha5434 (Tera Asura Project) for the information, fake-ping module and provided full opcodes for patch 92.04.
works fine
Instructions are not clear enough and leave a lot of room for interpretation:
- What is a "TERA Api" admin panel? There is no such thing. There's steer admin, box admin, server admin.
- Do I unpack the proxy folder itself into my server directory or the contents of the proxy folder? Both can be understood as "unpack the proxy folder in your server directory". Does it even matter?
- How do I know if it is working correctly? Does it output any errors if it's not working correctly?
Clarifying little details like this helps to minimize the troubleshooting needed. The instructions in this thread also miss the step about the ArbiterServer_m1.exe file. That step itself is mentioned on the Github page but the owner of said page has the step false too. The correct location is NOT TeraServers\bin as there is no such thing as a "bin" folder with the 100.02 official release that shadow66 packed up neatly in a virtual machine. The correct location is the root of TeraServers, the folder itself, where ArbiterServer.exe is located. Or at least I assume so. Again, there is a total lack of documentation to confirm this. But the lack of errors from the proxy server's command prompt makes me think that the exe is in the correct location.
- What is a "TERA Api" admin panel?Quote:
Originally Posted by xSpeedx
https://forum.ragezone.com/f797/tera...s-and-1205579/
Changelog > Update 06.08.2022 (Installation) > How to install an update
https://i.ibb.co/k2vW7Hg/Screenshot-59.png
- Do I unpack the proxy folder itself into my server directory or the contents of the proxy folder? it doesn't matter while you unpack the files into your server location
- How do I know if it is working correctly? When you start the proxy and an account reach the lobby it prints the output redirection in the cmd window from 7801 to 7701
https://i.ibb.co/z6QCG6c/Screenshot-60.png
The instructions in this thread also miss the step about the ArbiterServer_m1.exe file: I clearly see it
How to install:
2. Open the 1. ArbiterServer.bat file and change ArbiterServer to ArbiterServer_m1.
This guide is really well writen, keep in mind you're speaking about the configuration of the pre-made vm that was maded by someone else
in the original leak (non vm), the server has the following structure
https://i.ibb.co/SBGJqdR/Screenshot-61.png
The missing step has been added. Thank you for your comment.Quote:
Originally Posted by argeus99
With the patched arbiter, the 92.03 version with proxy is not working propertly...even with 33 as privilege it only allows to use the gm panel but not the gm commands...just does nothing when you type it
@argeus99 I think you are using the wrong arbiter file. You need to use ArbiterServer_m3.exe from the leaked server 92.03.
I also confirm that the proxy works fine on server 92.04 (with 300+ players online).
Thanks for clarifying, the structure is indeed different. I suppose the VM creator is to blame because one should never change the folder structure of a release from its original state unless a software error requires that. It only leads to confusion and issues when one guy has a different layout from what's commonly accepted as the original.Quote:
Originally Posted by argeus99
I can also confirm that GM commands appear to work on my privilege 31 account. Not all of them though. I could add exp to my character walk speed has no effect in the game. The server proxy prompt however reports the commands correctly:
At least setting invincible does work. There's no confirm feedback from the prompt but in the game, I take no damage when hit with the command active.Quote:
[10984] [12:28:35.608] QA Command Success: add_exp 1
[10984] [12:28:41.389] QA Command Success: invincible
[10984] [12:28:45.521] QA Command Success: invincible on
[10984] [12:28:58.799] QA Command Success: invincible off
[10984] [12:29:12.783] QA Command Success: invincible
[10984] [12:29:17.341] QA Command Success: invincible
[10984] [12:31:41.186] QA Command Success: set_walk_speed 1
[10984] [12:31:44.580] QA Command Success: set_walk_speed 10
[10984] [12:31:48.729] QA Command Success: set_walk_speed 2
[10984] [12:31:57.171] QA Command Success: set_walk_speed
[10984] [12:32:03.237] QA Command Success: set_walk_speed 2
For move speed try /@speed 2 that will make your character walk faster.Quote:
Originally Posted by xSpeedx
hello, lately this error is appearing and the proxy server crashes, what is the cause?
https://cdn.discordapp.com/attachmen...9481/image.png
I think, this problem is due to the fact that vmware incorrectly synchronizes the clock of the virtual machine with the PC, so the task queue in node.js does not work correctly. Check this: https://bootpanic.com/how-to-fix-ass...ine-309-error/Quote:
Originally Posted by Loliconera
Tera Proxy Server has been updated.
Added module to protect against exploit with packets C_REQUEST_PVE_RANKING and C_REQUEST_PVP_RANKING that cause the Arbiter server to crash. This vulnerability is present in almost all patches, and in recent days many private servers have been attacked. So please take note.
Tera Proxy Server has been updated.
Changes:
- Updated exploit-fix module.
- Updated tera-crypto library and added open-source packet integrity algorithm.
- Added setting to enable the packet integrity (disabled by default).
- Added node-fetch module (needed for some cases).
Installation:
- Download and replace all files with new ones (config.json can not be updated).
- Restart Tera Proxy Server.