Tera API (node.js) and Launcher with pacher for patch 92/100

[Muggus]

Read header of theme and THIS post

Thank you <3 started

[argeus99]

Check server_info table in database accountdb.

- - - Updated - - -



Try to detele local.db, check.db and version.ini from the game folder.

That's it! i just renamed launcher.exe and delete local.db/version.ini

Thanks for your help!

- - - Updated - - -

1 Question,

I restored a 92.03 mssql backup and it worked with 100.02, but in the character selection screen only show that i only have 1 character but i have 7 (this behavior is purelly visual, ingame i have all of my chars)



looking at character table in mysql, there's only 1 record...then, is there a way to put those characters there or need to do it manually?

Thanks in advance

[hsdn]

looking at character table in mysql, there's only 1 record...then, is there a way to put those characters there or need to do it manually?
Thanks in advance

Because API has its own database of characters (duplicating the main one), you need to manually add all the characters to the table account_characters. Also you can export Users table from PlanetDB using Navicat, edit (using notepad++) and import into account_characters.

- - - Updated - - -

I had plans to synchronize these tables, but because of the old version of the SQL Server (which is not supported by the Sequelize library on node.js). In patch 100, there is already an updated SQL Server, and this idea can be implemented, but this is only needed once when migration from 92 to 100.

[argeus99]

Because API has its own database of characters (duplicating the main one), you need to manually add all the characters to the table account_characters. Also you can export Users database from PlanetDB using Navicat, edit (using notepad++) and import into account_characters.

That's exactly what i did and it works

I had plans to synchronize these tables, but because of the old version of the SQL Server (which is not supported by the Sequelize library on node.js). In patch 100, there is already an updated SQL Server, and this idea can be implemented, but this is only needed once when migration from 92 to 100.

Looking forward to it!

Thanks!

[outlanderzor]

I got the Server and the API running, but when I try to enter the server I get an error message "Member authentication failed". When I check the server for logs the arb_gw returns the following message "GameAuthenticationLogin { "Return":false, "ReturnCode":0011, "Msg":"authkey mismatch" }.

I'm trying to setup the v100 server from scratch using the tera-api launcher and I'm kinda new on this.
Anyone had this issue or can give me any pointers on what I'm doing wrong?

I'll post some screenshots to make it easier to understand.
Thanks everyone for all the support.

[hsdn]

Try to log out of the launcher using the "logout" button and log in again using your username and password (a new ticket/auth-key will be created). If the problem is not solved, your computer probably has a different IP address for the game server and the API server (launcher). Check the port forwarding/nat/web-server-proxy settings.

[Brat05]

HI friend, your API is very good, thank you for sharing
But I have a problem with packing the file
No matter how I change, it always prompts that the directory cannot be found





solved，Need to create a temp temporary directory, thanks

[juniordark]

...
No matter how I change, it always prompts that the directory cannot be found

create a temp folder inside tera-client-packer

[Brat05]

create a temp folder inside tera-client-packer

Wow, solved, thank you very much

[Murasama]

