Author Topic: bug in 55  (Read 449 times)

Offline Warsun

  • Zinc Member
  • *
  • Posts: 94
bug in 55
« on: March 23, 2003, 12:58:44 AM »
Seems like that bug in 55 makes it useless to fight this scenario, the front is never going to move. Well see the same landscape everyday, because thats where everyone fights... I hope this map is not put again until that bug is fixed by placing a map room there. I've fought in this Tunisia map for 3 scenarios....

I know everyone likes it because it's easy to find the fight. But it's nice to see some new landscape sometimes even in the desert, without going out on my own to explore map and to see the front move to different areas. Axis would have already captured that field 10 times over. Maybe the allies need to put some effort into capturing the field we are taking off from, so we have atleast a field we can capture back... :)


thanks...

Offline Arlo

  • Radioactive Member
  • *******
  • Posts: 24759
bug in 55
« Reply #1 on: March 23, 2003, 01:20:38 AM »
It's a bug, true. Why the heck does it make it "useless to fight this scenario"? Does having a field you can't take equate to having a scratch you can't itch? I don't think resets are the be-all, end -all of the CT. Nor do I think the midnight milkrun is, either. Ask about the Slot map. ;)

Offline Warsun

  • Zinc Member
  • *
  • Posts: 94
bug in 55
« Reply #2 on: March 23, 2003, 01:37:24 AM »
I just want the chance to crash into a mountain or a different dune or something crashing and dying ontop of the previous dead bodies literating the desert is getting to me lol.... guess it's not useless but very repetive.... ;)

Offline Grissom

  • Zinc Member
  • *
  • Posts: 92
bug in 55
« Reply #3 on: March 25, 2003, 11:28:53 AM »
make 55 a ROOK base...  then everyone can ignore it... :D

Offline Arlo

  • Radioactive Member
  • *******
  • Posts: 24759
bug in 55
« Reply #4 on: March 27, 2003, 05:02:39 PM »
It got changed manually to a Knight base last night. Same result ... gonna be ignored.

  • I know the fella with the magic button didn't realize that the allied players had agreed not to mount an offensive on A2 because of the bug at A55.
  • I know the guy with the magic button didn't realize that allied players spent alot of time reminding axis players that attacking A55 was only going to pork the base and make it a pita to enjoy the air to air encounters between it and A2 (occasionally at a cost of death by typing).
  • I know that the guy with the magic button didn't realize that allied players were completely ignoring the axis bombers and goonies that decided to keep throwing themselves at A55 because they obviously couldn't grasp the problem.
  • I know that mentioning that to the guy with the magic button wasn't gonna get A55 changed back (since that would essentially just piss off both sides instead of one).
  • I just wish the guy with the magic button would wait long enough to converse with the players on both sides about making a "spur of the moment" change to a map where the action is instead of having a kneejerk reaction when he sees something or hears a complaint from just one side.

The problem isn't "fixed" ... it's just an axis advantage instead of an allied one now. The guy with the magic button isn't there all the time to manually "fix" things. When/if some player decides to take A55 back ... what should be done then? Call the guy with the magic button first?

Yeah ... until it's fixed ... Haven's suggestions makes the most sense.

Oh well. *ShruG*
« Last Edit: March 27, 2003, 05:46:29 PM by Arlo »

Offline Warsun

  • Zinc Member
  • *
  • Posts: 94
bug in 55
« Reply #5 on: March 27, 2003, 05:27:05 PM »
Yea Rook base......