• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

Compiling TFS 1.6 Compiling

lazarus321

Member
Joined
May 8, 2017
Messages
222
Reaction score
23
I compiled using the release 64x option following this tutorial Compiling on Windows (vcpkg) (https://github.com/otland/forgottenserver/wiki/Compiling-on-Windows-%28vcpkg%29)

When I run the file from the server, this window opens and then it closes, without error. Where can I discover this error?

1722118839084.webp

I noticed that the config.lua file didn't have this part and I added it manually, I don't know if it affects

-- MySQL
mysqlHost = "127.0.0.1"
mysqlUser = "root"
mysqlPass = "xxxx"
mysqlDatabase = "xxxx"
mysqlPort = 3306
mysqlSock = ""
passwordType = "sha1"
 
1- There I see that you did not place your database, look at the line that says mysql:user, password, database.
2- delete conf.lua that you modified and put the one that came by default again.
3- recompile
 
Forget what @lolomix1998 is telling you. The server is not made to only work after source edits. The problem is with your database connection most likely as you have already determined, but its not going to make any difference entering the same exact info you have in your config file to your sources... also tfs stopped using the config.lua to parse this information as of #4642

Now they include a .env file for setting up the configuration directly in the environment variables.

If using the .env file is not resolving this problem I suggest you navigate to your folder, highlight the address in the address bar like so:
1722138377157.webp

and then delete everything there and type in cmd like so

1722138431081.webp

hit enter and it will bring up the cmd prompt, already navigated to the server folder like so

1722138481928.webp

and now you just type forgottenserver and hit enter and it will launch your server with the command prompt as its parent, and thus will not close upon failure, and you will be able to actually catch whatever error is keeping you from connecting.

@lolomix1998 please don't suggest people make source edits when the solution doesn't require it, if you are not for sure yourself, its better to just not answer, as false information can make things worse.
 
It didn't close but nothing happened, it just skipped to the next line.

1722178074362.webp

I couldn't understand what to do with this part of the .env file. I put this file in the root and configured it, but nothing happened.

1722179931672.webp

I tried to compile for Win32 to see if it would work but this error appeared
1722178956498.webp

1722183651473.webp

When I tried to compile on Win32 to test this error appeared

1722188180595.webp
 
Last edited:
Olvídate de lo que te dice @lolomix1998. El servidor no está diseñado para funcionar solo después de editar el código fuente. El problema probablemente esté en la conexión a tu base de datos, como ya has determinado, pero no hará ninguna diferencia ingresar la misma información exacta que tienes en tu archivo de configuración en tus fuentes... además, TFS dejó de usar config.lua para analizar esta información a partir del n.° 4642.

Ahora incluyen un archivo .env para configurar la configuración directamente en las variables de entorno.

Si usar el archivo .env no resuelve este problema, le sugiero que navegue a su carpeta y resalte la dirección en la barra de direcciones de la siguiente manera:
View attachment 86315

y luego borra todo lo que hay allí y escribe cmd así

View attachment 86316

Presione Enter y aparecerá el símbolo del sistema, ya navegó a la carpeta del servidor como se muestra a continuación.

View attachment 86317

y ahora simplemente escribe forgottenserver y presiona enter y lanzará tu servidor con el símbolo del sistema como su padre, y por lo tanto no se cerrará en caso de falla, y podrás detectar cualquier error que te impida conectarte.

@lolomix1998 por favor, no sugiera a las personas que realicen ediciones de código fuente cuando la solución no lo requiere, si usted mismo no está seguro, es mejor simplemente no responder, ya que la información falsa puede empeorar las cosas.
This was suggested by me, for the reason that I had that same problem recently and managed to solve it just as I mentioned. If it was wrong to try to help with something, apologies to everyone
 
It is, work now. Thanks Nekiro.

When I log into the client this msn appears, it's not a function of the compilation, right?

1722205315813.webp
 
Last edited:
This was suggested by me, for the reason that I had that same problem recently and managed to solve it just as I mentioned. If it was wrong to try to help with something, apologies to everyone

It's not wrong to try to help, but to provide false information as if it were fact is the issue. When you do that it causes a lot of problems, not the least of which is having someone beat their head against the wall trying to figure out why something works for someone else but not them, its very discouraging. I don't know how your problem could have ever been resolved doing as you said you were doing, because its literally no different than having the same information in the config or the env.


It is, work now. Thanks Nekiro.

When I log into the client this msn appears, it's not a function of the compilation, right?

View attachment 86330

This issue can either be database or the client. I don't know what client you are using, but if you try with the default tibia client there should be no problems. With OTC there is a guide on how to login that can be found here OTC-TFS LOGIN GUIDE

If you still can't get logged in, then it could be your version of MariaDB or w/e, and here is the code change that would enable you to get past the error here on TFS GITHUB

Anyways, please mark Nekiro's post as the solution, so it is clear to others who visit this thread, how to solve this problem.
 
It is, work now. Thanks Nekiro.

When I log into the client this msn appears, it's not a function of the compilation, right?

View attachment 86330
Malformed session key means client sent session key that was not properly base64 encoded.

Make sure you are using the correct client version, your client looks like otc it may be not compatible, because in previous protocols session key was not being sent as base64 encoded string, but plain text.
 
Last edited:
Back
Top