This set of rules is an addition to the General Terms and Conditions of Travian. You should familiarize yourself with the General Terms and Conditions to verify what is allowed and especially consult them in the case of an account that has been banned for a violation of the rules. §7 of the General Terms and Conditions is especially important!
§1 Password, Registration & ownership
§1.1 Registration
The e-mail address used for the registration of an account must be under the personal and exclusive control of the person who registered the account. The person owning the e-mail address used to register an account is considered the owner of the account, regardless of any other personal or alliance agreements. The owner of an account is fully responsible for all actions taken with the account.
§1.2 Password
The owner of an account may not transfer the password of an account to any person playing on the same game world. Additionally, choosing the same password on the same game world as another person is illegal; any of these actions is considered multiaccounting, as defined in these rules.
However, it is permissible to transfer the password of an account to a person or persons playing on different game world (or not playing at all) in order to play a single account together.
There is no compensation for damages done by someone knowing the password for an account. The Travian Team reserves the right to deny service features and/or charge the account in question for illegal password sharing. Furthermore an account that uses an insecure password that can be easily obtained or guessed does not qualify for compensation in case of damage to the account.
The person receiving the password is subject to the rules of Travian as well as the General Terms and Conditions.
§1.3 Passing on accounts
In order to transfer an account to a new owner, the current owner must send an e-mail message to admin@travian.com from the e-mail address currently registered for the account. The e-mail must contain the following information:
1.The game world on which the account resides
2.The nickname of the account
3.The e-mail address of the new owner.
In order to switch an account with a person on the same game world, both persons must request the e-mail change as described above and request the password for their new account via the password retrieval function.
§2 Sitting & same pc usage
§2.1 Sitting
Every player has a right to name two sitters who may administer the account during an owner's absence. Sitters must play the account they are sitting to the account’s full benefit. You may not use the sitting function to attempt 24/7 playing.
Permanently sitting an account for a player that is absent for more than 2 weeks is not allowed. Foreseeable periods of absence longer than two weeks must be reported to a Multihunter before the departure of the owner.
There is no compensation for damages done by a sitter. Owners of an account are fully responsible for the actions of any sitters for their account. In the event that sitters of an account do not follow these rules and the General Terms and Conditions of Travian, both the account owner and the sitter may be punished.
The sitter of an account must sit the account using the account sitting function in game. The sitter of an account may not tend to an account by logging on with the password of the account they are sitting. (§1.2).
§2.2 Same pc usage
If there are two or more players using the same computer and playing on the same game world, all affected accounts must be listed in the profile by using the "PC use with another player" function of Travian. Abuse of this function is punishable.
Playing on different computers on the same network does not qualify as "same pc usage".
Players using the same computer and wanting to access each other's account must use the sitter function.
Read §3.2 for details about limitations for resource transfers.
§3 Resource transfers
Every account has to be played to its own benefit and may not be used only to support another account. Being blackmailed into sending resources exceeding the hourly production as described below is not considered a benefit to the account.
§3.1 General
In any 24 hour period, regular lopsided transfers with a specific other player may only equal one hour of resource production, including marketplace transactions. One hour of resource production is the gross sum of all resource productions of all villages without subtracting the upkeep for troops.
The aforementioned amount of resources must be split in cases of multiple regular lopsided transfers with specific players. The size of the affected accounts does not matter.
If your troops are reinforcing another player’s village which get attacked, you are allowed to send enough crops to that player to feed your troops. Normally, a sufficient and allowable amount of crops is enough to keep the troops alive for another 24 hours.
§3.2 Sitting & same pc usage
You may not make lopsided transfers of resources to another player entered as ‘same pc usage’.
Accounts that are connected by the sitter function may not make lopsided transfers, either. It does not matter whether an account is sitter or sitted.
Resources may only be traded at a ratio of 1:1 and the resource transfer has to be finished within 48 hours. An exception to this rule is the sending of crops to feed troops that are reinforcing another village which get attacked. You may transfer enough crops to feed your troops that are reinforcing another village. These transfers should be considered rare exceptions and must stop after 3 days from the first delivery of crops.
In the event of a one-sided transfer, you should wait 48 hours after the last lopsided transfer has been successfully delivered before connecting with each other using the sitter function or ‘same pc usage’.
Additionally, you must wait 48 hours before making a lopsided transfers after canceling sitter status or ‘same pc usage’.
§3.3 Wonders of the World
The only exception to the afore mentioned rules applies to builders of wonders of the world who actually participate in the race to the level 100 wonder of the world. Neither the builders nor the suppliers are bound by the transfer limits.
