How to Install and Run Tibia on Linux

Using Wine without Windows

Contents

1 Disclaimer
2 Overview/Background Information
3 Pre-requirements
4 Installing Wine
4.1 Get to know the environment
4.2 The easiest way (1): yum
4.3 The easiest way (2): apt
4.4. The easiest way (3): emerge
4.5. The easiest way (4): FreeBSD ports
4.6. The easiest way (5): NetBSD packages
4.7 The easy way: rpm
4.8 The hard way: compilation from source
5 Testing Wine
6 Installing Tibia
6.1 Get the latest client from www.tibia.com
6.2 Install Tibia
7 Running Tibia
7.1 First test
7.2 Create a more comfortable way to start Tibia
8 Known Issues
8.1 General warning
8.2 No shadow effects
8.3 Debug assertions occur when closing the client
8.4 Wine is throwing many errors in the console
8.5 Wine crashes when closing the client
9 Troubleshooting
9.1 Compilation fails
9.1.1 Missing dependencies
9.2 Tibia is installed but does not start
9.2.1 "Error 1: Cannot open file: Tibia.dat. Please re-install the program."
9.3 Wine is installed but does not work
9.3.1 Wine is complaining about a missing socket
9.4 Tibia update fails
9.4.1 Tibia is complaining that it cannot delete the old Tibia.exe
9.5 Performance issues
9.5.1 Framerate (fps) is low
1 Disclaimer
You agree that you use these instructions at your sole risk. We provide the instructions, the
software, the game, and all other services "as is". We disclaim all warranties or conditions of
any kind, expressed, implied or statutory, including without limitation the implied warranties of
title, non-infringement, merchantability and fitness for a particular purpose. We do not ensure
continuous, error-free, secure or virus-free operation of the software, the game, or your
account.
We are not liable for any lost profits or special, incidental or consequential damages arising
out of or in connection with the game, including, but not limited to, loss of data, items,
accounts, or characters from errors, system downtime, or adjustments of the gameplay.
Playing Tibia via Wine is not supported. The customer support will most likely not be able to
help you if installing or running Tibia via Wine fails. Please ask on the help board if problems
occur that you cannot fix yourself. Feedback regarding this document, success or failure is
very much appreciated.

