Создать новый документ

Заголовок вашего документа (будет отображаться как H1)
URL-дружественное имя (без пробелов, используйте дефисы)
Путь, где создать документ (опционально, используйте прямые слеши для создания подкаталогов)

Переместить/Переименовать документ

Текущее расположение документа
Новый путь для документа (включая слаг)
Это изменяет только путь документа и не изменяет заголовок документа (заголовок H1).

Удалить документ

Вы уверены, что хотите удалить этот документ? Это действие нельзя отменить.

Предупреждение: Если это папка, все содержимое, включая подпапки и документы, будет удалено.

Message

Message content goes here.

Confirm Action

Are you sure?

Вложения

Разрешенные типы файлов: jpg, jpeg, png, gif, svg, webp, txt, log, csv, sfd, zip, pdf, docx, xlsx, pptx, mp4 (Макс: 10MB)

Файлы документа

Загрузка прикрепленных файлов...

История документа

Предыдущие версии

Loading versions...

Предпросмотр

Выберите версию для предпросмотра

Настройки вики

Язык пользовательского интерфейса
Определяет, какие сообщения журнала записываются в консоль (debug, info, warn, error)
Количество версий для хранения для каждого документа. Установите 0, чтобы отключить версионирование.
Максимально допустимый размер файлов для загрузки в МБ.

Управление пользователями

Добавить нового пользователя

Оставьте пустым, чтобы сохранить текущий пароль
Пользователи с этими группами могут получать доступ к ограниченным разделам.

Определите правила доступа на основе путей для разделов вашей вики. Правила оцениваются по порядку. Побеждает первое совпадение.

Активные правила

Импорт файлов markdown из ZIP-архива. Файлы будут обработаны и сохранены в соответствующей структуре документов. Структура каталогов в ZIP (категория/подкатегория) будет сохранена в вики.

Загрузите ZIP-архив (сжатый файл), содержащий файлы markdown (.md) для импорта.

Создание и управление резервными копиями данных вашей вики. Резервные копии включают все документы, изображения и файлы конфигурации.

Доступные резервные копии

Загрузка резервных копий...

Добавить/Редактировать правило доступа

Выбрано: /

Добавить колонку

SERVER 98 ALLIANCE AGREEMENT

Rules of interaction between alliances and players of Server 98.

по русски
orignal site

INTRODUCTION

This agreement establishes the rules of interaction between the alliances and players of Server 98.

The purpose of this agreement is to preserve order, trust, server stability, and readiness for cross-server events.

This agreement enters into force after it is confirmed by the leaders of the top-5 alliances.

SECTION 01. GENERAL PRINCIPLES

All participants of this agreement must act in good faith, avoid provoking internal conflicts, and resolve disputes through direct dialogue between leaders.

No alliance, leader, or representative may speak on behalf of all participants of the agreement without the direct consent of all parties.

Any rule that affects the interests of a specific alliance cannot be adopted without that alliance’s consent.

SECTION 02. NAP-10 / NON-ATTACK PACT OF THE TOP-10

NAP-10 means Non-Attack Pact: a non-attack agreement between the alliances ranked in the top-10 of the server’s overall alliance ranking.

NAP-10 is not an alliance, a unified coalition, or a governing body of the server. Participation in NAP-10 only means the obligation to follow the non-attack rules and the other terms of this agreement.

NAP-10 includes the alliances ranked from 1st to 10th in the overall alliance ranking.

If an alliance is in the top-10, it must comply with the NAP-10 rules.

If a new alliance enters the top-10, it receives NAP-10 protection only after accepting the terms of this agreement.

If an alliance temporarily drops out of the top-10, its status may be separately discussed by the leaders of the top-5 alliances.

SECTION 03. ATTACK BAN

Any attacks between alliances under NAP-10 are prohibited.

Attacks on players, bases, troops, resources, and any other game objects of alliances under NAP-10 are prohibited.

Tile attacks are prohibited across all of Server 98 for all players and alliances without exception, regardless of alliance ranking or participation in NAP-10.

Any attack on a tile is considered a violation of the general server rules.

Any attack without prior coordination between alliances under NAP-10 is considered a violation of this agreement.

SECTION 04. BAN ON PLAYER POACHING

The ban on player poaching applies only between the top-3 alliances in the overall server ranking.

Poaching players from top-3 alliances is strictly prohibited.

A player may move from one top-3 alliance to another only by the player’s own personal initiative.

Pressure, persuasion, promises of rewards, or any other actions aimed at weakening another top-3 alliance are prohibited.

If a player requests a transfer on their own, the receiving alliance must be ready to prove that the initiative came from the player.

This ban does not apply to alliances below the top-3 unless otherwise separately agreed by all top-3 leaders.

SECTION 05. SHARED BLACKLIST

If a player behaves toxically, insults members, provokes conflicts, or violates alliance rules, that player may be removed from the alliance.

At the request of one of the alliances, such a player may be added to the shared blacklist.

Before adding a player to the blacklist, any alliance has the right to request evidence of the violations.

If a blacklisted player was accepted into an alliance by mistake, independent attacks against that player are prohibited. The alliance that notices the situation must notify the leader of the alliance that accepted the player.

The alliance has 48 hours from the moment the notification is sent to remove that player. If the notification is read and ignored, or if no decision is made within 48 hours, attacks are allowed only against that specific player’s base.

