<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[G1R:MP Forum - G1 Remake Multiplayer Community - Rules & Guidelines]]></title>
		<link>https://g1r-mp.com/forum/</link>
		<description><![CDATA[G1R:MP Forum - G1 Remake Multiplayer Community - https://g1r-mp.com/forum]]></description>
		<pubDate>Sat, 19 Sep 2026 08:26:58 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[G1R:MP— Official Rules]]></title>
			<link>https://g1r-mp.com/forum/showthread.php?tid=42</link>
			<pubDate>Fri, 04 Sep 2026 09:40:53 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://g1r-mp.com/forum/member.php?action=profile&uid=1">QCherry</a>]]></dc:creator>
			<guid isPermaLink="false">https://g1r-mp.com/forum/showthread.php?tid=42</guid>
			<description><![CDATA[<div style="text-align: center;" class="mycode_align"><span style="font-size: xx-large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">G1R:MP</span><br />
<span style="font-size: large;" class="mycode_size">[b]MULTIPLAYER PLATFORM RULES</span></span></div>
<br />
<div style="text-align: center;" class="mycode_align"><span style="font-style: italic;" class="mycode_i">G1R:MP is an independent community project. It is not affiliated with, sponsored, authorized, or operated by THQ Nordic, Alkimia Interactive, or entities associated with them.</span></div>
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Table of Contents</span></span><br />
<ul class="mycode_list"><li>Chapter I. General Provisions<br />
</li>
<li>Chapter II. Definitions<br />
</li>
<li>Chapter III. Project Status and Third-Party Rights<br />
</li>
<li>Chapter IV. General Rules for Using G1R:MP<br />
</li>
<li>Chapter V. Legality of the Game and Prohibition of Piracy<br />
</li>
<li>Chapter VI. Game Assets, Files, and Intellectual Property<br />
</li>
<li>Chapter VII. Cheats and Unfair Interference with Gameplay<br />
</li>
<li>Chapter VIII. Security, Malware, and Attacks<br />
</li>
<li>Chapter IX. Harassment and Conduct Toward Others<br />
</li>
<li>Chapter X. Spam and Disruption of Communication<br />
</li>
<li>Chapter XI. Data, Privacy, and IP Addresses<br />
</li>
<li>Chapter XII. Servers and the Server List<br />
</li>
<li>Chapter XIII. Projects and Project Teams<br />
</li>
<li>Chapter XIV. Banned Persons in Project Teams<br />
</li>
<li>Chapter XV. Server Rules<br />
</li>
<li>Chapter XVI. Advertising and Promotion<br />
</li>
<li>Chapter XVII. Bugs, Exploits, and Vulnerabilities<br />
</li>
<li>Chapter XVIII. Circumvention of Penalties<br />
</li>
<li>Chapter XIX. Accounts and Impersonation<br />
</li>
<li>Chapter XX. Reports and Evidence<br />
</li>
<li>Chapter XXI. Administration Procedures<br />
</li>
<li>Chapter XXII. Global Player Bans<br />
</li>
<li>Chapter XXIII. Global Server and Project Bans<br />
</li>
<li>Chapter XXIV. Other Penalties<br />
</li>
<li>Chapter XXV. Appeals<br />
</li>
<li>Chapter XXVI. User Content and Fraud<br />
</li>
<li>Chapter XXVII. Actions Outside the Platform<br />
</li>
<li>Chapter XXVIII. Server Infrastructure Security<br />
</li>
<li>Chapter XXIX. Platform Availability<br />
</li>
<li>Chapter XXX. Amendments to the Rules<br />
</li>
<li>Chapter XXXI. Final Provisions<br />
</li>
</ul>
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter I. General Provisions</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 1. Scope of the Rules</span><br />
<br />
1. These Rules define the principles governing the use of the G1R:MP multiplayer platform, in particular its services, software, server list, forum, and infrastructure made available to users.<br />
2. The rules referred to in point 1 also apply to actions performed outside the use of the platform, as referred to in point 119.<br />
3. The Rules apply to all G1R:MP users, including players, server owners, administrators, moderators, members of project teams, and users of the Platform's official social media channels.<br />
4. Use of G1R:MP constitutes acceptance of these Rules.<br />
5. Ignorance of the Rules does not exempt a user from liability for violating them.<br />
6. Individual server rules may introduce additional rules beyond those referred to in point 1, provided that they do not conflict with these Rules.<br />
7. In the event of a conflict between server rules and these Rules, the G1R:MP Rules shall prevail.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter II. Definitions</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 2. Definitions</span><br />
<br />
G1R:MP – an independent multiplayer project intended for use with Gothic 1 Remake.<br />
Platform – all G1R:MP services, software, systems, server lists, forum, and infrastructure.<br />
Administration – persons authorized to manage G1R:MP and enforce the Rules.<br />
User – any person using the Platform.<br />
Player – a User using G1R:MP for multiplayer gameplay.<br />
Server – a game instance made available for connection through G1R:MP.<br />
Project – a server, community, or undertaking using G1R:MP.<br />
Project Team – persons actually involved in creating, operating, moderating, maintaining, or representing a Project.<br />
Global Player Ban – a penalty applicable across the entire G1R:MP Platform, regardless of the server on which the violation occurred.<br />
Global Server/Project Ban – a penalty consisting of excluding a server or project from the official G1R:MP infrastructure, in particular from the server list.<br />
Cheat – a program, script, modification, or other interference that provides an unfair advantage or enables actions unavailable in normal gameplay.<br />
Spam – repeated, mass, excessive, or persistent sending of content or requests that disrupts use of the Platform.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter III. Project Status and Third-Party Rights</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 3. Independent Nature of G1R:MP<br />
<br />
8. G1R:MP is an independent community project.<br />
9. G1R:MP is not affiliated with, sponsored, authorized, or operated by THQ Nordic, Alkimia Interactive, or other entities that own or license rights to Gothic 1 Remake, unless this is expressly and officially announced in the future.<br />
10. The use of the names Gothic, Gothic 1 Remake, THQ Nordic, Alkimia Interactive, and other third-party designations is solely for identifying compatibility, context, or the subject matter of the project.<br />
11. G1R:MP makes no claim to trademarks, names, graphics, models, sounds, music, textures, dialogue, or other elements belonging to their respective rights holders.<br />
12. A User may not present G1R:MP as an official product of THQ Nordic or Alkimia Interactive.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size">[b]Chapter IV. General Rules for Using G1R:MP</span><br />
<br />
[b]§ 4. User Obligations</span><br />
<br />
13. Users shall use the Platform in accordance with the law, these Rules, the intended purpose of G1R:MP, and instructions issued by the Administration in connection with security or enforcement of the rules.<br />
14. Deliberately destabilizing the Platform, impairing the operation of services, circumventing technical restrictions, and abusing G1R:MP mechanisms are prohibited.<br />
15. Impersonating persons referred to in point 3 is prohibited.<br />
16. Suggesting an official partnership with G1R:MP without the express consent of the Administration is prohibited.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter V. Legality of the Game and Prohibition of Piracy</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 5. Piracy</span><br />
<br />
17. Using, distributing, or promoting a pirated version of Gothic 1 Remake in connection with the use of G1R:MP is prohibited.<br />
18. The prohibition includes, in particular, publishing links to illegal copies of the game, torrents, cracks, key generators, security bypasses, and instructions for obtaining an illegal copy.<br />
19. Encouraging other users to obtain the game from illegal sources is prohibited.<br />
20. A violation of this section may result in a Global Player Ban referred to in Chapter XXII.<br />
21. If the violation is committed by a member of a Project Team, or if the team knowingly tolerates such content on its official channels and servers, the Administration may impose a Global Server or Project Ban referred to in Chapter XXIII.<br />
22. Project Teams are required to moderate their official channels and servers with regard to content promoting piracy.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter VI. Game Assets, Files, and Intellectual Property</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 6. Prohibition on Distributing Game Assets</span><br />
<br />
23. G1R:MP does not distribute assets originating from Gothic 1 Remake or other files for which it does not have the appropriate distribution rights.<br />
24. The installation and operation of G1R:MP should be based on game files legally owned by the User, where such files are necessary for the Platform to operate.<br />
25. The use of official G1R:MP infrastructure to distribute models, textures, animations, recordings, music, dialogue, maps, executable files, or other protected assets extracted from the game is prohibited if the person publishing them does not have the right to redistribute them.<br />
26. Preparing project packages intended to replace a User's legal copy of Gothic 1 Remake by including significant game files or assets is prohibited.<br />
27. The User's own original materials, or materials for which the User holds an appropriate license, may be permitted.<br />
28. The Project Team is responsible for content and files distributed by it in connection with use of the Platform.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter VII. Cheats and Unfair Interference with Gameplay</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 7. Prohibition of Cheating</span><br />
<br />
29. Using cheats in G1R:MP is prohibited.<br />
30. Cheating may include, among other things, modifying process memory, using trainers, manipulating network traffic, falsifying packets, bypassing security measures, and using unauthorized automation that provides an advantage.<br />
31. Creating, distributing, advertising, and selling cheats intended for G1R:MP is prohibited.<br />
32. Confirmed use of cheats may result in a permanent Global Player Ban across the entire Platform.<br />
33. The Administration may base its decision on recordings, logs, technical data, observations, screenshots, and other credible evidence.<br />
34. A report alone does not establish guilt.<br />
35. The Administration is not required to disclose cheat-detection methods or information that would enable security measures to be bypassed.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter VIII. Security, Malware, and Attacks</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 8. Malicious Software and Attacks</span><br />
<br />
36. The distribution of malicious software, including viruses, trojans, ransomware, spyware, keyloggers, stealers, backdoors, and other harmful programs, is strictly prohibited.<br />
37. Presenting a malicious file as a G1R:MP client, update, launcher, mod, plugin, or administrative tool is prohibited.<br />
38. DoS/DDoS attacks, attempts at unauthorized access, account takeovers, data theft, and other actions against the infrastructure of G1R:MP, Projects, or Users are prohibited.<br />
39. Serious security violations may result in a permanent Global Player Ban and a Global Project Ban if the violation is connected with the activities of its team.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter IX. Harassment and Conduct Toward Others</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 9. Harassment</span><br />
<br />
40. Harassing, intimidating, threatening, persistently insulting, and organizing coordinated actions against G1R:MP Users are prohibited.<br />
41. Collecting and using information found about a User for the purpose of humiliating, intimidating, defaming, blackmailing, or causing a sense of danger, in particular by publishing such information, is prohibited.<br />
42. Point 41 also applies where the information was previously publicly available.<br />
43. Encouraging other people to harass a specific User is prohibited.<br />
44. If a violation is committed by a member of a Project Team in connection with their project activities, the Administration may impose a penalty on the Project as well.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter X. Spam and Disruption of Communication</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 10. Spam</span><br />
<br />
45. Spamming chats, the forum, reporting systems, the server list, and other G1R:MP functions is prohibited.<br />
46. Spam includes, in particular, repeatedly sending the same content, flooding a chat with messages or characters, mass advertising, automatically sending messages, and actions that disrupt normal communication.<br />
47. Manually performed activity may also be considered spam if its scale, intensity, or repetition clearly disrupts use of the Platform.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XI. Data, Privacy, and IP Addresses</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 11. User Data and Public Technical Information</span><br />
<br />
48. Users should exercise caution when publishing their own data.<br />
49. IP addresses used by Users to connect to the Platform — specifically to the servers and the forum — are treated as public data.<br />
50. IP addresses published by Users in public sections of the G1R:MP forum are publicly visible to persons who have access to those sections.<br />
51. The IP address and port of a public server may be publicly displayed on the forum or server list if this is necessary to allow other Users to connect.<br />
52. The person publishing a server address is responsible for having the authority to disclose it and should be aware that a public server address is not confidential information within the place where it has been published.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XII. Servers and the Server List</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 12. Rules for Publishing Servers</span><br />
<br />
53. The official server list may contain servers genuinely intended for gameplay or justified testing.<br />
54. Creating servers intended solely as a joke, for spam, impersonation, fraud, advertising unrelated to G1R:MP, or destabilizing the server list is prohibited.<br />
55. Mass publication of empty, fictitious, or automatically generated servers is prohibited.<br />
56. A server name may not mislead others as to its owner, status, or official affiliation with G1R:MP.<br />
57. The Administration may hide or remove a server that is non-functional, a test server, fictitious, spam-related, dangerous, or in violation of the Rules.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XIII. Projects and Project Teams</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 13. Project Responsibility</span><br />
<br />
58. The Project Owner is responsible for organizing the team, official project channels and servers, and responding to serious violations committed by persons acting on behalf of the Project.<br />
59. The Project Team should moderate its official channels and servers with regard to piracy, malware, harassment, and other serious violations of the Rules.<br />
60. A single violation by an ordinary Player does not automatically make the entire Project Team liable.<br />
61. However, the Administration may penalize the entire Project Team if the violation is committed by the Project Owner, by a team member acting in connection with the Project, or if the Project Team knowingly tolerates serious and repeated violations.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XIV. Banned Persons in Project Teams</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 14. Prohibition on Participation by an Officially Banned Person</span><br />
<br />
62. A person subject to an official ban prohibiting participation in G1R:MP Project Teams shall be informed of this prohibition by the Administration each time.<br />
63. A Project may not have on its team a person who is subject to a valid prohibition on participating in Projects.<br />
64. If a Project Team includes a person subject to such a prohibition, the Project is subject to a Global Server or Project Ban.<br />
65. A team member means not only a person formally listed as part of the team, but also a person actually involved in creating, managing, programming, moderating, maintaining infrastructure, representing, or making decisions concerning the Project.<br />
66. Falsely removing a person from a team while continuing to allow their actual participation in the Project is prohibited.<br />
67. Circumvention of the prohibition may include, among other things, using another person's account, performing duties through intermediaries, hidden administrative permissions, or undisclosed management of the Project.<br />
68. A Global Project Ban resulting from the presence of a prohibited person does not automatically mean an individual ban for all other team members unless they themselves committed violations.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XV. Server Rules</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 15.</span><br />
<br />
69. A Server Owner may establish additional gameplay rules.<br />
70. Server rules may not override G1R:MP rules concerning, among other things, cheating, piracy, malware, security, ban circumvention, and participation of persons subject to a global prohibition.<br />
71. Penalties imposed by the Administration of a specific server are separate from global G1R:MP penalties.<br />
72. As a rule, G1R:MP Administration does not resolve disputes arising solely from the internal rules of a private server.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XVI. Advertising and Promotion</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 16.</span><br />
<br />
73. Project advertising is permitted only in the places and forms provided for by the Platform's rules.<br />
74. Mass advertising, impersonating other Projects, providing false information about competing Projects, and using advertising bots without the required permission are prohibited.<br />
75. Competition between Projects may not take the form of harassment, sabotage, technical attacks, or organized raids.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XVII. Bugs, Exploits, and Vulnerabilities</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 17.</span><br />
<br />
76. Knowingly exploiting G1R:MP bugs in order to gain an unfair advantage, bypass security measures, obtain unauthorized data, or destabilize services is prohibited.<br />
77. A User who discovers a serious security vulnerability should report it to the Administration rather than publish instructions enabling its exploitation.<br />
78. The Administration may refrain from imposing a penalty if the action was solely a necessary test intended to document a bug and caused no harm.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XVIII. Circumvention of Penalties</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 18.</span><br />
<br />
79. Circumventing global and local restrictions imposed by the G1R:MP Administration is prohibited.<br />
80. Circumventing a penalty may include using additional accounts, other people's accounts, concealing one's identity in order to participate in a Project again, or other deliberate actions intended to nullify the effect of a ban.<br />
81. Helping a banned person circumvent a penalty may constitute a separate violation of the Rules.<br />
82. An attempt to circumvent a ban may result in an extension of the penalty, conversion of a temporary penalty into a permanent one, or additional sanctions.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XIX. Accounts and Impersonation</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 19.</span><br />
<br />
83. A User is responsible for the security of their account and should not share login credentials with third parties.<br />
84. Sharing an account with another person does not guarantee cancellation of a penalty for actions performed using that account.<br />
85. The Administration may order a change of an account, Project, or server name if it deliberately misleads others.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XX. Reports and Evidence</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 20.</span><br />
<br />
86. Users may report violations through channels designated by the Administration.<br />
87. Where possible, a report should contain the User's or Project's name, a description of the incident, the date or approximate time, and available evidence.<br />
88. The Administration may consider recordings, screenshots, logs, technical data, messages, and other credible evidence.<br />
89. The Administration may refuse to consider an obviously false or spam report, a report that cannot be verified, or one concerning solely the internal rules of a server.<br />
90. Knowingly submitting false reports and organizing coordinated reporting against innocent persons are prohibited.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXI. Administration Procedures</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 21.</span><br />
<br />
91. The Administration considers cases based on available information, the nature of the violation, and the credibility of the evidence.<br />
92. In the event of a security threat, the Administration may impose a temporary restriction before the full proceedings have been completed.<br />
93. The Administration is not required to publicly disclose internal moderation methods, security measures, cheat-detection mechanisms, or data that would enable security measures to be bypassed.<br />
94. Decisions may take into account the scale of the violation, its intentional nature, harm caused, previous offenses, attempts to remedy the harm, and the User's conduct after the incident.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXII. Global Player Bans</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 22. Nature of a Global Player Ban</span><br />
<br />
95. G1R:MP uses Global Player Bans.<br />
96. A Global Player Ban is imposed by the G1R:MP Administration and applies at the level of the entire Platform to the extent specified in the penalty decision.<br />
97. A Global Player Ban may prevent a Player from using G1R:MP gameplay regardless of the server on which the violation occurred.<br />
98. A Global Player Ban may be temporary or permanent.<br />
99. In cases of particularly serious violations, especially confirmed cheating, knowingly distributing malware, serious attacks on infrastructure, or serious circumvention of penalties, the Administration may impose a permanent Global Player Ban.<br />
100. The penalized person is informed of the penalty imposed and, where possible and safe, of its basis.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXIII. Global Server and Project Bans</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 23. Nature of a Global Server or Project Ban</span><br />
<br />
101. G1R:MP uses Global Server and Project Bans.<br />
102. A Global Server or Project Ban may result in a server being removed or blocked from the official G1R:MP server list and refusal to republish it for the duration of the penalty.<br />
103. A Global Project Ban may cover all servers operating under the same Project or entity if necessary to enforce the penalty.<br />
104. A Global Server or Project Ban may be imposed, among other things, for serious violations committed by its team, knowingly tolerating piracy or malware, circumventing penalties, harmful actions against the Platform, or the presence on the team of a person subject to an official prohibition on participation in Projects.<br />
105. Changing the server name, domain, formal owner, or publishing account does not invalidate a Global Ban if it is in fact the same Project or an attempt to circumvent the penalty.<br />
106. A Global Project Ban does not necessarily mean an automatic Global Player Ban for all ordinary Players who previously used that server.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXIV. Other Penalties</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 24. Types of Sanctions</span><br />
<br />
107. For violations of the Rules, the Administration may apply, in addition to the penalties referred to in Chapters XXII and XXIII, an instruction, warning, server hiding, or another proportionate restriction necessary for the security of the Platform.<br />
108. If a specific provision does not prescribe one mandatory penalty, the Administration selects a sanction appropriate to the circumstances of the case.<br />
109. A temporary penalty may have a duration determined individually.<br />
110. The Administration is not required to precede a serious penalty with a warning.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXV. Appeals</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 25.</span><br />
<br />
111. A User may appeal a penalty in the manner specified by the Administration if an appeals system is available for the relevant type of sanction.<br />
112. An appeal should concern a specific decision and present arguments or new information.<br />
113. Abuse of the appeals process, threats, spam, and repeatedly submitting the same case after a final decision may be left without further consideration.<br />
114. The Administration may designate a decision as final.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXVI. User Content and Fraud</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 26.</span><br />
<br />
115. A User is responsible for content published through the Platform.<br />
116. Publishing phishing, fake login pages, fake updates, scams, fraud, extortion, and other content intended to obtain Users' data or money is prohibited.<br />
117. The Administration may remove content that violates the Rules regardless of any penalty imposed on its author.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXVII. Actions Outside the Platform</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 27.</span><br />
<br />
118. As a rule, the Administration does not intervene in private conflicts unrelated to G1R:MP.<br />
119. Actions outside the official Platform may be taken into account if they are directly connected with G1R:MP and concern security, harassment, cheats, malware, circumvention of penalties, piracy, or official Project Team activity.<br />
120. Mere dislike or a private conflict between Users does not automatically constitute grounds for a global penalty.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXVIII. Server Infrastructure Security</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 28.</span><br />
<br />
121. A Server Owner is responsible for securing their own infrastructure and should apply appropriate technical measures.<br />
122. Publishing a server on the G1R:MP list does not mean that G1R:MP assumes responsibility for the security of the owner's private infrastructure.<br />
123. Publicly providing a server address means that the address may be visible to Platform Users.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXIX. Platform Availability</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 29.</span><br />
<br />
124. G1R:MP does not guarantee uninterrupted availability of its services.<br />
125. The Platform may be temporarily disabled or restricted due to updates, failures, technical work, problems with external services, or security incidents.<br />
126. The Administration may temporarily disable a specific function if required for the security or stability of the Platform.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXX. Amendments to the Rules</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 30.</span><br />
<br />
127. The Rules may be amended as G1R:MP develops, new functions and threats emerge, abuses occur, or it becomes necessary to clarify the rules.<br />
128. The current version of the Rules is published in the officially designated place.<br />
129. Users should familiarize themselves with the current version of the rules before continuing to use the Platform after changes have been announced.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXXI. Final Provisions</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 31.</span><br />
<br />
130. The purpose of the Rules is to ensure a fair, safe, and stable environment for the G1R:MP community.<br />
131. The Rules should not be interpreted in a manner that permits obvious circumvention of their provisions by exploiting linguistic loopholes or superficial organizational changes.<br />
132. If a particular action is not expressly listed but clearly corresponds to conduct prohibited by a given provision, the Administration may assess it in accordance with the purpose of that provision.<br />
133. In matters not regulated herein, the Administration may make decisions necessary for the security and proper functioning of G1R:MP, while maintaining proportionality.<br />
134. The Rules enter into force on the date specified at their official publication.]]></description>
			<content:encoded><![CDATA[<div style="text-align: center;" class="mycode_align"><span style="font-size: xx-large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">G1R:MP</span><br />
<span style="font-size: large;" class="mycode_size">[b]MULTIPLAYER PLATFORM RULES</span></span></div>
<br />
<div style="text-align: center;" class="mycode_align"><span style="font-style: italic;" class="mycode_i">G1R:MP is an independent community project. It is not affiliated with, sponsored, authorized, or operated by THQ Nordic, Alkimia Interactive, or entities associated with them.</span></div>
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Table of Contents</span></span><br />
<ul class="mycode_list"><li>Chapter I. General Provisions<br />
</li>
<li>Chapter II. Definitions<br />
</li>
<li>Chapter III. Project Status and Third-Party Rights<br />
</li>
<li>Chapter IV. General Rules for Using G1R:MP<br />
</li>
<li>Chapter V. Legality of the Game and Prohibition of Piracy<br />
</li>
<li>Chapter VI. Game Assets, Files, and Intellectual Property<br />
</li>
<li>Chapter VII. Cheats and Unfair Interference with Gameplay<br />
</li>
<li>Chapter VIII. Security, Malware, and Attacks<br />
</li>
<li>Chapter IX. Harassment and Conduct Toward Others<br />
</li>
<li>Chapter X. Spam and Disruption of Communication<br />
</li>
<li>Chapter XI. Data, Privacy, and IP Addresses<br />
</li>
<li>Chapter XII. Servers and the Server List<br />
</li>
<li>Chapter XIII. Projects and Project Teams<br />
</li>
<li>Chapter XIV. Banned Persons in Project Teams<br />
</li>
<li>Chapter XV. Server Rules<br />
</li>
<li>Chapter XVI. Advertising and Promotion<br />
</li>
<li>Chapter XVII. Bugs, Exploits, and Vulnerabilities<br />
</li>
<li>Chapter XVIII. Circumvention of Penalties<br />
</li>
<li>Chapter XIX. Accounts and Impersonation<br />
</li>
<li>Chapter XX. Reports and Evidence<br />
</li>
<li>Chapter XXI. Administration Procedures<br />
</li>
<li>Chapter XXII. Global Player Bans<br />
</li>
<li>Chapter XXIII. Global Server and Project Bans<br />
</li>
<li>Chapter XXIV. Other Penalties<br />
</li>
<li>Chapter XXV. Appeals<br />
</li>
<li>Chapter XXVI. User Content and Fraud<br />
</li>
<li>Chapter XXVII. Actions Outside the Platform<br />
</li>
<li>Chapter XXVIII. Server Infrastructure Security<br />
</li>
<li>Chapter XXIX. Platform Availability<br />
</li>
<li>Chapter XXX. Amendments to the Rules<br />
</li>
<li>Chapter XXXI. Final Provisions<br />
</li>
</ul>
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter I. General Provisions</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 1. Scope of the Rules</span><br />
<br />
1. These Rules define the principles governing the use of the G1R:MP multiplayer platform, in particular its services, software, server list, forum, and infrastructure made available to users.<br />
2. The rules referred to in point 1 also apply to actions performed outside the use of the platform, as referred to in point 119.<br />
3. The Rules apply to all G1R:MP users, including players, server owners, administrators, moderators, members of project teams, and users of the Platform's official social media channels.<br />
4. Use of G1R:MP constitutes acceptance of these Rules.<br />
5. Ignorance of the Rules does not exempt a user from liability for violating them.<br />
6. Individual server rules may introduce additional rules beyond those referred to in point 1, provided that they do not conflict with these Rules.<br />
7. In the event of a conflict between server rules and these Rules, the G1R:MP Rules shall prevail.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter II. Definitions</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 2. Definitions</span><br />
<br />
G1R:MP – an independent multiplayer project intended for use with Gothic 1 Remake.<br />
Platform – all G1R:MP services, software, systems, server lists, forum, and infrastructure.<br />
Administration – persons authorized to manage G1R:MP and enforce the Rules.<br />
User – any person using the Platform.<br />
Player – a User using G1R:MP for multiplayer gameplay.<br />
Server – a game instance made available for connection through G1R:MP.<br />
Project – a server, community, or undertaking using G1R:MP.<br />
Project Team – persons actually involved in creating, operating, moderating, maintaining, or representing a Project.<br />
Global Player Ban – a penalty applicable across the entire G1R:MP Platform, regardless of the server on which the violation occurred.<br />
Global Server/Project Ban – a penalty consisting of excluding a server or project from the official G1R:MP infrastructure, in particular from the server list.<br />
Cheat – a program, script, modification, or other interference that provides an unfair advantage or enables actions unavailable in normal gameplay.<br />
Spam – repeated, mass, excessive, or persistent sending of content or requests that disrupts use of the Platform.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter III. Project Status and Third-Party Rights</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 3. Independent Nature of G1R:MP<br />
<br />
8. G1R:MP is an independent community project.<br />
9. G1R:MP is not affiliated with, sponsored, authorized, or operated by THQ Nordic, Alkimia Interactive, or other entities that own or license rights to Gothic 1 Remake, unless this is expressly and officially announced in the future.<br />
10. The use of the names Gothic, Gothic 1 Remake, THQ Nordic, Alkimia Interactive, and other third-party designations is solely for identifying compatibility, context, or the subject matter of the project.<br />
11. G1R:MP makes no claim to trademarks, names, graphics, models, sounds, music, textures, dialogue, or other elements belonging to their respective rights holders.<br />
12. A User may not present G1R:MP as an official product of THQ Nordic or Alkimia Interactive.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size">[b]Chapter IV. General Rules for Using G1R:MP</span><br />
<br />
[b]§ 4. User Obligations</span><br />
<br />
13. Users shall use the Platform in accordance with the law, these Rules, the intended purpose of G1R:MP, and instructions issued by the Administration in connection with security or enforcement of the rules.<br />
14. Deliberately destabilizing the Platform, impairing the operation of services, circumventing technical restrictions, and abusing G1R:MP mechanisms are prohibited.<br />
15. Impersonating persons referred to in point 3 is prohibited.<br />
16. Suggesting an official partnership with G1R:MP without the express consent of the Administration is prohibited.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter V. Legality of the Game and Prohibition of Piracy</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 5. Piracy</span><br />
<br />
17. Using, distributing, or promoting a pirated version of Gothic 1 Remake in connection with the use of G1R:MP is prohibited.<br />
18. The prohibition includes, in particular, publishing links to illegal copies of the game, torrents, cracks, key generators, security bypasses, and instructions for obtaining an illegal copy.<br />
19. Encouraging other users to obtain the game from illegal sources is prohibited.<br />
20. A violation of this section may result in a Global Player Ban referred to in Chapter XXII.<br />
21. If the violation is committed by a member of a Project Team, or if the team knowingly tolerates such content on its official channels and servers, the Administration may impose a Global Server or Project Ban referred to in Chapter XXIII.<br />
22. Project Teams are required to moderate their official channels and servers with regard to content promoting piracy.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter VI. Game Assets, Files, and Intellectual Property</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 6. Prohibition on Distributing Game Assets</span><br />
<br />
23. G1R:MP does not distribute assets originating from Gothic 1 Remake or other files for which it does not have the appropriate distribution rights.<br />
24. The installation and operation of G1R:MP should be based on game files legally owned by the User, where such files are necessary for the Platform to operate.<br />
25. The use of official G1R:MP infrastructure to distribute models, textures, animations, recordings, music, dialogue, maps, executable files, or other protected assets extracted from the game is prohibited if the person publishing them does not have the right to redistribute them.<br />
26. Preparing project packages intended to replace a User's legal copy of Gothic 1 Remake by including significant game files or assets is prohibited.<br />
27. The User's own original materials, or materials for which the User holds an appropriate license, may be permitted.<br />
28. The Project Team is responsible for content and files distributed by it in connection with use of the Platform.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter VII. Cheats and Unfair Interference with Gameplay</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 7. Prohibition of Cheating</span><br />
<br />
29. Using cheats in G1R:MP is prohibited.<br />
30. Cheating may include, among other things, modifying process memory, using trainers, manipulating network traffic, falsifying packets, bypassing security measures, and using unauthorized automation that provides an advantage.<br />
31. Creating, distributing, advertising, and selling cheats intended for G1R:MP is prohibited.<br />
32. Confirmed use of cheats may result in a permanent Global Player Ban across the entire Platform.<br />
33. The Administration may base its decision on recordings, logs, technical data, observations, screenshots, and other credible evidence.<br />
34. A report alone does not establish guilt.<br />
35. The Administration is not required to disclose cheat-detection methods or information that would enable security measures to be bypassed.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter VIII. Security, Malware, and Attacks</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 8. Malicious Software and Attacks</span><br />
<br />
36. The distribution of malicious software, including viruses, trojans, ransomware, spyware, keyloggers, stealers, backdoors, and other harmful programs, is strictly prohibited.<br />
37. Presenting a malicious file as a G1R:MP client, update, launcher, mod, plugin, or administrative tool is prohibited.<br />
38. DoS/DDoS attacks, attempts at unauthorized access, account takeovers, data theft, and other actions against the infrastructure of G1R:MP, Projects, or Users are prohibited.<br />
39. Serious security violations may result in a permanent Global Player Ban and a Global Project Ban if the violation is connected with the activities of its team.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter IX. Harassment and Conduct Toward Others</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 9. Harassment</span><br />
<br />
40. Harassing, intimidating, threatening, persistently insulting, and organizing coordinated actions against G1R:MP Users are prohibited.<br />
41. Collecting and using information found about a User for the purpose of humiliating, intimidating, defaming, blackmailing, or causing a sense of danger, in particular by publishing such information, is prohibited.<br />
42. Point 41 also applies where the information was previously publicly available.<br />
43. Encouraging other people to harass a specific User is prohibited.<br />
44. If a violation is committed by a member of a Project Team in connection with their project activities, the Administration may impose a penalty on the Project as well.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter X. Spam and Disruption of Communication</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 10. Spam</span><br />
<br />
45. Spamming chats, the forum, reporting systems, the server list, and other G1R:MP functions is prohibited.<br />
46. Spam includes, in particular, repeatedly sending the same content, flooding a chat with messages or characters, mass advertising, automatically sending messages, and actions that disrupt normal communication.<br />
47. Manually performed activity may also be considered spam if its scale, intensity, or repetition clearly disrupts use of the Platform.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XI. Data, Privacy, and IP Addresses</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 11. User Data and Public Technical Information</span><br />
<br />
48. Users should exercise caution when publishing their own data.<br />
49. IP addresses used by Users to connect to the Platform — specifically to the servers and the forum — are treated as public data.<br />
50. IP addresses published by Users in public sections of the G1R:MP forum are publicly visible to persons who have access to those sections.<br />
51. The IP address and port of a public server may be publicly displayed on the forum or server list if this is necessary to allow other Users to connect.<br />
52. The person publishing a server address is responsible for having the authority to disclose it and should be aware that a public server address is not confidential information within the place where it has been published.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XII. Servers and the Server List</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 12. Rules for Publishing Servers</span><br />
<br />
53. The official server list may contain servers genuinely intended for gameplay or justified testing.<br />
54. Creating servers intended solely as a joke, for spam, impersonation, fraud, advertising unrelated to G1R:MP, or destabilizing the server list is prohibited.<br />
55. Mass publication of empty, fictitious, or automatically generated servers is prohibited.<br />
56. A server name may not mislead others as to its owner, status, or official affiliation with G1R:MP.<br />
57. The Administration may hide or remove a server that is non-functional, a test server, fictitious, spam-related, dangerous, or in violation of the Rules.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XIII. Projects and Project Teams</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 13. Project Responsibility</span><br />
<br />
58. The Project Owner is responsible for organizing the team, official project channels and servers, and responding to serious violations committed by persons acting on behalf of the Project.<br />
59. The Project Team should moderate its official channels and servers with regard to piracy, malware, harassment, and other serious violations of the Rules.<br />
60. A single violation by an ordinary Player does not automatically make the entire Project Team liable.<br />
61. However, the Administration may penalize the entire Project Team if the violation is committed by the Project Owner, by a team member acting in connection with the Project, or if the Project Team knowingly tolerates serious and repeated violations.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XIV. Banned Persons in Project Teams</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 14. Prohibition on Participation by an Officially Banned Person</span><br />
<br />
62. A person subject to an official ban prohibiting participation in G1R:MP Project Teams shall be informed of this prohibition by the Administration each time.<br />
63. A Project may not have on its team a person who is subject to a valid prohibition on participating in Projects.<br />
64. If a Project Team includes a person subject to such a prohibition, the Project is subject to a Global Server or Project Ban.<br />
65. A team member means not only a person formally listed as part of the team, but also a person actually involved in creating, managing, programming, moderating, maintaining infrastructure, representing, or making decisions concerning the Project.<br />
66. Falsely removing a person from a team while continuing to allow their actual participation in the Project is prohibited.<br />
67. Circumvention of the prohibition may include, among other things, using another person's account, performing duties through intermediaries, hidden administrative permissions, or undisclosed management of the Project.<br />
68. A Global Project Ban resulting from the presence of a prohibited person does not automatically mean an individual ban for all other team members unless they themselves committed violations.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XV. Server Rules</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 15.</span><br />
<br />
69. A Server Owner may establish additional gameplay rules.<br />
70. Server rules may not override G1R:MP rules concerning, among other things, cheating, piracy, malware, security, ban circumvention, and participation of persons subject to a global prohibition.<br />
71. Penalties imposed by the Administration of a specific server are separate from global G1R:MP penalties.<br />
72. As a rule, G1R:MP Administration does not resolve disputes arising solely from the internal rules of a private server.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XVI. Advertising and Promotion</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 16.</span><br />
<br />
73. Project advertising is permitted only in the places and forms provided for by the Platform's rules.<br />
74. Mass advertising, impersonating other Projects, providing false information about competing Projects, and using advertising bots without the required permission are prohibited.<br />
75. Competition between Projects may not take the form of harassment, sabotage, technical attacks, or organized raids.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XVII. Bugs, Exploits, and Vulnerabilities</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 17.</span><br />
<br />
76. Knowingly exploiting G1R:MP bugs in order to gain an unfair advantage, bypass security measures, obtain unauthorized data, or destabilize services is prohibited.<br />
77. A User who discovers a serious security vulnerability should report it to the Administration rather than publish instructions enabling its exploitation.<br />
78. The Administration may refrain from imposing a penalty if the action was solely a necessary test intended to document a bug and caused no harm.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XVIII. Circumvention of Penalties</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 18.</span><br />
<br />
79. Circumventing global and local restrictions imposed by the G1R:MP Administration is prohibited.<br />
80. Circumventing a penalty may include using additional accounts, other people's accounts, concealing one's identity in order to participate in a Project again, or other deliberate actions intended to nullify the effect of a ban.<br />
81. Helping a banned person circumvent a penalty may constitute a separate violation of the Rules.<br />
82. An attempt to circumvent a ban may result in an extension of the penalty, conversion of a temporary penalty into a permanent one, or additional sanctions.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XIX. Accounts and Impersonation</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 19.</span><br />
<br />
83. A User is responsible for the security of their account and should not share login credentials with third parties.<br />
84. Sharing an account with another person does not guarantee cancellation of a penalty for actions performed using that account.<br />
85. The Administration may order a change of an account, Project, or server name if it deliberately misleads others.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XX. Reports and Evidence</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 20.</span><br />
<br />
86. Users may report violations through channels designated by the Administration.<br />
87. Where possible, a report should contain the User's or Project's name, a description of the incident, the date or approximate time, and available evidence.<br />
88. The Administration may consider recordings, screenshots, logs, technical data, messages, and other credible evidence.<br />
89. The Administration may refuse to consider an obviously false or spam report, a report that cannot be verified, or one concerning solely the internal rules of a server.<br />
90. Knowingly submitting false reports and organizing coordinated reporting against innocent persons are prohibited.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXI. Administration Procedures</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 21.</span><br />
<br />
91. The Administration considers cases based on available information, the nature of the violation, and the credibility of the evidence.<br />
92. In the event of a security threat, the Administration may impose a temporary restriction before the full proceedings have been completed.<br />
93. The Administration is not required to publicly disclose internal moderation methods, security measures, cheat-detection mechanisms, or data that would enable security measures to be bypassed.<br />
94. Decisions may take into account the scale of the violation, its intentional nature, harm caused, previous offenses, attempts to remedy the harm, and the User's conduct after the incident.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXII. Global Player Bans</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 22. Nature of a Global Player Ban</span><br />
<br />
95. G1R:MP uses Global Player Bans.<br />
96. A Global Player Ban is imposed by the G1R:MP Administration and applies at the level of the entire Platform to the extent specified in the penalty decision.<br />
97. A Global Player Ban may prevent a Player from using G1R:MP gameplay regardless of the server on which the violation occurred.<br />
98. A Global Player Ban may be temporary or permanent.<br />
99. In cases of particularly serious violations, especially confirmed cheating, knowingly distributing malware, serious attacks on infrastructure, or serious circumvention of penalties, the Administration may impose a permanent Global Player Ban.<br />
100. The penalized person is informed of the penalty imposed and, where possible and safe, of its basis.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXIII. Global Server and Project Bans</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 23. Nature of a Global Server or Project Ban</span><br />
<br />
101. G1R:MP uses Global Server and Project Bans.<br />
102. A Global Server or Project Ban may result in a server being removed or blocked from the official G1R:MP server list and refusal to republish it for the duration of the penalty.<br />
103. A Global Project Ban may cover all servers operating under the same Project or entity if necessary to enforce the penalty.<br />
104. A Global Server or Project Ban may be imposed, among other things, for serious violations committed by its team, knowingly tolerating piracy or malware, circumventing penalties, harmful actions against the Platform, or the presence on the team of a person subject to an official prohibition on participation in Projects.<br />
105. Changing the server name, domain, formal owner, or publishing account does not invalidate a Global Ban if it is in fact the same Project or an attempt to circumvent the penalty.<br />
106. A Global Project Ban does not necessarily mean an automatic Global Player Ban for all ordinary Players who previously used that server.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXIV. Other Penalties</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 24. Types of Sanctions</span><br />
<br />
107. For violations of the Rules, the Administration may apply, in addition to the penalties referred to in Chapters XXII and XXIII, an instruction, warning, server hiding, or another proportionate restriction necessary for the security of the Platform.<br />
108. If a specific provision does not prescribe one mandatory penalty, the Administration selects a sanction appropriate to the circumstances of the case.<br />
109. A temporary penalty may have a duration determined individually.<br />
110. The Administration is not required to precede a serious penalty with a warning.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXV. Appeals</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 25.</span><br />
<br />
111. A User may appeal a penalty in the manner specified by the Administration if an appeals system is available for the relevant type of sanction.<br />
112. An appeal should concern a specific decision and present arguments or new information.<br />
113. Abuse of the appeals process, threats, spam, and repeatedly submitting the same case after a final decision may be left without further consideration.<br />
114. The Administration may designate a decision as final.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXVI. User Content and Fraud</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 26.</span><br />
<br />
115. A User is responsible for content published through the Platform.<br />
116. Publishing phishing, fake login pages, fake updates, scams, fraud, extortion, and other content intended to obtain Users' data or money is prohibited.<br />
117. The Administration may remove content that violates the Rules regardless of any penalty imposed on its author.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXVII. Actions Outside the Platform</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 27.</span><br />
<br />
118. As a rule, the Administration does not intervene in private conflicts unrelated to G1R:MP.<br />
119. Actions outside the official Platform may be taken into account if they are directly connected with G1R:MP and concern security, harassment, cheats, malware, circumvention of penalties, piracy, or official Project Team activity.<br />
120. Mere dislike or a private conflict between Users does not automatically constitute grounds for a global penalty.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXVIII. Server Infrastructure Security</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 28.</span><br />
<br />
121. A Server Owner is responsible for securing their own infrastructure and should apply appropriate technical measures.<br />
122. Publishing a server on the G1R:MP list does not mean that G1R:MP assumes responsibility for the security of the owner's private infrastructure.<br />
123. Publicly providing a server address means that the address may be visible to Platform Users.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXIX. Platform Availability</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 29.</span><br />
<br />
124. G1R:MP does not guarantee uninterrupted availability of its services.<br />
125. The Platform may be temporarily disabled or restricted due to updates, failures, technical work, problems with external services, or security incidents.<br />
126. The Administration may temporarily disable a specific function if required for the security or stability of the Platform.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXX. Amendments to the Rules</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 30.</span><br />
<br />
127. The Rules may be amended as G1R:MP develops, new functions and threats emerge, abuses occur, or it becomes necessary to clarify the rules.<br />
128. The current version of the Rules is published in the officially designated place.<br />
129. Users should familiarize themselves with the current version of the rules before continuing to use the Platform after changes have been announced.<br />
<br />
<hr class="mycode_hr" />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Chapter XXXI. Final Provisions</span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">§ 31.</span><br />
<br />
130. The purpose of the Rules is to ensure a fair, safe, and stable environment for the G1R:MP community.<br />
131. The Rules should not be interpreted in a manner that permits obvious circumvention of their provisions by exploiting linguistic loopholes or superficial organizational changes.<br />
132. If a particular action is not expressly listed but clearly corresponds to conduct prohibited by a given provision, the Administration may assess it in accordance with the purpose of that provision.<br />
133. In matters not regulated herein, the Administration may make decisions necessary for the security and proper functioning of G1R:MP, while maintaining proportionality.<br />
134. The Rules enter into force on the date specified at their official publication.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Welcome to the Colony — Board Rules]]></title>
			<link>https://g1r-mp.com/forum/showthread.php?tid=2</link>
			<pubDate>Thu, 06 Aug 2026 20:24:08 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://g1r-mp.com/forum/member.php?action=profile&uid=2">LordStrange</a>]]></dc:creator>
			<guid isPermaLink="false">https://g1r-mp.com/forum/showthread.php?tid=2</guid>
			<description><![CDATA[<span style="font-weight: bold;" class="mycode_b">Welcome to the Colony — Board Rules</span><br />
These rules apply everywhere on the G1R:MP forum. Staff enforce them with common sense rather than to the letter, but ignorance of them isn't a defence. By posting here you agree to follow them.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">1. Treat people decently.</span> Disagree with ideas, not people. No personal attacks, harassment, or hate speech targeting anyone's nationality, ethnicity, religion, gender, sexuality or disability. This community spans a lot of countries and a translated insult still counts.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">2. This is a legal fan project.</span> G1R:MP is an independent modification and requires a legitimate copy of Gothic 1 Remake. Do not request, link to, or hint at pirated copies, cracked executables, key generators or ripped game assets. Posts doing so are removed without discussion and usually earn a ban. Don't ask staff to make exceptions.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">3. Post in the right place.</span> English is the working language of the main forums. If you'd rather write in your own language, we have sections for Deutsch, Polski, Русский, Čeština &amp; Slovenčina, Español and Français — use them freely, and don't post the same thread in both a language section and the English one.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">4. Search before you ask.</span> A large share of support questions are already answered. If yours isn't, open a thread in Support &amp; Troubleshooting with your mod version, your OS, what you were doing when it broke, and the relevant log or error text. "It doesn't work" gets you nowhere.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">5. Make scripting help easy to give.</span> In Scripting Help, wrap code in tags<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>for example:

helloworld</code></div></div><br />
Post the actual error message rather than a paraphrase, and trim your example to the part that fails. Say what you expected to happen and what happened instead. Nobody is going to debug three hundred unformatted lines for you.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">6. Bug reports need to be reproducible.</span> One bug per thread in Bug Reports, with steps someone else can follow. Check whether it's already reported before opening a new thread, and add to that thread instead if it is.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">7. Server advertising has its own forum and its own rules.</span> One thread per server in Server Advertising, kept updated rather than reposted. Don't advertise servers in signatures outside that forum, don't recruit players by private message unsolicited, and don't badmouth competing servers.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">8. Credit other people's work.</span> If you release something built on someone else's script, resource or asset, credit them and respect whatever licence they published under. Reuploading another author's release as your own is treated as seriously as piracy.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">9. No spam, no advertising, no drama.</span> That includes referral links, unrelated commercial promotion, thread bumping, post farming, and reviving dead threads to argue. Keep signatures reasonable in size and avoid images that stretch the layout.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">10. One account per person.</span> Alternate accounts made to evade a ban, inflate a poll or argue with yourself will result in all of them being closed. If you've lost access to your account, contact staff rather than registering again.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">11. Let staff moderate.</span> If you see a rule broken, report it and move on — don't reply to police it yourself. If you disagree with a moderator's decision, take it up with them privately rather than opening a thread about it.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">12. Enforcement.</span> Depending on severity we'll warn, edit or remove content, temporarily restrict posting, or ban. Piracy, hate speech and ban evasion skip straight to the end of that list. Appeals go by private message to an administrator, once, politely.<br />
These rules will change as the community grows. Material updates will be announced in Announcements, and the date above at the top tells you when this post was last revised.]]></description>
			<content:encoded><![CDATA[<span style="font-weight: bold;" class="mycode_b">Welcome to the Colony — Board Rules</span><br />
These rules apply everywhere on the G1R:MP forum. Staff enforce them with common sense rather than to the letter, but ignorance of them isn't a defence. By posting here you agree to follow them.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">1. Treat people decently.</span> Disagree with ideas, not people. No personal attacks, harassment, or hate speech targeting anyone's nationality, ethnicity, religion, gender, sexuality or disability. This community spans a lot of countries and a translated insult still counts.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">2. This is a legal fan project.</span> G1R:MP is an independent modification and requires a legitimate copy of Gothic 1 Remake. Do not request, link to, or hint at pirated copies, cracked executables, key generators or ripped game assets. Posts doing so are removed without discussion and usually earn a ban. Don't ask staff to make exceptions.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">3. Post in the right place.</span> English is the working language of the main forums. If you'd rather write in your own language, we have sections for Deutsch, Polski, Русский, Čeština &amp; Slovenčina, Español and Français — use them freely, and don't post the same thread in both a language section and the English one.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">4. Search before you ask.</span> A large share of support questions are already answered. If yours isn't, open a thread in Support &amp; Troubleshooting with your mod version, your OS, what you were doing when it broke, and the relevant log or error text. "It doesn't work" gets you nowhere.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">5. Make scripting help easy to give.</span> In Scripting Help, wrap code in tags<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>for example:

helloworld</code></div></div><br />
Post the actual error message rather than a paraphrase, and trim your example to the part that fails. Say what you expected to happen and what happened instead. Nobody is going to debug three hundred unformatted lines for you.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">6. Bug reports need to be reproducible.</span> One bug per thread in Bug Reports, with steps someone else can follow. Check whether it's already reported before opening a new thread, and add to that thread instead if it is.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">7. Server advertising has its own forum and its own rules.</span> One thread per server in Server Advertising, kept updated rather than reposted. Don't advertise servers in signatures outside that forum, don't recruit players by private message unsolicited, and don't badmouth competing servers.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">8. Credit other people's work.</span> If you release something built on someone else's script, resource or asset, credit them and respect whatever licence they published under. Reuploading another author's release as your own is treated as seriously as piracy.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">9. No spam, no advertising, no drama.</span> That includes referral links, unrelated commercial promotion, thread bumping, post farming, and reviving dead threads to argue. Keep signatures reasonable in size and avoid images that stretch the layout.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">10. One account per person.</span> Alternate accounts made to evade a ban, inflate a poll or argue with yourself will result in all of them being closed. If you've lost access to your account, contact staff rather than registering again.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">11. Let staff moderate.</span> If you see a rule broken, report it and move on — don't reply to police it yourself. If you disagree with a moderator's decision, take it up with them privately rather than opening a thread about it.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">12. Enforcement.</span> Depending on severity we'll warn, edit or remove content, temporarily restrict posting, or ban. Piracy, hate speech and ban evasion skip straight to the end of that list. Appeals go by private message to an administrator, once, politely.<br />
These rules will change as the community grows. Material updates will be announced in Announcements, and the date above at the top tells you when this post was last revised.]]></content:encoded>
		</item>
	</channel>
</rss>