2 Overview/Background Information
The Tibia client has been developed for Windows using the DirectX-API. It is not possible to
run a Windows application on a native Linux environment.
Wine is an Open Source implementation of the Windows API on top of X and Unix.
Think of Wine (http://winehq.org) as a compatibility layer for running Windows programs.
Wine does not require Microsoft Windows as it is a completely free alternative implementation
of the Windows API consisting of 100% non-Microsoft code, however, Wine can optionally
use native Windows DLLs if they are available. Wine provides both a development toolkit for
porting Windows source code to Unix as well as a program loader, allowing many unmodified
Windows programs to run on x86-based Unixes, including Linux, FreeBSD, and Solaris.
At this point this how-to steps in and explains how to run Tibia on Linux using Wine.
3 Pre-requirements
• a PC running any x86-based actual flavor of Linux: Fedora (5+), CentOS (5+), SuSE
(10+), OpenSuSE (10.2+), Slackware, Debian (Etch), Gentoo (2006.1+), FreeBSD
(5.5+), NetBSD (3+), or Solaris 86 (9+).
• a working X11-environment. (X11 is a graphical window system)
• a working internet connection
• root access
The installation and configuration of your operating system, including anything except Wine
and Tibia itself, is beyond the scope of this how-to.

4 Installing Wine
Depending on the distribution you are using, there are different ways to install Wine on your
PC. Please study this part very carefully and make sure that you understand what you have to
do before you start to install something. Otherwise you may damage your operating system
environment!
In general there are 4 completely different ways to install Wine:
• using precompiled binaries via rpm/dpkg and an installation system
• using precompiled binaries via rpm/dpkg without an installation system
• compiling from source using a build system
• compiling from the source, doing all work by yourself
yum/rpm

apt/rpm

portage

packages
rpm

apt/dpkg

dpkg

ports

Compile from source

Package available
yast/rpm

Fedora X X X rpm

SuSE X X X rpm

CentOS X X X rpm

OpenSuSE X X X X rpm

Debian X X X dpkg

Slackware X tar.gz

Gentoo X X -

FreeBSD X X tgz
NetBSD X X tgz

Solaris 86 X X tgz

4.1 Get to know the environment

• check if Wine is already installed on your system

 open a shell command prompt (when X is already running, start: xterm, gterm,
kterm, or any terminal of your choice)
 type: which wine↵
 check the output:
➢ if you see something like "/usr/bin/wine", your system already contains a
Wine-installation and you can continue to install Tibia
➢ if you see something like "/usr/bin/which: no wine in
(/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin)", you have to
install Wine from scratch

Now try to figure out which will be the best installation option for you.

• check if your system is using yum

 open a shell command prompt
 type: yum –version↵
 check the output:
➢ if you see something like "2.2.1" (the version does not matter), your
system should be ready for the very-easy-install using yum
➢ if you see something like "bash: yum: command not found", go to the next
test

• check whether your system is using apt

 open a shell command prompt
 type: apt-get↵
 check the output:
➢ if you see lots of text scrolling by, your system should be ready for the
very-easy-install using apt
➢ if you see something like "bash: apt-get: command not found", go try the
next test

• check whether your system is using rpm

 open a shell command prompt
 type: rpm --version↵
 check the output:
➢ if you see something like "RPM version 4.3.3" (the version does not
matter), your system should be ready for the easy-install using rpm
➢ if you see something like "bash: rpm: command not found", go try the next
test

• check wether your system is using dpkg

 open a shell command prompt
 type: dpkg --version↵
  check the output:
➢ if you see something like "dpkg version 1.13.25 (i386)" (the version does
not matter), your system should be ready for the easy-install using dpkg
➢ if you see something like "bash: dpkg: command not found", go try the
next test

• check whether your system is using emerge

 open a shell command prompt
 type: emerge↵
 check the output:
➢ if you see some coloured help text, your system should be ready for the
very-easy-install using emerge
➢ if you see something like "bash: emerge: command not found", go try the
next test

• check whether your system is Linux

 open a shell command prompt
 type: uname -a↵
 check the output:
➢ if it reads “GNU/Linux” near the end, you have a Linux system with none
of the packet management systems we tried out. Please refer to your
systems documentation to find out how to install packages prepared for
your system, or use the manual installation.
➢ if it reads “FreeBSD” at the very beginning, you are ready using the
FreeBSD ports system installing Wine.
➢ if it reads “NetBSD” at the very beginning, you are ready using the
NetBSD packages system installing Wine.
➢ if it reads “OpenBSD” at the very beginning, there is nothing you can do.
Wine is, as far as we know, not ported to OpenBSD yet.
➢ if it reads “SunOS” at the very beginning, there is nothing you can do.
Wine does not support this ancient OS anymore!
➢ if it reads “Sun Solaris” or “Solaris” at the very beginning, there are Wine
packages available at http://winehq.org/site/download for the latest
versions of Solaris. Please try them! However, since we do not have a
Sun Workstation equipped with Solaris to test Tibia running inside this
Wine, you are on your own. Still we would like to hear if you were lucky!
➢ if it reads “AIX” or “IBM AIX” at the very beginning, there is nothing you
can do. Porting attempts have been made, but as far as we know there is
no running Wine yet.
➢ if it reads anything else, feel free to ask us, but in most cases we will not
have more information than http://winehq.org/ has!

4.2 The easiest way (1): yum

This part will only work if your system is using rpm and yum is installed. (RedHat, Mandriva,
CentOS, etc.)
• become root
 open a shell command prompt
 type: su -↵
 enter the root password of your system
• install Wine
  type: yum install wine↵
 check the output and confirm the installation

It is possible that your yum-repository does not contain a Wine package. In this case an error
message will appear
Cannot find a package matching wine
No actions to take
If this is the case, you have to choose the rpm-installation.

4.3 The easiest way (2): apt

This part will only work if your system is using apt. (Debian, Ubuntu, some flavors of
OpenSuSE)
• become root
 open a shell command prompt
 type: su -↵
 enter the root password of your system
• install Wine
 type: apt-get install wine↵
 check the output and confirm the installation

Depending on your operating system you might need to add the Wine-repository to your
/etc/apt/sources.list manually:
• open a shell command prompt
• open /etc/apt/sources.list with an editor (vi, emacs, joe, ...)
• add the following 2 lines to the list of your repositories:
deb http://wine.sourceforge.net/apt/ binary/
deb-src http://wine.sourceforge.net/apt/ source/
• save the changes and exit the editor
• type: apt-get update

Now you can (re)try the steps above and install Wine.

4.4 The easiest way (3): emerge

This part will only work if your system is using emerge. (Gentoo)
• become root
 open a shell command prompt
 type: su -↵
 enter the root password of your system
• install Wine
 type: emerge -a wine↵
 check the output and confirm the installation

Since emerge based systems compile from source, you will have to be patient watching your
system downloading, unpacking, patching, compiling, and installing Wine. Be prepared to wait
up to two hours until everything is finished.
It is a good idea to update your portage tree before starting to emerge Wine

emerge –sync↵
will do the trick!

4.5 The easiest way (4): FreeBSD ports

This part will only work if your system is using ports. (FreeBSD)
There are two ways to install Wine. Let's try the simplest first:
• become root
 open a shell command prompt
 type: su -↵
 enter the root password of your system
• install Wine
 type: portinstall -P wine↵

If your system tells you something like “csh: portinstall: not found”, try
 cd /usr/ports/emulators/wine
 make install

If this fails, too, refer to the “FreeBSD Handbook” on how to install ports and retry the second
step! The “FreeBSD Handbook” is available at http://www.freebsd.org/handbook/index.html
Since ports compile from source, you will have to be patient watching your system
downloading, unpacking, patching, compiling, and installing wine. Be prepared to wait up to
two hours until everything is finished.
It is a good idea to update your ports collection before building Wine. Please consult the
“FreeBSD Handbook” on how to set up and use cvsup!

4.6 The easiest way (5): NetBSD packages

This part will only work if your system is using packages. (NetBSD, sometimes SunOS and
Solaris)
• become root
 open a shell command prompt
 type: su -
 enter the root password of your system
• install Wine
 cd /usr/pkgs/emulators/wine
 make install

If this fails, refer to the NetBSD documentation on how to install packages and retry!
Since packages compile from source, you will have to be patient watching your system
downloading, unpacking, patching, compiling, and installing wine. Be prepared to wait up to
two hours until everything is finished.
It is a good idea to update your packages tree before building Wine. Please consult the
NetBSD documentation on how to set up one of the various ways available for updating!

4.7 The easy way: rpm

This part will only work if your system is using rpm

• download a recent Wine rpm
 go to http://winehq.org/site/download
  choose your distribution (if unsure, use Red Hat)
 choose the right version (if unsure, use Red Hat Linux 9)
 choose the architecture that matches your hardware (if unsure, use i386 - note
that this might affect the performance of Tibia)
 click on the link next to your chosen hardware
 choose a location geographically close to you
 save the file
• become root
 open a shell command prompt
 type: su -
 enter the root password of your system
• install the rpm
 type: rpm -ivh <path to the file that you just downloaded>
 check the output: if no error occurs, you should see a line of hashes ("#") and a
percentage running up to 100%

It might be possible that your system is missing certain dependencies to be able to install
Wine. In this case you have to resolve the problems before you can install Wine. Wine should
not require any packages that are not part of the distribution.

4.8 The easy way: dpkg

This part will only work if your system is using dpkg

• download a recent Wine rpm
 go to http://winehq.org/site/download
 choose your distribution (if unsure, use Red Hat)
 choose the right version (if unsure, use Red Hat Linux 9)
 choose the architecture that matches your hardware (if unsure, use i386 - note
that this might affect the performance of Tibia)
 click on the link next to your chosen hardware
 choose a location geographically close to you
 save the file
• become root
 open a shell command prompt
 type: su -
 enter the root password of your system
• install the rpm
 type: dpkg --install <path to the file that you just
downloaded>
 check the output: if no error occurs, you should see a line stating the package
installed with no errors.

It might be possible that your system is missing certain dependencies to be able to install
Wine. In this case you have to resolve the problems before you can install Wine. Wine should
not require any packages that are not part of the distribution.

4.8 The hard way: compilation from source

This is quite difficult and error-prone if you are new to Linux and never worked with sources
and compilers before. Make sure to read everything carefully and follow all advices
accurately. Otherwise you might damage your system seriously.
 • download the most recent Wine-release
 go to http://winehq.org/site/download
 scroll down to the bottom of the page
 click on the sourceforge.net-link with the description "Our official source release
site." (a new browser-window/tab should open up now presenting the last
releases)
 click on the topmost Download wine-<release>.tar.bz2-link
 choose a location geographically close to you
 save the file
