Several players have crashed logged at one point or another, I am not one of them. But logged will not go back to Massacre because of Sinister and Sprog aka Jackal.

Nice hit Pulsar, one of the best new players to play the game.

GLotR Freedom.

Great hit, you saw his error (not being on when your fleet is down) and took advantage of it. Congrats and enjoy the spoils...Build more LGs with it, gotta catch up to you know who...lol

GLotR Taolon, won't take you long.

Sweet hit, enjoy the spoils.

Here is what I think: You cannot cover all cases of rules. Just like in real life with the legal system. If we see someone breaking a rule, we report it, just as in real life. We let the legal system, or in this case, the owners of the game, decide what should be done. Maybe the judge was in good mo...

Not really, you could have your fleet in the air for awhile and figure it out. I am not saying each time the update changes, but more like once per week or there abouts.

May I suggest the following then:

Run a cron job that would randomize the time of the update, instead of having it the same all the time. Would make the game more interesting, no?

Maybe you misunderstood me, I was asking if there is a rule against alliance mates crashing each other just so no one else can get the fleet? Both players continue to play the game.

Zorg, Player A sees Player B's fleet sitting. Player A and Player B are in the same alliance. Player A crashes player B's fleet after he sees the 15 min next to the players name in the alliance list. Is there a rule against this? If not, why not? There should be either a) a rule stating that allianc...

Sprog wrote:Congrats to Pulsar and Wrath....would question the other after recent Zorg flamings but it's just a game right....

I followed the rules and am allowed to flame in UoH.


Thanks to the rest of the players that congratulated us.