Guild Wars 2

It’s simple, really. Make it possible to go into first person mode via a specific tonic, or perhaps make existing tonics have a first person mode available. Not only would this allow for costume brawl to be experienced differently, but making first person view available only in tonic form would solve all the issues that ArenaNet developers seem to have with a system-wide first person view.

It wouldn’t give anyone an unfair advantage in combat (can’t fight while in tonic form) and it won’t make people ignore their character model (tonic form isn’t their original character). I can’t really think of a feasible reason why first person mode being available in tonics is a bad idea, but if an ArenaNet dev would care to point out any flaws, I’m sure I could think of another way to implement a first person view without damaging anything in the game. =)

Strange behavior with Ghastly Shortbow

The first screenshot shows the hero panel. I am a Male Asura Thief with nothing equipped other than the Ghastly Shortbow. The Ghastly Shortbow is obtained from the Ascalonian Catacombs dungeon vendor in Lion’s Arch. The following problem appears regardless of any equipment added or removed, traits added or removed, or utility skills added or removed.

(The rest of the screenshots take place at night.)

The second screenshot shows that while the weapon is “sheathed” it has the mist particle effect as well as the blueish tint. This is abnormal in comparison to most Ghastly weapons because at night, when sheathed, they only retain the blueish tint, then when unsheathed, the mist particle effect is added.

The third screenshot shows the weapon unsheathed and it appears as it should be, with the blueish tint and mist particle effect.

The fourth screenshot shows the weapon after an auto attack was used (ability one). However, any ability used has the same result: the bow no longer has the mist particle effect and it only retains the bluish tint.

The fifth and sixth screenshots show the weapon after it is sheathed and unsheathed again. The blueish tint remains, but the mist particle effect never returns unless you unequip the bow and put it in your inventory, then reequip it. However, the initial problem will also remain as previously stated in the previous paragraphs.

This has been an issue since launch and the other Ghastly weapons had this issue before. Most of them were fixed except for the Ghastly Shortbow. I also heard the Ghastly Longbow has the same problem, but I cannot confirm this.

I browsed the forum and found out through several bug reports that any asura using any piece of the Protean armor set (and not hiding it) causes any back piece to bug out. In this instance, the bug is for the Quiver of Swift Flight on my asuran thief.

1st pic is neutral with no Protean armor equipped.
2nd is Protean shoulders equipped, but hidden
3rd is Protean shoulder equipped and unhidden. Note the change in the back piece.
4th and 5th are Protean chest and Protean legs respectively creating the same bug.

Pretty simple. Instead of having an invisible anti-bot/farm code, use a captcha system instead. That way, the bots won’t be able to benefit from their ToS violation and people that are farming legitimately don’t get penalized for it. Instead of the anti-bot/farm code triggering, have a captcha pop up. If the captcha is entered correctly, the anti-bot/farm code does not go into effect.

People might find it intrusive or immersion breaking, but I feel the benefits outweigh any detriment a million to one. If people want to farm legitimately, they shouldn’t be punished for it. The current system in place punishes bots as well as legitimate farmers. It absolutely needs to change, and I firmly believe captcha or a similar system is the answer.

Yeah, corrected.

I wonder if they skimmed over it and assumed I was complaining about 1% failure rate, Lol.

I still have no idea why they haven’t fixed this. There are 3 minor traits and 1 major trait for Opening Strike and they are all useless. Does ArenaNet just not care about this issue? They haven’t even mentioned it’s being worked on or that they’re even aware of it.

This makes me worried. I would much rather have this fixed than any non-responsive pet issues.

Opening Strike for the pet AND the ranger are still extremely bugged. Opening Strike does NOT work about 99% of the time.

Please, PLEASE fix this.

Edit: Typo

The only thing that is bugged is the visual description. One rune will not give you all six benefits. I tested this today when I bought a set of 6 and noticed the bug.

So, yeah. No exploit possible, but the visual bug is annoying.

Sometimes it works, but most of the time it doesn’t. When the icon is available in the “buff bar”, autoattacks will occasionally trigger it, but skills will rarely trigger it. For instance, the greatsword 3 skill will absolutely never cause an opening strike.

Considering that in the marksmanship trait line all three minor traits pertain to opening strike, this is pretty sad. It’s like the minor traits don’t even exist.

I haven’t tested it with every weapon and every skill, but with bows it seems like it almost never happens.