These rules apply to the game server, forum, official TheBattle.club communities, messengers, and the support service.
By using the project resources, the player confirms agreement with these rules.
1.1.
The rules are mandatory for all users of TheBattle.club.
1.2.
The project team has the right to change the rules without prior notice to players.
1.3.
The project team independently determines the sanction for a violation, taking into account its nature, consequences, and recurrence.
1.4.
The project team has the right to suspend access to a master account, game account, and/or character without explanation.
1.5.
Links to third-party resources are also subject to moderation. If content available through such a link violates the project rules, sanctions may be applied to the user who published the link.
1.6.
Ignorance of the rules does not exempt a user from responsibility.
1.7.
The administration intervenes in gameplay in cases of rule violations, technical problems, events, and other situations explicitly provided for by these rules.
The administration is not obliged to compensate for the consequences of a player's inattention, unsuccessful decision, or voluntarily confirmed action.
2.1.
Threats against the project team are prohibited.
2.2.
Publishing correspondence with the project team without prior approval is prohibited.
2.3.
Deceiving or attempting to deceive the project team is prohibited, including knowingly providing false information, falsifying evidence, and intentionally concealing material circumstances.
2.4.
Voluntary Account Lock
The account owner may contact the support service and request a temporary restriction of access to their account.
The support service may request proof of account ownership. The lock period must be specified when submitting the request. Early unlocking is not guaranteed and may require the owner to be verified again.
2.5.
For project security purposes, the team does not disclose server IP addresses or other internal technical information.
2.6.
The support service is intended to resolve technical problems, account and payment issues, rule violations, and other situations requiring intervention by the project team.
2.7.
The support service may decline to provide guidance on game mechanics, quests, classes, items, character progression, and the game economy if the information can be obtained in the game, on the forum, in project materials, from other players, or in any publicly available Lineage 2 High Five knowledge base.
Information from third-party knowledge bases does not apply to mechanics modified on TheBattle.club.
2.8.
A support request must be clear and contain the information required for verification: server, character, approximate time of the event, and a description of the problem.
For payment-related issues, support may request the date, amount, transaction identifier, and other payment details.
2.9.
The support service may request additional information and suspend consideration of a request until that information is received.
2.10.
Project staff do not need your account password. Do not provide your password to support staff or any other person.
2.11.
Requests are processed in queue order, taking into account their urgency and complexity. Creating multiple requests regarding the same issue does not speed up the review.
2.12.
If logs, item history, payments, or other technical data need to be checked, support may convert the request into a ticket.
The usual initial review time for such a ticket is up to 12 hours, and up to 24 hours in complex cases. If developer involvement, a payment provider, or an additional technical investigation is required, the final review time may be extended.
2.13.
When establishing the actual course of in-game events, server logs and internal project technical data take priority.
Screenshots and video recordings may be used as supplementary materials.
2.14.
The administration is not required to provide internal logs, anti-cheat and anti-fraud methods, internal evidence, or other service information.
2.15.
When communicating with the project team, threats, blackmail, harassment of staff, publication of their personal data, pressure, repeated insults, spam, falsification of evidence, and knowingly false information are prohibited.
2.16.
If the communication rules are violated, a staff member may terminate the conversation, close the request, or restrict the user's access to the support service.
Repeated or multiple cases of intentionally providing false information may result in the master account and game accounts being blocked.
2.17.
Serious or repeated threats, blackmail, harassment of staff, publication of personal data, and attempts to harm staff members or the project may result in the user being blocked across all TheBattle.club resources.
2.18.
After a decision has been made, support is not required to reconsider the same issue without new circumstances or evidence and is not required to continue a dispute regarding a closed request.
2.19.
The project team may decline to investigate missing items if the account owner shared authentication details with third parties.
3.1.
The account owner is solely responsible for account security and for all actions performed through the account.
3.2.
Sharing a login, password, or any other form of access with third parties is done at the account owner's own risk and does not exempt the owner from responsibility for violations.
If a person who obtained access to the account participated in RMT or another rule violation, sanctions may also be applied to the owner's account.
3.3.
The account owner is solely responsible for the safety of characters, items, and in-game valuables, except in cases explicitly provided for by these rules.
3.4.
The .ipro command is provided to protect items.
If the account owner shared account details with third parties and did not use .ipro, the project team is not required to investigate missing items.
At the player's request, a paid investigation may be conducted:
cost — 20 USD;
the investigation does not guarantee the return of items;
items transferred to other players and introduced into the game economy are not returned;
items located on other characters of the same account may be returned;
after the investigation, the character that removed the items will be identified.
3.5.
All accounts belonging to the same player may be sanctioned for a violation committed on any one of them.
3.6.
Accounts or characters inactive for more than 60 days may be deleted without the possibility of recovery.
4.1.
Using names or nicknames that create the impression of affiliation with the project team is prohibited, including:
GM;
Admin;
ADM;
Support;
Administrator.
4.2.
Impersonating a TheBattle.club staff member or an authorized representative of the administration is prohibited.
4.3.
Obscene, provocative, or offensive names and titles are prohibited.
4.4.
Impersonating another player for the purpose of deception, humiliation, or harm is prohibited.
For a first violation, the administration may forcibly change the nickname. A repeated violation may result in an account block.
5.1.
Statements capable of causing reputational harm to the project are prohibited.
5.2.
Spreading false information about TheBattle.club is prohibited.
5.3.
Direct or indirect advertising of other online games or game projects is prohibited.
5.4.
Any manifestations of racism or nationalism are prohibited.
5.5.
Political statements and political campaigning are prohibited.
5.6.
Use of the symbols Z, V, or O associated with military actions is prohibited in any context.
5.7.
Use of fascist symbols is prohibited.
5.8.
Public mass giveaways of in-game valuables without prior approval from the administration are prohibited, including giveaways related to leaving the project.
5.9.
Threats against players that are unrelated to gameplay are prohibited.
5.10.
Calls to leave the project are prohibited.
5.11.
Insults directed at family members, including the use of profanity in public chats, are prohibited.
5.12.
Flooding and spam are prohibited.
5.13.
Profanity itself is not prohibited unless it violates other provisions of these rules.
5.14.
Private chats are generally not moderated. To stop unwanted communication, use the /block nickname command.
5.15.
The game is intended for an adult audience. Parents, legal guardians, or the device owner are responsible for children's access to the game client, chats, and user-generated content.
To limit chat display, you may use ALT + J and the game client settings.
5.16.
A game chat block is issued for a period ranging from 60 minutes to permanent, depending on the violation and the history of previous chat blocks.
A repeated similar violation generally increases the block duration. Systematic violations may result in a permanent chat block or game account block.
6.1.
Automation of gameplay using third-party software, peripheral-device macros, third-party files, or game client modifications is prohibited.
6.2.
Using game bugs, vulnerabilities, or flaws is prohibited. If such a problem is discovered, the player must report it to the support service.
6.3.
The player is solely responsible for actions they confirm through the game client.
The administration is not required to reverse consequences or compensate valuables in cases of an incorrect purchase, sale, exchange, craft, enchantment, attribute insertion, augmentation, synthesis, unsealing, deletion, use, or transfer of an item, or when a price, quantity, or characteristic was read incorrectly.
6.4.
An unsuccessful outcome of a standard game mechanic is not, by itself, grounds for a refund or compensation.
6.5.
The administration may decline to intervene in disputes between players if they occur within standard game mechanics and do not involve a separate violation of these rules.
7.1.
Before confirming a trade, purchase, paid mail, craft, or other transaction, the player must independently verify the item, quantity, price, enchantment level, attributes, and other displayed characteristics.
If the terms were correctly displayed by the game client and the player independently confirmed the transaction, the administration is not required to return in-game valuables or sanction the other party solely because of the player's inattention or a prior agreement between the parties.
7.2.
The TheBattle.club administration is not a guarantor of private or verbal agreements between players.
Loans, installment arrangements, promises of later buyback, transfers of items for enchantment or improvement, services, and other trust-based transactions are carried out at the participants' own risk.
The administration is not required to investigate such agreements, return items, or compensate losses.
7.3.
The administration does not regulate or interfere in market relations between players. The value of items and game services is determined by the players themselves.
A high, low, or unusual price is not a violation if it is correctly displayed by the game client.
7.4.
For the purposes of these rules, fraud means actions involving the use of a bug, vulnerability, technical flaw, incorrect display, substitution directly within the trading mechanic, or impersonation of another player or a representative of the administration in order to obtain another person's in-game valuables.
Ordinary player inattention or failure to fulfill a private agreement does not, by itself, constitute grounds for applying this provision.
7.5.
Using client or game flaws during trading is prohibited, including methods that allow an item, quantity, price, or other transaction terms to be hidden, substituted, or displayed incorrectly.
7.6.
RMT
Buying or selling in-game valuables for real money, monetary equivalents, external services, or other value outside the project's official mechanisms is prohibited.
When in-game valuables are purchased, the account may be blocked and the received items removed:
purchase of up to and including 30 USD — unlocking costs 30 USD, with the purchased items removed;
purchase above 30 USD — unlocking costs 50 USD, with the purchased items removed.
7.7.
Accounts involved in selling in-game valuables through FunPay are not eligible for unlocking.
A sale includes:
offering in-game valuables for sale in game chat;
posting a sale listing on forums or third-party services;
completing an actual sale.
The administration may choose not to disclose its methods for detecting violations or the evidence used.
7.8.
The administration may terminate access to the server for an RMT violation at any time without the right of appeal.
7.9.
Exchanging in-game valuables between TheBattle.club servers, other game projects, or other games is prohibited.
Buying, selling, or exchanging game accounts or characters is prohibited, including within the same server.
Discussing or arranging such transactions in the game, on the forum, or on third-party resources is prohibited.
8.1.
In the event of a DDoS attack, technical failure, or other emergency, the administration may postpone, cancel, restart, or change the conditions of a game event.
Information about changes may be published through available official channels. The absence of a separate notification is not, by itself, grounds for compensation.
8.2.
Force majeure circumstances include, among other things, data center and infrastructure failures that affect server operation.
8.3.
Disputes over Epic Boss Drops
The administration may intervene only in a dispute concerning an item that dropped directly from an epic boss during an organized clan or command-channel raid.
This provision applies to the following bosses:
Antharas;
Queen Ant;
Baium;
Beleth;
Core;
Orfen;
Valakas.
A request is accepted from the clan leader whose clan is credited with the boss kill according to server logs, no later than 24 hours after the kill.
The request must specify the boss, the approximate time of the kill, and the characters associated with the disputed item.
The administration checks server logs, the item's ObjectId, whether it dropped, who picked it up, and any subsequent transfers.
If the item was taken by a member of the same clan or command channel who was part of it at the time of the boss kill, the administration may confiscate the item and return it to the clan leader.
Disputes between different clans over an item picked up from the ground are treated as part of gameplay and are not covered by this provision.
Items dropped from PK characters are not covered by clause 8.3 regardless of their origin.
If the item can no longer be safely confiscated without affecting third parties or the game world, the administration may refuse to return it.
For violations of the rules, the administration may apply one or more of the following measures:
9.1.
Blocking access to a game account, master account, forum, support service, social networks, or other project resources.
9.2.
Blocking access by HWID and/or IP.
9.3.
Deleting an account and/or character.
9.4.
Temporarily or permanently blocking game chat, including by HWID.
9.5.
Removing items or in-game valuables.
9.6.
Temporarily restricting actions of a character or account.
10.1.
A block on one account may serve as grounds for blocking other accounts belonging to the same user, regardless of their registration dates.
10.2.
A block on one TheBattle.club resource may serve as grounds for restricting access to other project resources.
10.3.
A player may appeal a block. Appeals are reviewed in queue order, and the decision is made by the project team.
The right to appeal does not apply to violations for which these rules explicitly provide otherwise.
10.4.
Repeated appeals without new circumstances or evidence may be left without review.
10.5.
Unlocking an account blocked for a rule violation costs from 30 USD:
bots — 30–150 USD, depending on the violation;
RMT — from 30 USD, for buyers only;
fraud and other violations — from 30 USD.
10.6.
The exact cost of unlocking a master account, account, or character can be obtained from the support service.
Payment is made through the master account balance.
11.1.
Adding funds to the personal account balance is voluntary and non-refundable.
A refund is possible only with the administration's approval or in force majeure cases provided for by the project.
11.2.
Funds are usually credited automatically within 15 seconds, but in some cases processing may take longer.
If funds were charged but the balance did not change, check the personal account and contact the support service if the problem persists.
11.3.
After funds from the personal account balance have been used, the user loses the right to a refund.
11.4.
By making a payment, the user confirms agreement with these rules.
