NeoLauncher 0.9.1a (Latest)
Image from 0.7.3b:
Updated: 03.01.2021 - NeoLauncher 0.9.1a
-Now just 1 Tl.exe file, no need for 2 different EU/ASIA Clients
-Language Selection in launcher simplified (No Client selection anymore)
-Added "Tl.exe" Path to the config file
For the different Clients to work correctly, the Tl.exe file has always be one folder up from the "\Binaries" folder
example: (Copy files to and edit the path in the config file)
For EU/NA: Tera\Client\Binaries\Tera.exe --> Tera\Client\Tl.exe
For TW: Tera\Binaries\Tera.exe --> Tera\Tl.exe
etc.
Download Link:
https://mega.nz/file/F01DQQBK#mypZPK...rylJxHAMKnadlo
Last edited by P5yl0; 13-01-21 at 08:31 PM. Reason: Re-Upload Launcher
Thanks!!!
ru client not supported?
@P5yl0 excause me ,could you tell me which version of chinese client(main land ,not 'taiwan' 's client ) does this emu lancher support?
i have the chinese client 1.98 1.76,1.14,
and a client which have 43 files : 42 of them namedTERA_SHOCK.z42 ,500MB ,
the 43 one named TERA_SHOCK.zip 335.7mb
maybe this can login??
Launcher should work with all Client Versions listed above...
EU, NA, RU, KR, CN, TH, working!
(JAP not tested)
launch process is always the same on all versions,
its just a different folder tree between the clients...
cause of this there are 2 TL.exe files for the starter it just has a max limit of ~5 languages supporting
so i splitted them in 2 variants... one for eu/na/ru and one for asian languages
i will add the tl.exe files in a later version into the launcher file so theres no need to do anything just copying the launcher.exe into the right folder...
Updated!
wow,Can it be Korean or Chinese?
latest NA, RU got error: endPopup(131347)gamestr
hmm okay thnx for the notice..
ill check that on the weekend...
for now just took a look on the source and i have that error already i there ...
so far on the messages i had reconstructed that already when played with the files...
marked it back then already as (NA) only error, cause it didnt happened on other clients...
if you havent done something on the files, could be that they have done it with the latest patch..
maybe tl.exe (gamestr) changes...
Code:if (data.Message == "endPopup(131347)") { SimpleLogger.Error($"[NeoLauncher]-> { data.Message } Unknown ?!? GameString Problem, Game Client Crashed! (NA)"); SetLabelStatusText($"Ouuppss, there is a Problem with your GameString Settings! Game Client Crashed."); return (IntPtr)1; }
Cant find any errors,
EME 88.05 works fine..
RU cant check but i think should work too
up to.. EU works to...
Version: Live-90.02 GF #10 (Gold)
so there should no problems with any client from 88 ->90
the direectroy tree and files between those client havent changed..
i think you have some corrupted files or any miss configuration.
![]()
i had some time so i tested now with 90.02 p-server ^^
the launcher works without problems..
![]()
I really don't understand the text tutorial. and I have problems I do something wrong and I don't know what it is, I followed the steps as I understood in the text but I can't enter. could you help me please?the videos you have do not have the same files as your current server.
- - - Updated - - -
https://prnt.sc/rwxxla I cannot enter the server :( @P5yl0
you error is on server side... check out what the gameserver says when you try to enter,
cause the launcher is just to startup the game till the serverlist screen where you are...
from that part the connection goes to the gameserver,
be sure you use in launcher same crypt mode for user login(password) as the gameserver (normaly "md5")
if you use launcher > authorization there shopuld be no problem cause the check already happens in the launcher then...
if you dont use web authorization be sure you have the correct crypt mode and a existing user (account) in your mysql database...
and the correct data (ip) in your serverlist files to connect to a gameserver
@P5yl0 Could you make a current video tutorial please but with everything necessary for a novice like me to do it, I would appreciate it quite a lot..
Last edited by gatitoxp; 14-04-20 at 05:59 AM.