Tile attacks remain prohibited under all circumstances, even against blacklisted players, violators, or alliances not included in NAP-10.

SECTION 06. CHANGE OF ALLIANCE LEADER

A change of alliance leader does not cancel previously accepted agreements.

All agreements confirmed by the previous leader remain fully valid.

The new leader assumes responsibility for complying with this agreement.

SECTION 07. TRUCKS, CONTAINERS, AND CONTESTED OBJECTS

Trucks, containers, and similar contested game objects may be attacked by players and alliances.

These objects are considered free game activity and are not covered by the attack ban.

Exception: after an official cross-server battle is announced and cross-server raids are opened, attacks on trucks, containers, and similar objects between alliances of Server 98 are prohibited.

The tile attack ban always applies across the whole server and is not affected by this section.

SECTION 08. VIOLATION OF THE AGREEMENT

If a player from an alliance under NAP-10 violates the rules, that player’s alliance must investigate the situation, provide an explanation to the affected party, compensate the damage if the violation is confirmed, take measures against the violator, and prevent the situation from repeating.

If an alliance protects the violator or refuses to resolve the problem, the matter is submitted for joint discussion by the leaders of the top-5 alliances.

SECTION 09. SYSTEMATIC VIOLATIONS

If the same alliance regularly violates NAP-10, provokes conflicts, or ignores confirmed decisions of the top-5 leaders, its NAP-10 status may be reviewed.

A regular violation means at least 5 confirmed violations since the agreement entered into force, with a frequency of at least once every 2 weeks.

Violations by the alliance leader or R4 members are considered more serious than violations by ordinary members.

An alliance can be excluded from NAP-10 only according to the voting rules set out in this agreement.

After exclusion, the alliance loses NAP-10 protection and is no longer considered a participant in the Non-Attack Pact.

SECTION 10. PROCEDURE FOR RESOLVING DISPUTES

In case of a conflict between alliances under NAP-10, the parties must first try to resolve the issue directly through their leaders.

If the conflict is not resolved within 7 days, it is submitted for joint discussion by the leaders of the top-5 alliances.

The joint discussion of the top-5 leaders is not a separate authority over the server. It is only a platform for negotiation and coordination of decisions.

No alliance may be forced to accept a decision with which it directly disagrees.

SECTION 11. VOTING AND DECISION-MAKING

All important decisions regarding server development, rule changes, recognition of an alliance as a violator, exclusion from NAP-10, or restrictions on alliances must be made unanimously by the leaders of the top-5 alliances.

Each top-5 alliance has one vote.

Majority rule does not apply.

If there is no unanimity, the decision is not adopted, and the existing rules remain unchanged.

The parties may take up to 3 days to search for a compromise, but no decision is adopted automatically after that period expires.

No alliance has the right to change the rules of this agreement unilaterally.

SECTION 12. FORMING ALLIANCES

Each alliance has the right to enter into individual alliance agreements with any other alliance at its own discretion.

NAP-10 is not an alliance and does not require alliances to enter into alliance relations with each other.

No alliance may be forcibly included in an alliance or forced to break an alliance without a decision adopted under the rules of this agreement.

A demand to break an alliance is possible only if the allied party regularly violates the rules, undermines server stability, or is recognized as an aggressor under the procedure established by this agreement.

If an alliance knowingly shelters an ally recognized as an aggressor, its NAP-10 status may be submitted for discussion by the leaders of the top-5 alliances.

SECTION 13. ACADEMIES AND SUBSIDIARY ALLIANCES

Academies, branches, and junior rosters of alliances under NAP-10 must comply with this agreement.

The main alliance is responsible for the actions of its academy.

If an academy violates NAP-10, the leader of the main alliance must resolve the situation and prevent it from repeating.

NAP-10 applies to academies and subsidiary alliances of NAP-10 participants regardless of their ranking position.

A violation against an academy is treated as a violation against the main alliance.

Academies and subsidiary alliances of NAP-10 participants must indicate their connection to the main alliance in their name or description.

SECTION 14. ANNOUNCEMENT OF DECISIONS

All decisions adopted by the top-5 leaders enter into force only after the wording has been agreed by all parties.

After approval, the decision must be published and added to this agreement.

It is prohibited to announce rules on behalf of all leaders before they are fully agreed.

Public announcement of unapproved rules is considered a provocation and a violation of this agreement.

SECTION 15. STATUS OF SERVER STABILITY GUARANTOR

The alliance ranked first in the overall server power ranking is recognized as the guarantor of server stability.

The status of guarantor does not grant the right to rule the server alone, but it grants the right of first initiative in matters of protecting order, preventing conflicts, and preparing the server for cross-server events.

The stability guarantor may initiate urgent discussion of violations, propose temporary measures to prevent conflict, and demand review of situations that threaten server stability.

If first place in the power ranking changes, the guarantor status passes to the new alliance ranked first.

SECTION 16. WAR MODE DURING CROSS-SERVER EVENTS

After an official cross-server event is announced, the server enters a mode of general coordination.

During a cross-server event, internal conflicts, political disputes, and actions that weaken the server must be stopped.

Coordination of the server’s actions in cross-server events is carried out by the leaders of the top-3 alliances, taking into account the actual power, activity, and contribution of each alliance.

The alliance ranked first in server power has the right to initiate the general action plan and distribute key tasks for the duration of the cross-server event.


Version for publication by link. The text may be updated after approval by alliance leaders.

Результаты поиска