Jump to content
  • Sign Up

Kidel.2057

Members
  • Posts

    588
  • Joined

  • Last visited

Everything posted by Kidel.2057

  1. What is called is relevant if it's a deliberate attempt to avoid calling it a nerf (or, to be honest, a quick dirty fix to Energy Sigils on Vindicator, something that should have been obvious from day one to anyone developing this spec) and is, again (7th time?), the main point of this thread. If you think it's irrelevant there is the door. You're not forced to reply. And there are multiple classes with weaponswap that ALSO trigger "in swap" sigils with F skills, such as Firebrand, Necromancer and Spectre. I don't know why you're only thinking about Elementalist and Engineer when ALL classes worked like Revenant did, and it was intended by the dev making Revenant to leave it like that and see (and it has been ok for like 6 years, until Vindicator came with dodgespam, which is still a thing in pve).
  2. Some people are discussing that the nerf is unfair because it's made only to quickly address the dodge spam of Vindicator, yet it nerfs all the other builds and the flow of Revenant in general, also creating an exception in how Guild Wars 2 works. Are you going to simply repeat that ANet has the right to do so? It's true. But we don't have to like it AND we don't buy it was a bug.
  3. At the moment Alliance defaults to Archemorus the first time and later defaults to St. Viktor any time you change map or dismount. This is clearly not an intended behaviour, however even fixing this and defaulting to Archemorus would not be ideal for support builds. I have suggested it in the general feedback thread but it's lost in 45 pages of comments. What I'm asking is to make the default one selectable via trait. This would fix the problem and also help the flow and the build making. At the moment there is no incentive to swap between the two, so it only happens out of necessity. Archemorus could be the default one, with Saint Viktor becoming the new default one if the player selects Redemptor's Sermon (or Saint of zu Heltzer).
  4. The title of the thread quotes the whole sentence from the notes. The first post of this thread is this: And the first page is all people discussing how this could never be called a bug and it's just another nerf. I'm starting to thing you're not unable to formulate proper reasoning, but you simply can't get the meaning of what you read.
  5. Nobody is arguing that. For the 5th time. Are you doing this on purpose? Stop changing reality. You can say it's pointless to argue semantics in your opinion, fine, but don't claim anything else is happening here.
  6. So you should probably stop posting here, right? You don't care how it is called yet you're replying in a thread about how it's called.
  7. We are arguing how they are calling it. For the 4th time. Impressive how you can read a sentence 3 times and still not get the meaning. Or maybe you're just trolling. If you're not here to discuss the way they called it, then have fun talking to the mirror you've been desperately trying to climb. And also please explain to all of us why that behaviour has been called "a bug" only on Revenant while it's still there on literally every other class in some form.
  8. I'd be ok with them saying "we decided to change it" or "we nerfed it". Again, for the third time: the problem is that they're trying to claim it was a bug, when it's a fact that it was intended behaviour. The fact that they now want a new behaviour (and only on Revenant) doesn't make that retroactively a bug. It's simply a change. Hell, I'm a CTO and I'm arguing issue types with a random dude on a game forum. It's like if you have a wireframe and a mockup saying that the forum buttons have to be red, and after 6 years you go around saying "well, we now want the buttons to be blue, so the red buttons are a bug". Sorry, it doesn't work like that and devs at ANet know it perfectly. So claiming it's a bugfix it's probably a deliberate way to hide the fifth nerf in a patchnote hoping people would not recognize it (or hoping to get guys like you blindly defending them through mirror climbing).
  9. So are you just going to completely ignore the 2 posts made by Roy saying that the "on swap" triggering on legendswap was supposed to work like that? And are you also ignoring all the other F skills of all the other classes (literally) that trigger "on swap" sigils? You're claiming "that's how it was supposed to work" with no basis and directly contradicting facts. No, they trigger on F skills too. And also on kits.
  10. goes immediately into saint if I do that. And if I wasp to arch and go into a mount or through a portal, it still goes back to saint. 😕 Am I doing something wrong?
  11. the problem with camping arch is that you revert to viktor every time you dismount. And if you dismount in water it even triggers heal or urn at random.
  12. how is 37k high compared to the other specs?
  13. Interesting how you completely omitted from your quote the part where I explain WHY it's stupid. The reason being you can still virtually trigger "on swap" sigils via legendswap IF you give up your weaponswap. So it's objectively bad design. In case you decide to skip part of my post again, I'll repeat: it's objectively bad design. That being said, other professions have similar F mechanics that DO trigger "on swap" sigils and work exactly like legendswap used to do. Guardian tomes, Necro shroud, Spectre shroud. All those F skills are used very often, even more so than legendswap on vindicator. So just to recap we have: 1. A change that was called a "bugfix" when we have direct proof (2 forum posts) of the original Rev developer claiming it's intended by design. This alone should shut you up if you had any decency. 2. A way to still trigger "on swap" sigils via legendswap if you just give up a second weapon (aka: bad design). The part of my post you avoided to quote. 3. Other classes that have similar mechanisms, so the game just got more inconsistent. Something you claim it's different from legendswap, please explain how. 4. A full list of nerfs on core Rev and Vindicator. From one hand making Vindicator better than other specs (especially Herald), while nerfing Vindicator in all game modes. Sorry to burst your bubble, but that patch note entry was made only to justify a nerf to Sigil of Energy on Vindicator and try to pass it as a bugfix. And that's absolutely hilarious. Again: this is all to nerf Vindicator and try to avoid calling it a nerf, since Revenant got nerfed big time in this patch and for no reason at all. They didn't want to upset people and in my eyes that just backfired. Hope you give up your mirror climbing dude. It's getting embarassing.
  14. Well you described it way differently the first time. Now I agree it's a bug. And I shouldn't have to test it, frankly.
  15. and nobody cares about that, so you're talking to yourself. Have fun I guess. And the change IS actually stupid. Now to achieve the result of triggering sigils while swapping legends I can: 1. equip 2 of the same weapon (like GS) 2. make a macro to weaponswap on legendswap This virtually reverts the revenant back to the time when it didn't have weaponswap (and effects only triggered on legendswap).
  16. Going underwater after dismounting from skyscale automatically sumons Urn of Saint Viktor. I have Jalis on land and it's slotted to Alliance underwater. So when it swaps to Alliance because it goes underwater, it summons Urn automatically. It only happens after I land on water from a mount I think.
  17. most people here are not complaining because it changed, but because it was passed as a "bugfix". Your ability to miss the point entirely in every single thread is baffling. And we all know they changed it to nerf rune of energy on Vindicator. Calling it a bug is just false (objectively since Roy Chronacher explicitly said it was intended) and hypocritical.
  18. I don't think this is a bad thing. Heals rightfully take priority over skills.
  19. Never intended to change anything between "BETA" 4 and "RELEASE", sure. Why did we even think something so preposterous.
  20. they didn't change a single thing or fix a single bug since the second Vindicator beta. They just nerfed core rev, heavily.
  21. Did they even fix any Vindicator bug? It all seems identical to the last beta, except the huge core Revenant nerfs.
  22. so instead of buffing Alliance they nerfec core legends... And Glint too. All facets from 10 to 5 targets...
×
×
  • Create New...