Life is Feudal: Your Own Dedicated (HOME HOST) Guide 2017

[Bohica]

Life is Feudal Dedicated Server Setup 2017
Recommendations on the server specs:
At least 8GB to 16GB RAM
Intel i7 2015 model or greater
250GB+ SSD storage device

Step 1: Download and Install Steam & Life is Feudal Dedicated Server.
(you can log in with your account on steam on the dedicated computer, download the dedicated server and then log out. No need to buy 2 copies of the game.)
*must have at least access to a steam account that has purchased the game*

(It's "ideal" to install steam on the desktop of the dedicated machine for easy access to the directory later on.)

Step 2: Download and install MariaDB 10.2 x64.msi (https://mariadb.org/)
Choose these options!
Database Password: <CreateAPassword>
Process: MySQL
Check: "Access Root Remotely"
Format: UTF-8

Step 3: In the Steam folder, open “\SteamApps\Common\Life Is Feudal Your Own Dedicated Server\Docs\config_local.cs” with Notepad++ (https://notepad-plus-plus.org/download/v7.4.2.html)
Make the following changes:
Server: "127.0.0.1:3306"
Password: <SamePasswordFromStep2>
Save it!

Step 4: Copy the edited config_local.cs and paste it into main server directory - (\SteamApps\Common\Life Is Feudal Your Own Dedicated Server\)

Step 5: In the Steam folder, open “\SteamApps\Common\Life Is Feudal Your Own Dedicated Server\Config\world_1.xml” with Notepad++.
Configure this file to the server settings of your liking.
Save it!

Step 6: Click on Start menu, search MariaDB > Right click and click "Open File Location". Keep this open for now.

Step 7: Click on Start menu and search for "HeidiSQL", open it.
Create a new session called “LIF”.
Click on "Prompt for Credentials"
Input Password: <PasswordFromStep2>
Click the “Open” button
Click "Login"

Step 8: In the white space area, Right Click > Create New > Database
Name Database: lif_1
Collation: utf8_general_ci
Right Click (in the white space again) > Refresh

Step 9: In the Steam folder, open “\SteamApps\Common\Life Is Feudal Your Own Dedicated Server\Docs\my.ini” with Notepad++
Copy the block of text in this “my.ini” file.

Step 10: Switch to the opened MariaDB file location window we had opened earlier. (C:\Program Files\MariaDB 10.2\data)
Paste the contents of the copied "my.ini" text into the MariaDB my.ini file in the [mysqld] section(above the [client] tag) !!! Remove any duplicated lines. Should only be 1 or 2 duplicates. !!!
Save it!

Step 11: In the Steam folder, open “\SteamApps\Common\Life Is Feudal Your Own Dedicated Server\SQL\new.sql” with Notepad++.
Copy all the contents of this document and paste it in the HeidiSQL database “Query” tab on the top right of the screen in database "lif_1" that you created earlier.
Paste the copied text into the blank query window.
Click the blue down arrow, next to the blue “Go Arrow” button and change to “Send Batch In One Go”.
Click the “Go Arrow” button to run the batch.

Step 12: Create a static IP address in your router for the dedicated machine so that it has a fixed IP address in the routing table pool. (https://kb.netgear.com/25722/How-do-I-reserve-an-IP-address-on-my-NETGEAR-router)

Step 13: In your Router configuration, find the "Port Forwarding" settings and create a forwarding rule to the static IP address you set in step 12 for the following ports:
28000-28003 UDP and TCP
(NOTE: The ports to forward are the ones you set in your “\SteamApps\Common\Life Is Feudal Your Own Dedicated Server\Config\world_1.xml”)

Step 14: Create a server start shortcut - “\SteamApps\Common\Life Is Feudal Your Own Dedicated Server\ddtcd_cm_yo_server.exe” and click “Send to Desktop”.
Next, on the desktop, right click “ddtcd_cm_yo_server.exe” shortcut and click “Properties”.
Change the “Target” to include “-world 1” at the end. Example: "C:\Program Files (x86)\Steam\SteamApps\common\Life is Feudal Your Own Dedicated Server\ddctd_cm_yo_server.exe" -world 1

Step 15: Start Life is Feudal Dedicated Server via the desktop shortcut created in step 14
The server will attempt to connect to the database and White/Green/Yellow/Red text will fly by in the server window. As long as this window stays open, the setup has been completed successfully.

Let the server run at least 5-10 minutes the first time before the name shows up on the Steam server list. (You will know the server is done loading when you see the following line, "Steam Initialized."

If you get a bunch of red text and the window immediately closes, something is wrong and previous Steps need to be verified.
There is a log file in the “\SteamApps\Common\Life Is Feudal Your Own Dedicated Server\Logs” folder that may contain some useful information to help troubleshoot.

Exiting/Shutting down the server
To shut down the server gracefully, in the Server console window, type quit();

If you are having issues getting others to connect to your server, please verify your ports are properly forwarded in your router.

[Blade57]

I keep getting this Error/Warning over and over again --- WARN 2018-02-23 06:44:01.194 {} <<Thread>> [316850] DB::RS(1 ms) select ID, TicketID, ActionType, ProducerCharID, GuildID, CharID, GuildName, GuildTag, GuildCharter, GuildTypeID, CharIsKicked, CharGuildRoleID, ^OtherGuildID, StandingTypeID, UnmovableObjectID, ClaimID, HeraldryID, CanEnter, CanBuild, CanClaim, CanUse, CanDestroy from guild_actions_queue where OwnerConnectionID = CONNECTION_ID(); [T:DBIGuildsProcess:0x2D04] ---

[GamerTeah]

^^) Thanks again Still works perfectly

[Yuri]

Originally posted by Blade57 (Caboose):

I keep getting this Error/Warning over and over again --- WARN 2018-02-23 06:44:01.194 {} <<Thread>> [316850] DB::RS(1 ms) select ID, TicketID, ActionType, ProducerCharID, GuildID, CharID, GuildName, GuildTag, GuildCharter, GuildTypeID, CharIsKicked, CharGuildRoleID, ^OtherGuildID, StandingTypeID, UnmovableObjectID, ClaimID, HeraldryID, CanEnter, CanBuild, CanClaim, CanUse, CanDestroy from guild_actions_queue where OwnerConnectionID = CONNECTION_ID(); [T:DBIGuildsProcess:0x2D04] ---

@Blade57 ever figure this out? :(

[Blade57]

unfortunatly not

[Trackhe]

When i do step 10, my mariadb not start anymore. then innodb_file_format=barracuda block the start. i dont know why and i dont find any solution.
my MariaDB version 10.3.8

my solution i use mariadb 5.5

[Wulf]

Awesome guide... worked for me... thanks. I'm left wondering though, why does this process always seem to change? This makes the 3rd or 4th different process for setting up a dedicated server that I've had to use since YO came out years ago, none of my old references/videos/guides work anymore.

[Wulf]

OK, it's for sure working but all I see is "ERRR... syntax error...dumpClientInfo" on the server log, how long is this supposed to go on for?

*edit - well, it does work, but the ERRR's are indefinite. I've tried this a few times now and it happens everytime.

[Hammer]

Got it all running thanks to this guide, you rock dude!

[Jebbus]

Hello! I did this but get error: WARN 2018-09-20 15:21:07.561 {} <> [0] Warning - Last tick took 423 (>64) ms!
core/scripts/server/server.cs (0): Unable to find function destroyWorld
INFO 2018-09-20 15:21:07.561 {01} <onExit> [1] The server has been shut down!

[Jebbus]

Sorry for my last post. I found the problem. The pasword on Config_local.cs wossnt the same as in HeidiSQL's pasword.

[al_vr]

step 11 doesnt work !!! "(1064): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 3 */"

[TyRao]

Had a little issue getting MariaDB. Followed the Process through. Once I started the server up it stopped with the following!

WARN 2019-01-27 17:29:43.087 {} <<Thread>> [] DB::noRS(0 ms) COMMIT; [T:DBIGuildsProcess:7876]6]
WARN 2019-01-27 17:29:48.088 {} <<Thread>> [] DB::noRS(0 ms) START TRANSACTION; [T:DBIGuildsProcess:7876]
WARN 2019-01-27 17:29:48.089 {} <<Thread>> [] DB::noRS(0 ms) UPDATE guild_actions_queue set OwnerConnectionID = CONNECTION_ID(), OwnedTimestamp = CURRENT_TIMESTAMP() where OwnerConnectionID = 0 limit 10; [T:DBIGuildsProcess:7876]
WARN 2019-01-27 17:29:48.090 {} <<Thread>> [] DB::RS(1 ms) SELECT `ID`, `TicketID`, `ActionType`, `ProducerCharID`, `GuildID`, `CharID`, `GuildName`, `GuildTag`, `GuildCharter`, `GuildTypeID`, `CharIsKicked`, `CharGuildRoleID`, `OtherGuildID`, `StandingTypeID`, `UnmovableObjectID`, `ClaimID`, `HeraldryID`, `CanEnter`, `CanBuild`, `CanClaim`, `CanUse`, `CanDestroy` FROM `guild_actions_queue` where OwnerConnectionID = CONNECTION_ID() ORDER BY `ID` [T:DBIGuildsProcess:7876]
WARN 2019-01-27 17:29:48.090 {} <<Thread>> [] DB::noRS(1 ms) COMMIT; [T:DBIGuildsProcess:7876]6]

Any Idea's?

[Bohica]

MariaDB version needs to be 5.5

[TyRao]

Originally posted by Bohica:

MariaDB version needs to be 5.5

It is

[Trinan]

Originally posted by Blade57 (Caboose):

I keep getting this Error/Warning over and over again --- WARN 2018-02-23 06:44:01.194 {} <<Thread>> [316850] DB::RS(1 ms) select ID, TicketID, ActionType, ProducerCharID, GuildID, CharID, GuildName, GuildTag, GuildCharter, GuildTypeID, CharIsKicked, CharGuildRoleID, ^OtherGuildID, StandingTypeID, UnmovableObjectID, ClaimID, HeraldryID, CanEnter, CanBuild, CanClaim, CanUse, CanDestroy from guild_actions_queue where OwnerConnectionID = CONNECTION_ID(); [T:DBIGuildsProcess:0x2D04] ---

Get the same error, who has the solution ?