• unpackage, compile and install the sources
 open a shell command prompt
 type: tar xzf ~/download/Wine-*.tar.gz
 type: cd wine-*
 type: ./configure --disable-debug
(Now many lines will be scrolling through your console. No worries, that is
alright.)
 wait until the configure-process has been finished, this might take a while
 check the output:
➢ if everything works fine, you should see "Configure finished. Do 'make
depend && make' to compile Wine." as very last output from configure
➢ if this is not the case (any kind of error occurred), check the
Troubleshooting section for help. Most likely some important
requirements for compiling Wine are missing like gcc (a compiler) or
anything related.
 if no error occurred, type: make depend && make
(Again many lines will be scrolling through your console.)
 wait until the compilation has been finished, this might take several minutes
 check the output:
➢ if everything works fine, you should see "Wine build complete."
➢ if not, check the Troubleshooting section.
 become root, type: su
 install Wine, type: make install

5 Testing Wine
• open a command prompt
• type: wine
• check the output, you should see something like:
Wine 20050524
Usage: wine PROGRAM [ARGUMENTS...] Run the specified program
wine --help Display help and exit
wine --version Output version information and exit
• if any errors occur - check the Troubleshooting section
6 Installing Tibia

6.1 Get the latest client from www.tibia.com

• go to https://secure.tibia.com/account/?subtopic=downloadclient
• read and accept the license agreement
• choose Tibia (for Windows)
• click on the download link and save the file

