Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
http://steamcommunity.com/app/290080/discussions/4/613936673573696940/
"this is a quote from lord.p"
I have had the same problem. Some DB table have not been closed correctly try this. I hope it helps.
For people which haven’t used the win command for a long time like me a little more detailed explanation:
1. Download the file myisamchk.exe
2. Copy the file into your folder: folder where you have installed LIF and then in the folder
a. \SteamApps\common\Life is Feudal Your Own\daemon\mariadb\data\mysql
3. Win start menu and enter cmd the command window opens
a. Now the old commands you know from DOS "cd" to the correct drive (if you have more than one) cd folder where you have installed LIF and \SteamApps\common\Life is Feudal Your Own\daemon\mariadb\data\mysql
4. Then type ore cope into the command window myisamchk.exe proc.myi -c
You should get following infos:
Data records: 45 Deleted blocks: 1
myisamchk: warning: 1 client is using or hasn't closed the table properly
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check record links
5. Then type in: myisamchk.exe proc.myi –r
6. You get some infos but the most important is “ …- Fxing index 1”
7. You can start to play again :)
"this is a quote from lord.p"
Search for "Paradise Lost" in the server name.
I look forward to seeing you there
Tias
it happens to me a lot of times...
u need to put command in the console:
quit();
then wait until it stop writing, then pres X and close it.
next time when the error normaly appears.. u should be fine
How long do you wait for it to stop running after you type quit();
daemon folder in which root directory?