Package Details: tibia latest-1

Git Clone URL: https://aur.archlinux.org/tibia.git (read-only, click to copy)
Package Base: tibia
Description: Fast-paced free massively multiplayer online role-playing game
Upstream URL: http://www.tibia.com
Keywords: cipsoft mmorpg
Licenses: custom:CipSoft
Submitter: Cameri
Maintainer: seds
Last Packager: seds
Votes: 13
Popularity: 0.016906
First Submitted: 2015-11-09 06:01 (UTC)
Last Updated: 2025-08-30 20:31 (UTC)

Pinned Comments

seds commented on 2025-08-30 20:37 (UTC)

I've made some changes to this packages, and hopefully this works for everyone. I've added a few optional dependencies which namcap raised and changed how we deal with installing the package.

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 Next › Last »

mateusfccp commented on 2017-02-11 15:02 (UTC)

When trying to build I get this: ==> Criando o pacote: tibia 11.04.4347-1 (sáb fev 11 12:59:51 BRST 2017) ==> Verificando as dependências de tempo de execução... ==> Verificando as dependências de tempo de compilação... ==> Obtendo fontes... -> Baixando tibia-11.04.4347.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 65.2M 100 65.2M 0 0 1228k 0 0:00:54 0:00:54 --:--:-- 936k -> Baixando agreement.php... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1920 100 1920 0 0 3824 0 --:--:-- --:--:-- --:--:-- 3824 -> Encontrado tibia-starter.patch ==> Validando source arquivos com sha256sums... tibia-11.04.4347.tar.gz ... FALHOU agreement.php ... FALHOU tibia-starter.patch ... Passou ==> ERRO: Um ou mais arquivos não passaram na verificação de validade! It fails on sha256sums validation.

TrialnError commented on 2017-01-20 16:51 (UTC)

After testing various enviroment variables and the FAQ entry it still didn't work. I decided to use chmod and chgrp (altough I don't like the solution that much), to give the group "games" write access to /opt/Tibia. So make sure your user is listed with the group, or adjust the PKGBUILD and change the group to users or whatever. Best regards

semeion commented on 2017-01-20 15:19 (UTC)

Okay mate! I will wait, thank you very much!

TrialnError commented on 2017-01-20 15:09 (UTC) (edited on 2017-01-20 15:13 (UTC) by TrialnError)

I think, this sounds like a plan. Will work on it now. But cannot promise anything, as the FAQ entry seems for the old client And regarding your previous post. Yes, Steam does everything in $HOME. The taboo I mentioned just applies for pacman packages. On install those, $HOME shouln't be touched at all :) What the program itself does is not of concern.

semeion commented on 2017-01-20 15:04 (UTC)

@TialnError I think have a way to solve this problem. Tibia have a commandline option to change the place to save the config file. Maybe can be necessary make some patch to run tibia using this commandline option changing the path to $HOME/.tibia Reference doc: http://www.tibia.com/support/?subtopic=faq&question=specificdirectory What do you think about?

semeion commented on 2017-01-20 13:45 (UTC) (edited on 2017-01-20 13:46 (UTC) by semeion)

Okay mate, but what can be done to solve this problem? I don´t think is a good idea run tibia using superuser/root privileges. I said about use /HOME/.tibia because Steam platform install his things in /HOME/.steam, but in fact i don´t know if it is the best solution. Well, i will follow your package receiving notifications, i have somes accounts in tibia and could be nice have this game in aur. Btw, i would like to talk thanks you for try put this game here in AUR. Tibia is a nice game.

TrialnError commented on 2017-01-20 13:29 (UTC)

This cannot be done. It is an absolute taboo to create or install files in $HOME

semeion commented on 2017-01-20 13:24 (UTC)

So, the solution could be modify the PKGBUILD to install tibia in /HOME/.tibia?

TrialnError commented on 2017-01-18 17:50 (UTC)

Had the time to take a further look, and despite my earlier assumption, it is a packaging problem. The files in /opt belong to root, and starting it as the normal user doesn't allow the creation of the config file, which is the reason why it fails.

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 Next › Last »