6.2 Install Tibia

• make sure that X is running

• open a command prompt under X (xterm, gterm, kterm, etc.)
• type: wine tibia*.exe (if necessary, add the path to the file that you have
downloaded)
• if your Wine installation is working correctly, a new window should appear with the
usual Windows options to install Tibia
• follow the instructions and install Tibia
• select "Don't create a Start Menu folder", you will not see it anyway
• deselect the options to create icons, you will not see them anyway
• start the installation
• click "Finish" at the end of the installation process, the Tibia login screen should appear

Congratulations!

7 Running Tibia

7.1 First test

• cd to the directory where Tibia has been installed to:

cd <path to Tibia>
(e.g. cd ~/.wine/drive_c/Program\ Files/Tibia)
Please note that you may have to escape certain characters in the path, e.g. blanks.
• run Tibia
wine Tibia.exe engine 0
Now the Tibia client should start and present you the usual login screen. This might take a
few seconds.

7.2 Create a more comfortable way to start Tibia

• create a start script

 open a text editor (vi, emacs, joe, ...)
 paste the following script to your editor or write something similar yourself:
#!/bin/bash
cd ~/.wine/drive_c/Program\ Files/Tibia
WINEDEBUG=-all wine Tibia.exe engine 0
 (Adjust the path in the line after "cd" as necessary and save the file. The "~" is a
synonym for your home directory. Please note that you might need to escape
certain characters, like the blank in the example above. This can be achieved by
adding a "\" right in front of the respective character.)

• make the script executable

 open a shell command prompt
 type: chmod +x <name of the file that you just have created>
• test the script
 open a shell command prompt
 Type in the name of your script and press enter. Tibia should start now.
• optionally create a link on your desktop to start Tibia with a click
(Depending on your window manager the way to create a starter on your desktop
differs. Usually you have to right-click on a free part of your desktop and choose
something like "create launcher". Fill in the name (Tibia) and direct the launcher to start
your script. When clicking on the newly created launcher, the Tibia client should start.)

8 Known Issues

8.1 General warning

Tibia is a native Windows application. Please note that Wine is still in development (just
entered beta-state) and does not fully implement all Windows functions yet. Chances are high
that you may stumble on more or less serious problems:
• causing your client to crash
• distorting/screwing the display of certain parts of the Tibia client
• distorting/screwing the display of certain parts of your X window system
• causing certain functions of your operating system to fail
• causing your operating system to hang/crash

Please keep in mind that you use the software at your sole risk, and that these instructions
are provided as is, disclaiming all warranties and conditions of any kind. Playing Tibia via
Wine is NOT supported officially.

8.2 No shadow effects

• Tibia does not display light effects, you see black dots only

This is a known issues and caused by Wine. It is not an error and there is currently no
known way to enable light effects. It might be possible that Cedega (a commercial
branch of Wine with enhanced DirectX capabilities) or future Wine-releases are able to
display light effects.

8.3 Debug assertions occur when closing the client

• It might happen that different debug assertions occur when you log off, close the client,
switch characters, etc.
 This is a known issue and caused by Wine. It is not an error and usually should not
affect the gameplay.

8.4 Wine is throwing many errors in the console

• It might happen that several error messages appear in the console where you started
Tibia.
fixme:richedit: ...
err:menubuilder: ...
err:ddraw: ...
...

These are known issues and caused by Wine. They are generally harmless and should
not affect the gameplay.

8.5 Wine crashes when closing the client

• When closing the client Wine may crash, prompting you to the debug console.

This is a known issue and should not affect the gameplay. Just close the message box
or kill the debug session. Such crashes can be prevented by closing the client via the
exit button.

9 Troubleshooting

9.1 Compilation fails

9.1.1 Missing dependencies

Compiling Wine from source requires to have a few programs installed. If any errors occur
telling you that something is missing, check if the following tools are installed:
• gcc (gnu C compiler)
• automake/autoconf
Usually you will get a rather detailed error message telling you what is wrong. Follow the
given advices.

9.2 Tibia is installed but does not start

9.2.1 "Error 1: Cannot open file: Tibia.dat. Please re-install the program."

You forgot to cd to the directory where Tibia has been installed to. Please type
cd <path to where Tibia has been installed to>
and restart Tibia.
9.3 Wine is installed but does not work

9.3.1 Wine is complaining about a missing socket

This might occur when you compile Wine from source. In this case you might need to start
wineserver prior to running Wine. Example:
wineserver -p
wine Tibia.exe engine 0
The option "-p" runs wineserver as a daemon, allowing you to start multiple Wine sessions
without restarting the wineserver each time you want to use Wine. You might want to add this
line to your Tibia startup script or optionally to your operating system start scripts, e.g.
/etc/rc.local.

9.4 Tibia update fails

9.4.1 Tibia is complaining that it cannot delete the old Tibia.exe

When the client is getting updated, it is likely that the update process fails. The Update
program might be unable to delete the old Tibia.exe before installing the new Tibia.exe. In this
case you have to change to your Tibia-directory manually
cd <path to your Tibia directory>
delete the old Tibia.exe
rm Tibia.exe
move Tibia.bak
mv Tibia.bak Tibia.exe

9.5 Performance issues

9.5.1 Framerate (fps) is low

Using an accelerated driver may improve your framerate. Visit your vendor's website for
further information.