Guild Wars 2

Guild Wars 2

Reaper Scythe Bug
Why has the scythe bug with the necro still not been fixed after almost a decade?

The scythe still disappears after activating Reaper Shroud,
so that you fight with your fists. It looks stupid and this bug has been around for so long...

It's really disappointing when you play for hours and it happens so often that you just spin your character around even though he doesn't have a scythe.

Entries go back to 2018 or even older. why isn't it just fixed? :steamsad:
Last edited by Nafiganza; Jan 5 @ 11:00pm
< >
Showing 1-13 of 13 comments
ExERain Jan 10 @ 8:00am 
The dev team is not very well managed, the current game is very unbalanced and even with classes not worth touching, they only focusing primarly on making expansion and cash shop then fixing the game, of course they fixed something but takes ages its like at times the team is not existing.
I actually have very few problems with the game when it comes to bugs. I hardly ever have any problems in the main story or with activities and achievements. But little things like the scythe thing are really annoying... and I don't understand why they can't fix it, as it has a big impact on the look of a class.

As a Mesmer you want to see all of your mirror, how bad would it be if you couldn't see mirror anymore because of bugs. Just as a comparison.
graphical bugs with no effect on gameplay are the lowest of low priorities.
Nafiganza Jan 10 @ 11:08am 
Originally posted by SinisterSlay:
graphical bugs with no effect on gameplay are the lowest of low priorities.

How many years have to pass before graphical bugs that affect the functionality of a class are fixed?

The priority of designing a new hammer for the shop is of course higher than fixing bugs...

I understand that all other classes except Reaper see no reason to fix the problem. But for someone who only plays the game because of this class because it is so much fun, it bothers them more than others :sadelf:
Last edited by Nafiganza; Jan 10 @ 11:09am
LSD Jan 10 @ 11:16am 
Bugs that have been in the game this long will just never be fixed. Firstly because the dev team is barebones as can be right now, and secondly because the amount of layoffs they've done since the games release means they have nobody with the skill to actually fix it.

See also: Guardian mace #3. When you use it, you get a big visual effect with shields rotating around you. The problem is, they often don't despawn. In a typical match, you'll have at least 3 or 4 sets of this visual effect spinning around you, and it only gets worse the longer you play. Hooray for visual effect spam and incompetent devs!
Originally posted by Nafiganza:
Originally posted by SinisterSlay:
graphical bugs with no effect on gameplay are the lowest of low priorities.

How many years have to pass before graphical bugs that affect the functionality of a class are fixed?

The priority of designing a new hammer for the shop is of course higher than fixing bugs...

I understand that all other classes except Reaper see no reason to fix the problem. But for someone who only plays the game because of this class because it is so much fun, it bothers them more than others :sadelf:
It's still a problem that is not easily reproducable.
If you can from a fresh start of the game, make a video of the exact steps to reproduce the problem, and send that to ANET, they can probably fix it. But that is the minimum required of you to get it fixed. Otherwise, the problem has to happen to a dev while they have dev tools open monitoring for it or some other issue. And even then, ANET might operate under a dev culture where you are not allowed to fix bugs you find unless they are verified by a stakeholder. This is an oddly common culture for companies with tight deadlines.

If I had to guess, its a graphics pipeline issue. GW2 has a ton of them. You can see some funny ones like if you mount up on your raptor or something, the game wastes time first rendering the stock raptor, then swaps it out for your skinned version. With the assumption these 2 processes would happen at the same time, but they race condition and it wastes time loading the wrong one first. You will find race conditions like this all over the game and I bet the reaper weapon disappearing is one of them.
Last edited by SinisterSlay; Jan 10 @ 11:34am
Nafiganza Jan 10 @ 11:44am 
Originally posted by SinisterSlay:
Originally posted by Nafiganza:

How many years have to pass before graphical bugs that affect the functionality of a class are fixed?

The priority of designing a new hammer for the shop is of course higher than fixing bugs...

I understand that all other classes except Reaper see no reason to fix the problem. But for someone who only plays the game because of this class because it is so much fun, it bothers them more than others :sadelf:
It's still a problem that is not easily reproducable.
If you can from a fresh start of the game, make a video of the exact steps to reproduce the problem, and send that to ANET, they can probably fix it. But that is the minimum required of you to get it fixed. Otherwise, the problem has to happen to a dev while they have dev tools open monitoring for it or some other issue. And even then, ANET might operate under a dev culture where you are not allowed to fix bugs you find unless they are verified by a stakeholder. This is an oddly common culture for companies with tight deadlines.

If I had to guess, its a graphics pipeline issue. GW2 has a ton of them. You can see some funny ones like if you mount up on your raptor or something, the game wastes time first rendering the stock raptor, then swaps it out for your skinned version. With the assumption these 2 processes would happen at the same time, but they race condition and it wastes time loading the wrong one first. You will find race conditions like this all over the game and I bet the reaper weapon disappearing is one of them.

That's right, I noticed that with the raptor too. Or that the skimmer disappears when you open the map while you're riding on it. It comes back as soon as you're floating, but it disappears when you open the map :lunar2019deadpanpig:
Nafiganza Jan 10 @ 11:46am 
Originally posted by LSD:
Bugs that have been in the game this long will just never be fixed. Firstly because the dev team is barebones as can be right now, and secondly because the amount of layoffs they've done since the games release means they have nobody with the skill to actually fix it.

