Guild Wars 2

I greatly enjoy the WvWvW jumping puzzles. I also enjoy going there with my guild-mates and the competition as well as the hilarity that can ensue. I spent entirely WAY to much time in the Eternal Battlegrounds jumping puzzle last night with many of my guild-mates. Sorrows Furnace and Darkhaven were in there as well and we have many back and forth battles.

At 2 separate occasions last night, Sorrows Furnace rolled through the jumping puzzle with what seemed like a group of 20 players, face-rolling everyone in their path. It certainly made for a challenging time.

However, I’d like to make a plea to ArenaNet to switch the jumping puzzles in all 4 battlegrounds to a different instance, separate from the main battlefields. It occurred to me last night that our participation within the jumping puzzles contributed to a lack of forces on the main battlefield that would have helped out the main forces immensely. Beyond that, our presence within the jumping puzzle added our numbers to the Eternal Battlegrounds population cap. Without our direct participation in WvWvW battles on the main field, we were essentially useless to the overall combat actions and prevented those players who WANTED to be, from getting into the battleground.

I’m all for jumping puzzles that involve PvP but making them separate from the actual battlefields and NOT included in the population cap would be preferable if not ideal. This way anyone can have fun within the puzzles while not hurting their own servers efforts on the battlefield.

Thank you for the consideration.

Except, you go in, lose your spot and have to queue up to get back in to the rest of wvw. Or potentially have to queue to get into jump puzzles too…

Lativado.2308:

Except, you go in, lose your spot and have to queue up to get back in. Or potentially have to queue to get into jump puzzles too…

This is not a concern I have really. I find it hard to believe that there would be so many PvPers within any one particular jumping puzzle, whether that be a borderland or the Eternal Battlegrounds puzzle, that we would experience a queue for them.

I would think that if the jumping puzzles were transferred to a separate instance from the main fields of battle, all the current mechanics would still be in place as well as all of the current rewards. Queuing for any WvWvW battle would remain the same and once inside a jumping puzzle you could either accept a queue pop-up, re-queue, or even decline the queue and not go in at all.

It’s seems like a non-issue to me. No offense intended of course and thank you for the reply.

I don’t mean to trash your idea, but you didn’t even read my whole post so, meh. The issue I saw was losing your spot in wvw, the queues for getting into the puzzles was an afterthought (though I could see it being potentially exploitable … dance party to deny other servers access to “free siege blueprints” anyone?).

I did indeed read your whole post and I fail to see how one could lose their spot in a WvWvW queue if they go into an instanced PvP puzzle in the suggestion I made above.

If you queue for WvWvW and go into a PvE instance, do you lose your place in queue? Nope. The queueing system (I hope) would work in exactly the same manner as it does now:

1. You try to go into Eternal Battlegrounds and get a queue.
2. You queue up for Eternal battlegrounds and decide to do a PvP jumping puzzle while you wait for queue pop
3. You progress along in the jumping puzzle and 1/2 way through the puzzle the queue pops up and asks if you want to travel to the Eternal battlegrounds.
4. You accept the queue, enter into Eternal Battlegrounds and leave the jumping puzzle.

I guess I can clarify that the ENTRANCE to the PvP jumping puzzles would have to be located OUTSIDE of the battlegrounds/borderlands and no longer accessible from inside those lands. To leave them inside the battlegrounds would defeat the purpose of having them separate from the battlegrounds to begin with. Entrance to these puzzle would have to be accessed in the PvE realm…or even ideally, the Mists.

What is the issue again?