MEGA BUG>

Advanced search

[hillbilly]

Few minutes ago.
kreel mothership warps back to ally border planet >> s349 with scout mission and being killed on the same  tick by incoming enemy ships which were ment to be catched BY THAT MATERSHIP !!!!
THERE WASNT ANY KIND OF WAR ON THAT PLANET BEFORE..



HAL.. This time no excuse for that..

Standart galaxy number 163..

If we dont see that problem solved and the galaxy rollbacked  with the zeebs fleet snared by our evade scouts and the warps, i will actually stop space for good. Also my ally the turian will stop also..

[Jorn_Stones]

Well, this was the first galaxy I joined after returning to the game, and now this happened.
Wether it was by a bug, or by cheating so a certain alliance had the advantage instead of us, if it is not fixed I see no reason to join another galaxy ever, and will simply quit the game. I will simply not continue to play a game where either bugs like this remain unfixed and allow an alliance to win a decisive battle instead of losing it, or where the admins themselves manipulate the game so they can win all the time.

- Jorn

[hillbilly]

Well, its not a cheat. Its just a random bug..

[Skythorn]

our report shows the Mater ship not being targeted in the first tick, nor being killed that tick

----------------

s242 08/07/2012
19:58:29 Your battle report
Attack on (Playboy) planet s242, round 1
Condition: Blue
Own fleets left:2 ships left:168 lost:0
Ally fleets left:1 ships left:443 lost:0
Enemy fleets left:1 ships left:1 lost:0
No shots fired.
1 enemy ships decloaked out of nowhere and executed a stunning strike to our fleets !

----------------

What did yours show?

[Skythorn]

dumb question - does the mater ship need to be set to 'ambush' on a planet of it's allies? Or does it just do its thing no mater what it's orders?

[Hal]

Well, this was the first galaxy I joined after returning to the game, and now this happened.
Wether it was by a bug, or by cheating so a certain alliance had the advantage instead of us, if it is not fixed I see no reason to join another galaxy ever, and will simply quit the game. I will simply not continue to play a game where either bugs like this remain unfixed and allow an alliance to win a decisive battle instead of losing it, or where the admins themselves manipulate the game so they can win all the time.

- Jorn

Oh yeah. I cheat every time I play. Even when I havent logged in in like 36 hours because I have been slammed at work, I'm cheating.


........


(and yes, that was sarcasm)


(but not about the havent logged in in 36 hrs, thats true).

[Hal]

Few minutes ago.
kreel mothership warps back to ally border planet >> s349 with scout mission and being killed on the same  tick by incoming enemy ships which were ment to be catched BY THAT MATERSHIP !!!!
THERE WASNT ANY KIND OF WAR ON THAT PLANET BEFORE..



HAL.. This time no excuse for that..

Standart galaxy number 163..

If we dont see that problem solved and the galaxy rollbacked  with the zeebs fleet snared by our evade scouts and the warps, i will actually stop space for good. Also my ally the turian will stop also..

Can I see the battle report please?


<edit> Skythorn's battle report contradicts your statement. Do you have the actual battle report to backup your statement of a bug?

<edit 2> wait I see thats on a different planet. let me look back in.

[Mistress of Mayhem]

Couple of things-

Don't think it's a bug, and definitely not a cheat.

Likely, I would think stealth/ambush.  One of my favorites.  Can't remember if the orders need to be set to ambush, or if stealth is good enough.

Rollbacks in Space happen very infrequently.

[Mistress of Mayhem]

Good godz, do we have to do this again?  Lame lame lame.  I will not tolerate lameness. Sorry.  And FFS, grow up!

Well, this was the first galaxy I joined after returning to the game, and now this happened.
Wether it was by a bug, or by cheating so a certain alliance had the advantage instead of us, if it is not fixed I see no reason to join another galaxy ever, and will simply quit the game. I will simply not continue to play a game where either bugs like this remain unfixed and allow an alliance to win a decisive battle instead of losing it, or where the admins themselves manipulate the game so they can win all the time.

- Jorn

Oh yeah. I cheat every time I play. Even when I havent logged in in like 36 hours because I have been slammed at work, I'm cheating.


........


(and yes, that was sarcasm)


(but not about the havent logged in in 36 hrs, thats true).

[Hal]

is this the battle report you are talking about?

 s349 08/07/2012
19:58:29

Your battle report

Attack on (Simpsonites) planet s349, round 1
Condition: Green
Own fleets left:3 ships left:493 lost:1
Ally fleets left:6 ships left:84 lost:0
Enemy fleets left:0 ships left:0 lost:2
Own shots: fired 1442, misses 97
Enemy shots: fired 4, misses 0
Your bombardment has killed 4108141 of 4200000 population
6 mines destroyed by point defense
16 mines destroyed by allied point defense
Mines triggered:19
Mines hitting your forces 11, misses 6
Mines hitting alliance forces 12, misses 7
Your forces destroyed 2 ships
You gained 138 ore salvage
Your forces destroyed 1114 buildings
Your forces conquered the system

 

[mavolence]

dumb question - does the mater ship need to be set to 'ambush' on a planet of it's allies? Or does it just do its thing no mater what it's orders?

No, do not put KMS in ambush... that screws up the 1st tick of battle KMS advantage for that first tick of battle which is the only tick you can get your one "free" shot at the enemy and hold them a tick w/o being shot back.

[Hal]

ok, I looked in the database from 15 minutes before that battle report that i posted above. I'm assuming that is the correct battle. You said it was on scoutback, so I checked for fleets that were sent from s349 (heading to s60, thats the number, not sure the name). There was only one fleet sent from s349 that was moving in the DB, and is had orders #6 which im pretty sure is scout orders. It tracks back to a medium scout with this ship name: Mater MS v1.0. It appears from the DB that you thought you were scouting back a matership but actually you scouted back a scout. Based on your recollection of events, is this possible? Were your orders set before or after the :45 minute mark?

[DirectorPhleg]

LOL i just love these threads.

[Skythorn]

I'm a bit pissed - an accusation was thrown, a tantrum was made, Hal took hard to find time out of his life to try and trace down what happened where, and there is no reply or commentary from any of the parties involved.  He also received quite nastily voiced assumptions, and still replied reasonably.

In my view, its really all quite rude.

I dont mind the tantrum, we all get upset, but staying away from the outcomes of your behaviour, to me, sucks!

[Hal]

well, life goes on. Thread closed...