<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Overhauling the FAF ruleset]]></title><description><![CDATA[<p dir="auto">FAF rules, or rather, their application has gone downhill for quite some time. I keep hearing about more and more completely ridiculous bans based on some very ridiculous rules (or how they are written).<br />
I completely understand that rules have to be written rather broad to not have someone go around them. But improving on the current ruleset is imo the best first step to fixing this.<br />
(FYI: this is a different and more broad topic compared to my overwork of the exploit-rules)</p>
<p dir="auto">Here is the rules page: <a href="https://faforever.com/rules" rel="nofollow ugc">https://faforever.com/rules</a></p>
<hr />
<p dir="auto">So here are some rules and my recommended changes, including reasoning (going from top the bottom according to the rules page):</p>
<ol>
<li><img src="/assets/uploads/files/1760564779337-1cc77d7a-b2b5-44f2-a3e6-0d0e3d204155-image.png" alt="1cc77d7a-b2b5-44f2-a3e6-0d0e3d204155-image.png" class=" img-fluid img-markdown" /><br />
-&gt; Friendly fire — Do not maliciously reclaim allied units or purposefully fire on allies</li>
</ol>
<p dir="auto">Reasoning is quite simple. Units are in the way of me building something (doesn’t have to be on the front, can literally be anywhere) – for example a random T1 air unit. In theory I get banned because I reclaim this if he doesn’t respond to pings. Not always can you just build somewhere else.<br />
(Check rule-wording on the rule of “Helping enemy team” -&gt; here the word maliciously is used, so I think its appropriate here aswell)</p>
<hr />
<ol start="2">
<li><img src="/assets/uploads/files/1760564790179-0203e7f6-d9ea-478b-a135-ab985112921d-image.png" alt="0203e7f6-d9ea-478b-a135-ab985112921d-image.png" class=" img-fluid img-markdown" /><br />
-&gt;</li>
</ol>
<p dir="auto">Not quite sure how to formulate a better rule here, because this rule shouldn’t even exist. A simple chat message like “Make Torps!!!” (based on a recent ban) can be bannable. You should be allowed to tell someone how to play, BUT not be toxic about it or spam it. Telling someone how to play, even if they didn’t ask for it, is completely normal, just like in any other game.</p>
<hr />
<ol start="3">
<li><img src="/assets/uploads/files/1760564801950-d40312d2-171c-4f34-ba61-37c5df028a7d-image.png" alt="d40312d2-171c-4f34-ba61-37c5df028a7d-image.png" class=" img-fluid img-markdown" /><br />
-&gt;</li>
</ol>
<p dir="auto">Another rule where I am not 100% sure how to formulate it correctly. But I think this is pretty nonsense, because 1) try to tell this to anyone on Dual Gap, Setons or Astro (literally the most played maps). If I take a mex which DOES belong to someone else, you can 95% of the time see him reclaiming it to get it back.<br />
Or lets take a different example where there actually are no “reserved” mass extractors: Mapgen. So in theory I can get a spawn with 3 mex and try to rush some air with it, meanwhile the guy next to me takes every mex around me and doesn’t want to give me any. So how is this not game ruining for the player who doesn’t get any?<br />
Tons of example more here but I think you get the point.</p>
<hr />
<ol start="4">
<li><img src="/assets/uploads/files/1760564876410-71e6d256-c050-4f78-a954-6cd61c6fc524-image.png" alt="71e6d256-c050-4f78-a954-6cd61c6fc524-image.png" class=" img-fluid img-markdown" /></li>
</ol>
<p dir="auto">Here the point of lagging games or connection issues are missing. I have had games where the lag (for me) was horrible, and I did not want to play that. But apparently nobody else in this game shared this opinion and wanted to continue. So according to these rules I am forced to play, or I can get banned upon report. So, I think we can add:</p>
<ul>
<li>Leaving in case of very noticeable connection issues is allowed.</li>
</ul>
<hr />
<ol start="5">
<li><img src="/assets/uploads/files/1760564893782-a09ef8eb-928f-463e-9b73-88c300113f03-image.png" alt="a09ef8eb-928f-463e-9b73-88c300113f03-image.png" class=" img-fluid img-markdown" /><br />
	Do not self-destruct, also known as or “CTRL-K”, your base or significant quantities of units, unless your team agrees.<br />
This was a big topic for me and others because of, shockingly, some more bans. My intention of changing the rule is that if the game is over the team can ctrl k their bases as they wish, as long as they all agree. Yes, that includes 1 person ctrl-k-ing his base and the rest continues playing, because the team should be able to do whatever they want with their bases as a team. The enemy team should have no say whatsoever on this, because why would they? How is self destructing a base more game ruining than recalling? In both cases you “take the fun of destroying the enemy base”.</li>
</ol>
<hr />
<ol start="6">
<li>Exploits</li>
</ol>
<p dir="auto">I don’t think I need to mention it here, because there is an entire thread of this, which will (hopefully) at some point made into a proposal by me. Just wanted to have this here on the list to get an overview of what I’d like to get changed.</p>
<hr />
<ol start="7">
<li><img src="/assets/uploads/files/1760564937434-6bc3e1e6-cff1-49b1-972e-6ab44b08eda0-image.png" alt="6bc3e1e6-cff1-49b1-972e-6ab44b08eda0-image.png" class=" img-fluid img-markdown" /></li>
</ol>
<p dir="auto">This rule is fine, but I just wanted to post this here for context for the actual rule I think needs changing:</p>
<p dir="auto"><img src="/assets/uploads/files/1760564944500-ff549c9f-f937-4c9a-a407-e6fec40b69c4-image.png" alt="ff549c9f-f937-4c9a-a407-e6fec40b69c4-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">So the first rule allows me to insult people if its not based on the reasons mentioned. But this rule means I must always be respectful. So, respectfully, fuck off (a joke).<br />
I don’t want to imply here that I would like everyone to go mental and insult. But I would like some more leeway here.</p>
<p dir="auto">Here is the chat-log of a recent ban. Now I don’t know if its because of toxicity or “controlling behaviour”:</p>
<p dir="auto">Player 1 to allies: DO SOMETHYING<br />
Player 1  to allies: STOP SLURPING AND PLAY<br />
Player 1 to allies: YOU CLOWN<br />
Player 1 to allies: YOUR OPPONENT IS NORTHH<br />
Player 2 to allies: relax, we're doing fine<br />
Player 1 to allies: no we are not<br />
Player 1 to allies: he's drooling over his keyboard<br />
Player 1 to allies: TORP NOW OR I QUIT<br />
Player 1 to allies: 10 seconds to comply<br />
Player 1 to allies: WALK THEM UP MID<br />
Player 1 to all: can't play this with drool zone</p>
<p dir="auto">But in my opinion even this should not be bannable for multiple reasons:</p>
<ol>
<li>whoever got “flamed” here did not reply or say anything (as in “stop” or something like that)</li>
<li>There is a mute function</li>
</ol>
<p dir="auto">There are no direct insults anywhere in this (I sure hope we can at least call people a clown...) so I think the way to go about this is not moderation-&gt;ban but rather the mute function ingame. But if you disagree I’d love to hear why exactly, because this doesn’t even haven an insult (yes, its not necessarily respectful, but still “normal”).</p>
<hr />
<ol start="8">
<li>And here we have the biggest of them all:<br />
<img src="/assets/uploads/files/1760564968537-242c93de-7130-44b2-9a71-98d50a0c4efc-image.png" alt="242c93de-7130-44b2-9a71-98d50a0c4efc-image.png" class=" img-fluid img-markdown" /></li>
</ol>
<p dir="auto">The discussion of bans. The foe of all moderators (for some reason).<br />
Jokes aside I don’t even know how or where to start here. Why is this not allowed? Is the reason to not have spam on the forum / chat that discusses bans? Basically this means bans are discussed everywhere but the FAF discord / forum. I get that the moderators don’t want to publicly reply everywhere something is posted regarding a ban, but this rule could simply be changed to moderators won’t do public statements regarding bans. This way moderators themselves can discuss it (if they want), but don’t need to and also don’t need to reply.<br />
For these kind of discussions (and the exploit-thread) it is quite annoying to not be allowed to talk about the specific bans.<br />
I don’t know if in other similar sized communities this kind of rule exists, but I can’t imagine so (feel free to prove me wrong though, this is just my opinion). I know this is not the intention, but what it actually feels like is that we have tons of ridiculous bans and then can’t talk about them (this is not just my opinion / feeling).</p>
<hr />
<p dir="auto">So I posted this specifically in the general chat and not association forum to get responses / ideas from all. I just hope it doesn't escalate into something again and then locked.</p>
]]></description><link>https://forum.faforever.com/topic/9583/overhauling-the-faf-ruleset</link><generator>RSS for Node</generator><lastBuildDate>Wed, 03 Jun 2026 23:48:34 GMT</lastBuildDate><atom:link href="https://forum.faforever.com/topic/9583.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 15 Oct 2025 21:55:03 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Overhauling the FAF ruleset on Thu, 16 Oct 2025 11:47:40 GMT]]></title><description><![CDATA[<p dir="auto">This has been discussed repeatedly before. Many of the points you state are misleading, and you have already been told to discuss in the FAF Association sections of the forum if you think particular rules should be changed.  Given this, and the discussion of specific cases, this thread has been locked.</p>
]]></description><link>https://forum.faforever.com/post/69802</link><guid isPermaLink="true">https://forum.faforever.com/post/69802</guid><dc:creator><![CDATA[maudlin27]]></dc:creator><pubDate>Thu, 16 Oct 2025 11:47:40 GMT</pubDate></item><item><title><![CDATA[Reply to Overhauling the FAF ruleset on Thu, 16 Oct 2025 11:11:40 GMT]]></title><description><![CDATA[<p dir="auto">I see this Nuggets guy has a lot of free time..<br />
Challenge us into a 3rd match of a Clan War!<br />
We will be respectful -_-  (probably)</p>
]]></description><link>https://forum.faforever.com/post/69801</link><guid isPermaLink="true">https://forum.faforever.com/post/69801</guid><dc:creator><![CDATA[Swatoslav]]></dc:creator><pubDate>Thu, 16 Oct 2025 11:11:40 GMT</pubDate></item><item><title><![CDATA[Reply to Overhauling the FAF ruleset on Thu, 16 Oct 2025 09:43:10 GMT]]></title><description><![CDATA[<p dir="auto">i don't think that warrants a ban unless it happens every other game or something, it's pretty light toxicity</p>
]]></description><link>https://forum.faforever.com/post/69800</link><guid isPermaLink="true">https://forum.faforever.com/post/69800</guid><dc:creator><![CDATA[waffelzNoob]]></dc:creator><pubDate>Thu, 16 Oct 2025 09:43:10 GMT</pubDate></item><item><title><![CDATA[Reply to Overhauling the FAF ruleset on Thu, 16 Oct 2025 08:54:52 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/speed2" aria-label="Profile: speed2">@<bdi>speed2</bdi></a> I thought the same way like he literally showed a reasonable ban for insulting. Calling someone a clown is totally unacceptable the way he did in caps and with his intentionial meaning. Besides the overrall toxic behavior and telling someone how to play</p>
]]></description><link>https://forum.faforever.com/post/69799</link><guid isPermaLink="true">https://forum.faforever.com/post/69799</guid><dc:creator><![CDATA[Newbie_recoverin]]></dc:creator><pubDate>Thu, 16 Oct 2025 08:54:52 GMT</pubDate></item><item><title><![CDATA[Reply to Overhauling the FAF ruleset on Thu, 16 Oct 2025 08:28:02 GMT]]></title><description><![CDATA[<p dir="auto">So you want to change the rule<br />
from: do not insult<br />
to: be respectful<br />
And then you show an example of someone being totally not respectful and say thats fine behaviour<br />
The fact that you can mute someone isnt get out of jail free card for them</p>
]]></description><link>https://forum.faforever.com/post/69798</link><guid isPermaLink="true">https://forum.faforever.com/post/69798</guid><dc:creator><![CDATA[speed2]]></dc:creator><pubDate>Thu, 16 Oct 2025 08:28:02 GMT</pubDate></item><item><title><![CDATA[Reply to Overhauling the FAF ruleset on Thu, 16 Oct 2025 00:24:52 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/waffelznoob" aria-label="Profile: waffelzNoob">@<bdi>waffelzNoob</bdi></a> said in <a href="/post/69792">Overhauling the FAF ruleset</a>:</p>
<blockquote>
<p dir="auto">was foley banned?</p>
</blockquote>
<p dir="auto">No</p>
]]></description><link>https://forum.faforever.com/post/69793</link><guid isPermaLink="true">https://forum.faforever.com/post/69793</guid><dc:creator><![CDATA[Nuggets]]></dc:creator><pubDate>Thu, 16 Oct 2025 00:24:52 GMT</pubDate></item><item><title><![CDATA[Reply to Overhauling the FAF ruleset on Wed, 15 Oct 2025 23:09:34 GMT]]></title><description><![CDATA[<p dir="auto">was foley banned?</p>
]]></description><link>https://forum.faforever.com/post/69792</link><guid isPermaLink="true">https://forum.faforever.com/post/69792</guid><dc:creator><![CDATA[waffelzNoob]]></dc:creator><pubDate>Wed, 15 Oct 2025 23:09:34 GMT</pubDate></item><item><title><![CDATA[Reply to Overhauling the FAF ruleset on Wed, 15 Oct 2025 22:06:27 GMT]]></title><description><![CDATA[<p dir="auto">shout out to the drooler</p>
]]></description><link>https://forum.faforever.com/post/69790</link><guid isPermaLink="true">https://forum.faforever.com/post/69790</guid><dc:creator><![CDATA[KnownSniper]]></dc:creator><pubDate>Wed, 15 Oct 2025 22:06:27 GMT</pubDate></item><item><title><![CDATA[Reply to Overhauling the FAF ruleset on Wed, 15 Oct 2025 21:58:23 GMT]]></title><description><![CDATA[<p dir="auto">No man quick trigger bans are good for a dying community</p>
]]></description><link>https://forum.faforever.com/post/69789</link><guid isPermaLink="true">https://forum.faforever.com/post/69789</guid><dc:creator><![CDATA[Deli]]></dc:creator><pubDate>Wed, 15 Oct 2025 21:58:23 GMT</pubDate></item></channel></rss>