Retirement rule updated. Here is the rule fully with past and new additions:

1.A retirement crash will result in account deletion. If you want to keep your account you must not crash your fleet.
2.Anyone who receives or conducts a retirement crash of at least 50M total damage, must inform administration via email at webmaster@zorgempire.net in the following form:

Code: Select all
Title:
Retirement Crash on <Server Name>
Body:
Retiring player: <username>
Receiver: <username>
All relative battle reports.



3.Switched accounts are not allowed to crash their fleet on retirement.


Involved accounts that violate this rule, will be terminated.

DISCLAIMER:
This rule is a follow up to the MILKING RULE which primarily states:
Every account must be played to its own full benefit.

Therefore Fleet crashing on purpose is ILLEGAL, whether is on retirement or not and this is why it will not be included in the Rule page.
Any player conducting a retirement crash is subject to the sub-rule either he is aware of it or not.
The sub rule only exists to give the choice to the fair player, who truly wants to retire, what to do of his own fleet.

Any attempted taints (even if they are not mentioned here) will be regarded as an attempt to mock administration and fair players everywhere. The penalty for this will result in instant termination of any involved accounts, including players that were aware of the deal but did not report it.

when this rule was implanted a noticed sommething there is way to bypass this and we see when some friend crush to other account
the will not get banned.
my question is why you added rule that not works
this rule should stop players crush each others fleet by switching account or retirement .

How to bypass:
simple we wil use 4 account and we wil name it A,B,C,D.

Well let say players with account A,B,D are freinds C is other players.
so
player A decided to retire he crush fleet on B account B account send email and all stuff is needed to admin.
next player A goes Blue.
now Player C ho is not friend decided to crush to account B his fleet of course player B will send email and everything be fine
C goes Blue now player D also decided to retire and crush his fleet on account B again same routine by email sending to admin.
same player D goes Blue.
now player B gets tons resurses and he can build lots stuff and fleet .However after same time accounts A,C will be back and the will done again same to feed that account up.

When player retire or sommething it should just retire without any fleetcrushing .
was that player freind of his or teammember it should just enter v mode.

With this you ruin players ho work very hard with single account to be top 30 .
as long this continue players will still feed each other.

http://i1097.photobucket.com/albums/g343/Akatcuki/Peinxd2323555.jpg

Pein, you should re-read the rule. It covers account switching and retirement crashing, however the TD must be at least 50 million in order for the rule to apply. If you paid attention, you'd notice that the penalty for violating this rule is the involved accounts are deleted. In other words, anyone who does a retirement crash of 50 mil+ TD has their account deleted, and I imagine if the recipient neglects notifying administration then they lose their account as well. Therefore, your bypass is invalid.

Read more carefully next time before you claim a rule is not working as it should, this one is fine.

if the crush fleet as excuse of retirement it should both players get deleted
thats unfair to players ho play fair and squire

http://i1097.photobucket.com/albums/g343/Akatcuki/Peinxd2323555.jpg

Pein wrote:if the crush fleet as excuse of retirement it should both players get deleted
thats unfair to players ho play fair and squire

The problem with that is what if the person that gets the fleet crashed into them was unaware of this plan?

Since already one player got banned, I recommend that you all read the Fleet Crashing on Retirement rule once again.

Read it carefully.

Let me help you:
Fleet Crashing on Retirement rule is a sub rule of milking. It is activated on a players request and only if this one is honestly going into retirement.

So what Pein describes here, is already covered.

Zorg wrote:Since already one player got banned, I recommend that you all read the Fleet Crashing on Retirement rule once again.

Read it carefully.

Let me help you:
Fleet Crashing on Retirement rule is a sub rule of milking. It is activated on a players request and only if this one is honestly going into retirement.

So what Pein describes here, is already covered.

admin could you clear one thing up for me if someone finds a fleet they cannot crash and offers to give me the info for 20% of the profit is this against the rules?

You are off topic but i'll answer;

This can be regarded as a mercenary payment. Generally, loot sharing is permitted and it can happen with various ways (DF sharing, losses recovery etc). The only problem in this cases is that administration is not always aware of the transport reason. This is why it is better doing such dispatches shortly after the hit. If not, you will have to follow the regular resource sending limitations.

Generally, as long as it is a honest trade, no real limitations apply. Always remember the golden rule of milking which is that every account must be played to its own full benefit.

It is the dishonest trades and players that are trying to bend these rules in their favor, that are our main focus in the milking rule. Whether the other player is your rl buddy or just a kind-hearted fellow willing to help or just a deceived ally, we do not care; accounts must be played to their OWN benefit.

thankyou for the clerification mr zorg