Funat Server

Description

This repository saves the server made for a Project of Investigation for my highschool. It is based on SaltyEmu. Also the client for which it is thought is for Funat Client.

How to make it work

What I used

I used Visual Studio Community 2019 and remember that this project uses .NET Core 3.1.

Also for the database part it only works with Microsoft SQL Server (only tested in the Developer Edition of 2017).

Setting up the database

Once you got the editor or the terminal to build the Login Server or the World Server, if you run one of them, they will produce an error.

This happens because it has generated the configuration file with default values, which does not have the correct credentials to connect to the database.

This configuration file is different for each server, and can be found in the "Config" folder in the same folder as the executable (it is in YAML format).

Once the server gets the correct credentials it should set up the database automatically and not show any error.

Important notes

Login Server using too much resources

If you think that the Login Server is using too much resources define the ProcessorsToUse to the number of logical processors you want it to use for Hashing the passwords (can be found in the Config folder YAML).

World Server with increasing memory usage without meaning

World Server has a memory leak relationated with the Session of players, causing on the long run to "explode", so watchout with making a lot of connections without restarting the World Server.

Updating Server.SharedThings in the Client too

If you update Server.SharedThings and want to "export" the changes to the Client, you should replace the old Server.SharedThings.dll in the Client for the new one. Also, because of its use of MessagePack it requires of generating a pre-generated code. To generate it:

1. Open the CodeGenerator (inside the Unity Editor) "Window -> MessagePack -> CodeGenerator"
2. Fill the first parameter with the csproj or directory of Server.SharedThings (if you have any folder with spaces in the name put quotation marks at the beginning and end of the path).
3. Fill the second parameter -> MessagePackGenerated.

Talking about the architecture

It is really simple and I am aware that things like this are horrible:

• Hardcoded IP and Port for World Server.
• No direct connection between Login Server and World Server, making the redirection of the connection between them difficult.
• Not saving the Session IDs in a cached server like Redis.

But I did not have time to do it all, I had a limited time (studies, date limit, etc.).

Also here is a preview of the architecture between the client and the servers (sorry it has some gibberish in Spanish, it is recycled from the writen part for the highschool).

Known errors

There are problems for which I also did not have time to fix (probably I can not list all of them):

• The possible incorrect implementation of LazyLoadingProxies in the database, that caused some unexpected responses or conflicts with the Database.
• Not detecting inactivity because lack of time to implement it.
• To fix MovableComponent.cs phyisics.
• Auto regulation of the parameters of Argon2 hashes on the long run.
• World Server memory leak.