See also: Guardian mace #3. When you use it, you get a big visual effect with shields rotating around you. The problem is, they often don't despawn. In a typical match, you'll have at least 3 or 4 sets of this visual effect spinning around you, and it only gets worse the longer you play. Hooray for visual effect spam and incompetent devs!

That sounds pretty terrible too. And I still think that these graphic bugs are no small thing... they can really ruin your day, because you don't just see them once in a while, but for hours, days and weeks :er_sad:
Originally posted by Nafiganza:
How many years have to pass before graphical bugs that affect the functionality of a class are fixed?

There's a "bug" in WvWvW where the fire temple map has a significant error that makes it practically impossible to use in that area, just because a dev set it to the wrong asset. It looks completely out of place and would be apparent to everybody that it doesn't belong there. That has been around forever too without a fix, among hundreds of other bugs that would be very easy to fix. Honestly, I don't know how bad it looks for the studio or if this is a management issue, but a single junior dev could fix a lot of the obvious and apparent bugs. Hell, an intern could do it.
Originally posted by Little Strawberry:
Originally posted by Nafiganza:
How many years have to pass before graphical bugs that affect the functionality of a class are fixed?

There's a "bug" in WvWvW where the fire temple map has a significant error that makes it practically impossible to use in that area, just because a dev set it to the wrong asset. It looks completely out of place and would be apparent to everybody that it doesn't belong there. That has been around forever too without a fix, among hundreds of other bugs that would be very easy to fix. Honestly, I don't know how bad it looks for the studio or if this is a management issue, but a single junior dev could fix a lot of the obvious and apparent bugs. Hell, an intern could do it.

What looks easy might not be easy at all.

For years, they didn't add any extra hairstyles to the cash shop in Fallout 76. You had a bunch to choose from in game. The cash shop had 2 extra you could buy. But the Devs could not add any more.

They could add masks, helmets, hats, whatever. Not hairstyles.

You cannot make the argument that Horse-Armor-Bethesda wouldn't do an easy fix to sell extra hairstyles.

There was some bizarre code issue that caused server problems when they added extra hairstyles to buy. It took them about 5 years to fix it. That's just how coding goes. Some things that look simple from the outside are actually complex issues.
Originally posted by Little Strawberry:
Originally posted by Nafiganza:
How many years have to pass before graphical bugs that affect the functionality of a class are fixed?

There's a "bug" in WvWvW where the fire temple map has a significant error that makes it practically impossible to use in that area, just because a dev set it to the wrong asset. It looks completely out of place and would be apparent to everybody that it doesn't belong there. That has been around forever too without a fix, among hundreds of other bugs that would be very easy to fix. Honestly, I don't know how bad it looks for the studio or if this is a management issue, but a single junior dev could fix a lot of the obvious and apparent bugs. Hell, an intern could do it.

That sounds really bad. I understand that there are priorities for bugs, but I cannot understand why bugs that have been around for many years are ignored.
Originally posted by Hefutoxin:
Originally posted by Little Strawberry:

There's a "bug" in WvWvW where the fire temple map has a significant error that makes it practically impossible to use in that area, just because a dev set it to the wrong asset. It looks completely out of place and would be apparent to everybody that it doesn't belong there. That has been around forever too without a fix, among hundreds of other bugs that would be very easy to fix. Honestly, I don't know how bad it looks for the studio or if this is a management issue, but a single junior dev could fix a lot of the obvious and apparent bugs. Hell, an intern could do it.

What looks easy might not be easy at all.

For years, they didn't add any extra hairstyles to the cash shop in Fallout 76. You had a bunch to choose from in game. The cash shop had 2 extra you could buy. But the Devs could not add any more.

They could add masks, helmets, hats, whatever. Not hairstyles.

You cannot make the argument that Horse-Armor-Bethesda wouldn't do an easy fix to sell extra hairstyles.

There was some bizarre code issue that caused server problems when they added extra hairstyles to buy. It took them about 5 years to fix it. That's just how coding goes. Some things that look simple from the outside are actually complex issues.

You describe the problems of our time very well.
Developers spend 5 years solving problems and fixing something for the shop instead of worrying about everything else.
Fallout 76 is the best example of something like that, the game has more bugs than you can imagine and they spend 5 years looking for a solution to sell additional hairstyles :cozybethesda:
Originally posted by Nafiganza:
Originally posted by SinisterSlay:
graphical bugs with no effect on gameplay are the lowest of low priorities.

How many years have to pass before graphical bugs that affect the functionality of a class are fixed?

The priority of designing a new hammer for the shop is of course higher than fixing bugs...

I understand that all other classes except Reaper see no reason to fix the problem. But for someone who only plays the game because of this class because it is so much fun, it bothers them more than others :sadelf:
I am a Reaper too and have never seen this bug, also i would not care if i did, i would just chuckle at it, as it seems was explained this does not actually effect your damage output or the functionality of your game-play, it is just visual correct?
I understand better than most, as I am a Coder, how complicated "Small" things like this can be.
If it does not stop your damage, or actually Effect your game-play, other than the visuals sometimes, then they are probably just not concerned about trying to fix something which will probably break more things when they do, Fix One thing Break Two more is a coders life.
< >
Showing 1-13 of 13 comments
Per page: 1530 50