I seem to be running into a different issue on my setup (using tya0411's virtual machine) where the launcher isn't even displaying the login/signup form. I've pretty much gone through this entire topic and tried every conceivable tip in it, to no avail.

IP Address on the VM is 192.168.163.130. The following pertinent parameters remained constant in .env:

API_ARBITER_LISTEN_PORT=8080
API_PORTAL_LISTEN_PORT=8090
API_PORTAL_LOCALE=en
API_PORTAL_CLIENT_DEFAULT_REGION=EUR
API_PORTAL_CLIENT_PATCH_NO_CHECK=true
API_PORTAL_PUBLIC_FOLDER_ENABLE=true

The initial issue was getting arb_gw to run: it failed with the following (and any iteration of the portal address setting where localhost is used for Arbiter):

API_ARBITER_LISTEN_HOST=127.0.0.1
API_PORTAL_LISTEN_HOST=192.168.163.130

arb_gw throws:



The only parameters where arb_gw got to server ready were:

1. leaving both API_ARBITER_LISTEN_HOST and API_PORTAL_LISTEN_HOST blank
2. setting both API_ARBITER_LISTEN_HOST and API_PORTAL_LISTEN_HOST to 192.168.163.130

With either of these, I can launch the necessary server processes.

The launcher (from the repository) is resource edited as follows:



The following are the changes made in accountdb.server_info:



Even though I have API_PORTAL_CLIENT_PATCH_NO_CHECK=true, I still have the packed client cab files in the tera-api/public/patch folders on the virtual machine side (the pack was done after making sure local.db and version.ini were not in the client folder).

Running the launcher results in no login window/launcher window being displayed, it only shows the Error 274 (40400): ini error message dialog:



I've tried all variations posted in this thread regarding the version.ini file in /public/patch including removing it but the above error still persists. I'm able to get the login/signup window loaded by going to http://192.168.163.130:8090/tera/LauncherMain via a web browser, and then to the game start window after signing up, and then logging in from the first screen (just cannot get the launcher itself to display this unlike most others folks who have had issues with Error 274):



I'm suspecting it is something simple that I might have overlooked elsewhere (the virtual machine firewall is still disabled as is the one on the system running the VM and the game client files to remove this from the equation).

[tya0411]

I seem to be running into a different issue on my setup (using tya0411's virtual machine) where the launcher isn't even displaying the login/signup form. I've pretty much gone through this entire topic and tried every conceivable tip in it, to no avail.

IP Address on the VM is 192.168.163.130. The following pertinent parameters remained constant in .env:

API_ARBITER_LISTEN_PORT=8080
API_PORTAL_LISTEN_PORT=8090
API_PORTAL_LOCALE=en
API_PORTAL_CLIENT_DEFAULT_REGION=EUR
API_PORTAL_CLIENT_PATCH_NO_CHECK=true
API_PORTAL_PUBLIC_FOLDER_ENABLE=true

The initial issue was getting arb_gw to run: it failed with the following (and any iteration of the portal address setting where localhost is used for Arbiter):

API_ARBITER_LISTEN_HOST=127.0.0.1
API_PORTAL_LISTEN_HOST=192.168.163.130

arb_gw throws:



The only parameters where arb_gw got to server ready were:

1. leaving both API_ARBITER_LISTEN_HOST and API_PORTAL_LISTEN_HOST blank
2. setting both API_ARBITER_LISTEN_HOST and API_PORTAL_LISTEN_HOST to 192.168.163.130

With either of these, I can launch the necessary server processes.

The launcher (from the repository) is resource edited as follows:



The following are the changes made in accountdb.server_info:



Even though I have API_PORTAL_CLIENT_PATCH_NO_CHECK=true, I still have the packed client cab files in the tera-api/public/patch folders on the virtual machine side (the pack was done after making sure local.db and version.ini were not in the client folder).

Running the launcher results in no login window/launcher window being displayed, it only shows the Error 274 (40400): ini error message dialog:



I've tried all variations posted in this thread regarding the version.ini file in /public/patch including removing it but the above error still persists. I'm able to get the login/signup window loaded by going to http://192.168.163.130:8090/tera/LauncherMain via a web browser, and then to the game start window after signing up, and then logging in from the first screen (just cannot get the launcher itself to display this unlike most others folks who have had issues with Error 274):



I'm suspecting it is something simple that I might have overlooked elsewhere (the virtual machine firewall is still disabled as is the one on the system running the VM and the game client files to remove this from the equation).

When you're visiting http://192.168.163.130:8090/tera/LauncherMain is it from the server or your machine(or both)?

[argeus99]

Spoiler:

I seem to be running into a different issue on my setup (using tya0411's virtual machine) where the launcher isn't even displaying the login/signup form. I've pretty much gone through this entire topic and tried every conceivable tip in it, to no avail.

IP Address on the VM is 192.168.163.130. The following pertinent parameters remained constant in .env:

API_ARBITER_LISTEN_PORT=8080
API_PORTAL_LISTEN_PORT=8090
API_PORTAL_LOCALE=en
API_PORTAL_CLIENT_DEFAULT_REGION=EUR
API_PORTAL_CLIENT_PATCH_NO_CHECK=true
API_PORTAL_PUBLIC_FOLDER_ENABLE=true

The initial issue was getting arb_gw to run: it failed with the following (and any iteration of the portal address setting where localhost is used for Arbiter):

API_ARBITER_LISTEN_HOST=127.0.0.1
API_PORTAL_LISTEN_HOST=192.168.163.130

arb_gw throws:



The only parameters where arb_gw got to server ready were:

1. leaving both API_ARBITER_LISTEN_HOST and API_PORTAL_LISTEN_HOST blank
2. setting both API_ARBITER_LISTEN_HOST and API_PORTAL_LISTEN_HOST to 192.168.163.130

With either of these, I can launch the necessary server processes.

The launcher (from the repository) is resource edited as follows:



The following are the changes made in accountdb.server_info:



Even though I have API_PORTAL_CLIENT_PATCH_NO_CHECK=true, I still have the packed client cab files in the tera-api/public/patch folders on the virtual machine side (the pack was done after making sure local.db and version.ini were not in the client folder).

Running the launcher results in no login window/launcher window being displayed, it only shows the Error 274 (40400): ini error message dialog:



I've tried all variations posted in this thread regarding the version.ini file in /public/patch including removing it but the above error still persists. I'm able to get the login/signup window loaded by going to http://192.168.163.130:8090/tera/LauncherMain via a web browser, and then to the game start window after signing up, and then logging in from the first screen (just cannot get the launcher itself to display this unlike most others folks who have had issues with Error 274):



I'm suspecting it is something simple that I might have overlooked elsewhere (the virtual machine firewall is still disabled as is the one on the system running the VM and the game client files to remove this from the equation).

Make sure you have version.ini in your game folder

This how my configs looks like working as intended





also make sure set to true the client verification

# Enable the client file check disallow.
# If set to true, the launcher will not check for client updates.
API_PORTAL_CLIENT_PATCH_NO_CHECK=true

[hsdn]

@Murasama Try this: https://forum.ragezone.com/f797/tera...1/#post9126481

[outlanderzor]

Try to log out of the launcher using the "logout" button and log in again using your username and password (a new ticket/auth-key will be created). If the problem is not solved, your computer probably has a different IP address for the game server and the API server (launcher). Check the port forwarding/nat/web-server-proxy settings.

Solved.
I had to logout and log in again, thanks!

[Murasama]

When you're visiting http://192.168.163.130:8090/tera/LauncherMain is it from the server or your machine(or both)?

It's from outside the virtual machine

- - - Updated - - -

Make sure you have version.ini in your game folder

This how my configs looks like working as intended





also make sure set to true the client verification

Thanks argeus99, will give this a look over again and see what happens!

- - - Updated - - -

@Murasama Try this: https://forum.ragezone.com/f797/tera...1/#post9126481

Thanks hsdn. I did that before with all of my other tests but will try again by duplicating argeus99's .env config (I don't think I tried 0.0.0.0 for the portal).

------
RESOLVED

Thanks everyone for the pointers and tips!

I tried argeus99's .env settings but it didn't work for me as the launcher got stuck with just the loading dialog and I could no longer load up the launcher form from outside the VM via a web browser. So I went back to one of the original configs I had (where I could at least reach the launcher form from outside the VM via a web browser) but the launcher was still throwing Error 274. I double checked server side (for the hundredth time) to make sure version.ini wasn't in the patch directory (it wasn't) and I had my original version.ini in the game client folder (it was).

It was as expected, something VERY simple that was curb stomping my launcher. What happened is that I had also inadvertently removed launcher_info.ini (probably happened the same time when I removed version.ini and ended up forgetting that it existed until I unpacked a copy of the tera-api archive to start over from scratch). Replaced that, and everything is now working.