Guild Wars 2

Keeping apart the point about unliking this map coming back (I won’t argue about it here), why Anet didn’t fix the old bugs and exploits that this map had in the past, before throwing it back to the game?

Wait, you don’t know what exploits and bugs I mean?

- Guards entering in combat with npcs and contesting structures without reason (as happened with the Garrison in EOTM, btw).

- Siege being placed in respawn, into zones where are supposed to not be possible to place (a very old exploit used by lame players for sieging and defending towers in the north).

- Structure doors that can’t be crossed after breaking when the door is broken at same time than siege is blocked with Siege Disabler.

- Enemy players being able to cross the respawn doors and entering in.

I wait an answer from the devs about all this, since it’s supposed these old failures should be fixed time ago.

I have no idea why, they stated from the beginning alpine would be brought back into a rotation, and to not fix existing issues makes no sense. I can understand if they didn’t have the time before with all the updates going into wvw recently. But now that alpine is back the existing issues need to be fixed.

Siege being able to be put up at the citadel area is a big one it makes holding the north towers impossible.

The WvW playerbase was leaking like a burst pipe after HoT release and the new DBL.

Anet had to do something, and the one thing was players wanted the alpine BL back. So Anet gave us those, only updated it with the new HoT features, ignored the bugs and slapped it on our plate like that old school dinner lady who smoked and spat every 10 seconds.

As stated above. They were probably too busy trying to solve the extreme negativity and player loss to worry about fixing spaghetti code. In this case I’d be willing to assume cycling ABL back in this quick required the use of panic mode.

On the bright side, they did lower the number of wildlife in both abl and eb, which is really great. And they finally disabled the mosquito event in EB. Hopefully the pre-existing issues with alpine will be worked on in upcoming updates.

Well, that’s why they’re bringing it back.

We’ll be beta testing the changes, even though we shouldn’t have to. However, given the state the game is, I say just get it going now and move forward.

The issues with ABL weren’t addressed since they weren’t ready to bring it back yet but felt the need to do so since they were now under new direction from a different game director. I think a lot of us would be shocked on the number of changes and how the game was delayed at launch because of staffing changes internally as people were moved or replaced during development. I wouldn’t fault the teams hard work on probably a quick change over, nor would I fault them for not applying changes to a map that was out of play and still had open issues if other deadlines were applied to them. And no, even if Anet uses “soon” too often I doubt that their teams weren’t given internal deadline to meet, never seen a business that didn’t self impose deadlines else nothing would ever advance.

That said, continue to report bugs else they might not be prioritized correctly in the long run.