How Did It Happen?

Does anyone know how the change in the map occured? Many of the disputed line town are now LUXON? There are no missions I can find to aid in taking them back, since currently my team is KURZICK. I just dont get it....

When did this happen and what towns?

I've been playing in the Quarry the weekend so I haven't thrown down in PVE for the weekend, what happened?

Sorry if I sound like a total noob, I really am still new to the game.

When you check the full map, you will see a red/blue line. This denotes the Luxon/Kurzick battle lines. The line shifts depending on which side is winning more in Alliance Battles.

Guild Wars was recently updated with a momentum algorithm. Once one side wins enough to push past neutral, they need a lower ratio of wins to push to the next deeper map.

I'm sure this Double Faction weekend is basically a beta test for the algorithm and it will be adjusted so that the line doesn't shift wildly as it has been.

That makes sense...you know, I have noticed that when the game first came out, most went Kurzick...but now the pendulum has swung heavily the other way. I know my team is in an alliance, but there is not an alliance. Crazy...I hope this does not effect the movement of my other chars to finish the game.

Maybe the disputed towns are mainly Luxon because Luxons had a big win swing? Kurzicks will swing back soon. They changed momentum bonus so it actualy makes a difference, and now AB actually makes the line move like it was meant to.

Nah, ownership of a town won't affect your ability to work through the storyline at all. It may mildly inconvenience you when you have to go somewhere else to sell your treasure though. =)

Thx to all who responded...it looks like my team has decided to move towards Luxon allegience anyhow. The boss wants to see what is on the other side of the map...so see ya over there!!!

not recently.. it was AGES ago.. even after they implemented this "momentum rule" for months after the line was still very steady at pretty much dead centre.

Only in the past week has this suddenly changed, and its all happened just when our entire alliance were getting error code 30 - and were not able to log on for well over 30 minutes.

I personally smell a rat.