1366 + 1402
Server Rules

Read and Follow The Server Rules Provided Below!

There must be a level of respect when commenting on World Chat. Friendly banter is okay, but making inflammatory statements, creating conflict, and having overall aggressive behavior will not be tolerated. This includes, but is not limited to:
  • Attacks on a person’s race, nationality, and/or orientation
  • Slander towards an alliance
  • Personal attacks (regardless if the statements are true, half-true, or elaborations)
  • Unsubstantiated accusations

    • Harassment, unwanted sexual advances, propositioning, and/or any other behavior of an unwanted sexual nature are also strictly prohibited. This applies to World/Server Chat as well as Whisper.
    Toxic behavior such as this will result in the member’s expulsion from their alliance for a two-week probationary period. If the behavior continues, the Server Council will convene regarding the behavior, then designate and enforce punishment. We should all work together to keep World Chat friendly and create a strong and united server that is enjoyable for everyone.
    Server 1366 + 1402 is a permanent NAP (Non-Aggression Pact) server and therefore does NOT follow the Evony event calendar. The Monarch Competition KE (Kill Event) is not in effect.
  • Attacking and/or scouting any keep (castle) or subordinate city (sub) that belongs to a player in an alliance, or attacking/scouting any alliance city, is strictly prohibited. If a player desires this protection, they may join an alliance or spend 200 gems to create their own alliance.
  • If a player in an alliance is attacked, the attacker will either pay compensation or be declared KoS (Kill on Sight) by the Server Council through a mail sent by the ruling King/Queen.
  • If a player must expel their alt/farm from an alliance to plunder, the player must change the name of that alt/farm to prevent other players from attacking it. The name must contain the alliance acronym and the term mini, farm, rss, ore, wood, stone, food, etc. (Examples: SCCrss4Me, NFGMiniDel, PTOFarm1)
  • Any keep that is not in an alliance and does not have the name changed as above is vulnerable to attack.
  • Player owned sub cities must NOT be stolen, regardless whether or not the owner belongs to an alliance. If a player leaves the server and does not give their sub cities away, the alliance is responsible for their distribution.
  • Do NOT attack an NPC sub city if a player is sitting next to it. The player may be leveling Generals or switching sub cities.
    • It is almost impossible to cancel attacks if you are next to a target, so if Player1 attempts to take an NPC sub city while Player2 is in the process of leveling generals, Player1 will be responsible for compensation. Player1 will also need to give the sub back or risk becoming KoS.
  • For the sake of proving ownership, it is beneficial to the player to take a screenshot of their keep next to the sub city before they release it.
  • R5/4s are responsible for kicking sub city thieves from the alliance for a two-week probationary period. If the player continues to steal sub cities and/or does not return the sub city to the rightful owner, they will become KoS.
  • KOS-players lose protection from all server rules. R5/4s are responsible for expelling and/or not accepting the KoS member. If an alliance harbors a KoS member for more than 12 hours, the entire alliance will become KoS.

    • SERVER SUBORDINATE CITY
  • 1366+1402 has multiple subordinate cities which have been donated to the server for general leveling. These sub cities belong to the server and are not to be taken by individual players.
  • If a player takes a server sub city, that player’s R5/4’s must be notified so they can reach out to the player and have them release the sub. If the player does not release the sub city within 24hrs, the player will be considered KoS until they release said sub city.
    • Do NOT attack players in resource tiles, relics, pyramids, and/or barbarian castles; unless that player is KoS or it is during Purge (see Rule 6).
    Barbarians: Do NOT attack Barbarian Castles occupied by an alliance.
    • It is advisable to take a screenshot as soon as you start marching towards a Barb Castle as proof of “ownership.”
    • Attackers are obligated to pay compensation or risk going KoS.
    Pyramids: If you see a player marching to a pyramid, do NOT send a speed march or port next to it to try to claim it.
    • Pyramid theft is responsible for multiple disputes, so it is advisable to take a screenshot as soon as you start marching towards the pyramid.
    • If someone steals your pyramid, inform your R5/4s and provide the screenshot as proof, allowing them to inform the thief’s alliance of the situation. Alliance leadership is responsible for reprimanding the pyramid thief. If pyramid theft becomes habitual, the issue will go to Server Council.
    • The penalty for attacking an occupied pyramid will be twice the compensation to the rightful pyramid owner.
    Relics: Relic theft is also a common problem.
    • If another alliance attacks your relic and kills your troops, the attacker will pay compensation or become KoS.
    • If another alliance takes your relic and there are no casualties, send a mail to the person occupying the relic, as well as your and their R5/R4s.
    • If there is communication in less than 12 hours, the occupier can choose to leave the relic or open a new relic. No harm, no foul.
    • If there is no response within 12 hours, you may attack the relic.
  • If your teammate steals a relic, which you unknowingly occupy, and the rightful owner attacks it, your teammate is responsible for your compensation.
  • If a conflict arises regarding rule breaking, players must try to resolve their conflict at the lowest level possible (player to player). If they are not capable of doing so, the involved alliance’s R5/4s must intervene. If the R5/4s are unable to solve the issue, the Server Council will intervene.
  • “Revenge” is not an approved method of conflict resolution. If a player or their alliance reacts without going through Step 1, they will need to send compensation for the resulting damage or go KoS.
    • Accidental hits are especially NOT a cause for retaliation.
  • Examples of accidental hits include, but are not limited to, taking a NPC city when a player is sitting next to it, hitting one occupied resource tile, hitting one occupied pyramid or one barb castle during their respective events, etc.
  • If a player makes multiple prohibited attacks, it is malicious intent and the player will be KoS.
    • Server versus Server War happens every two weeks. It starts at Friday midnight server time and lasts for 48 hours. PURGE: To prevent giving points to the enemy server, a purge will start at 22:00 server time. Before the start of the purge, all players must have a truce shield (bubble) and recall all troops from relics, pyramids, resource tiles, camps, etc. (anywhere a player can get attacked). THERE WILL BE NO SUB CITY STEALING DURING PURGE.
  • Anybody who is purging WILL add Purge to their Monarch name. (examples: OdinPurge, PurgerDel, PurgeYou)
    • Players may NOT attack anyone with the Purge name format. Members without a bubble and without Purge in their name are vulnerable to attack.
  • If a player has an emergency/ red evony and is unable to bubble, a green bubble and protection will be granted by high exception. This will be communicated in World Chat, on the server council discord, and with as many R4/5’s as possible so an alliance mail can be sent.

    • PURGERS:
  • Purgers may attack all occupied relics, resource tiles, pyramids, etc, after purge has started at 22.00h server time.
  • Castles may be purged from 23.00h server time.
  • Purgers MUST scout an unbubbled player before attacking. This warns the player to bubble if they are online, but also determines if there are troops to kill.
  • Purgeable keeps will not be reinforced from 23.00h server time on, unless they are protected to be green bubbled as per previous point.
  • If the Purger comes across an unbubbled keep that they are unable to attack/rally due to its size, they must inform their R5/4s and post the coordinates to World Chat: Someone will be able to help clear it.
  • In case of a wrongly purged keep, the Purger must compensate the victim and the reinforcer.

    • TIMELINE:
    22.00 Server Time: All Purgers will attack occupied resource tiles, pyramids, relics, camps, etc
    23.00 Server Time: All purgers will attack unbubbled keeps
    00.00 Server Time: SvS Starts
    During SVS-War: There will be a CONTINUOUS PURGE of the 1366 server.

    Any player on the 1366 server who collects resources on the world map or occupies ruins, pyramids, or barbarian castles during SvS may have their resource tiles cleared so the opposing server cannot take easy points. However, 1366 persons will not be purged on the enemy server as positive points can be accumulated strategically from participating in events on the enemy server. Please note this will be subject to review if there is a significant impact on future SVS negative scores or SVS outcomes.
    Players who have their Wonder 1 open will be eligible to be Queen or King of the server. Each person will be Queen/King/Conqueror for two consecutive weeks to qualify for opening their Wonder 2. Conquering throne will be played by ear. Priority goes to players needing to open Wonder 2; however, in the event the enemy throne will be challenging to conquer, an older player can conquer to achieve their fame points. In the event the enemy throne will be almost impossible to conquer, there will be a throne truce.
    • Throne truce will not be determined until the first day of SvS.
    It is preferable for players to have a positive score in SvS when they get their wings; however, up to 15% of the player’s score may be from negative points. If more than 15% of their score is negative points, they will drop to the bottom of the list for taking King/Queenship, even if they have Wonder 1 open.

    Server Subordinate City

    Subordinate City

    Server Subordinate City can be used to increase your general's level and please be careful not to take sub servers, please read RULE 3.

    Location Coordinates:
    X: 344 - Y: 736
    X: 773 - Y: 329
    X: 449 - Y: 946
    X: 1106 - Y: 0049

    Server Time:
    Loading...

    Join our Discord server to stay updated and participate in community discussions!

    Join Discord

    Pinned Videos