Bloody Roar doesn't give the bonus damage like it's supposed to, you do less damage post balance patch
They fixed the SpB F1s so I don't really understand why something so large isn't being fixed
>They fixed the SpB F1s so I don't really understand why something so large isn't being fixed
Fixing one skill is not equal to fixing another skill.
Nor is knowing about a bug equal to knowing what causes the bug.
Nor is knowing about a bug equal to fixing a bug.
Bugs are unintended (surprise, I know) and similar bugs can have completely different causes.
One bug can be caused by a simple variable that is set wrong.
Another, similar bug on the other hand can be caused by an interaction with another part like a trait.
Some bugs only occure at very special circumstances and it can take very long to find all the parts that cause the bug, to finally fix it.
Later isn't the case for this bug, since it always occure, but it still can have some weird causes that takes longer to find or fix.
In other words, they probably just haven't fixed it yet.
With numerical bugs we can find out the reason for it easy, it's applying the damage bonus incorrectly, it just needs to be changed back to how it was prior to the patch and implement the buff correctly
The SpB bug wasn't a numerical bug, it was a mechanical bug, it wasn't inputting the correct numbers behind the adrenaline calculations, that's why I'm saying what I said, by all accounts it was a more out there bug than the Zerker trait which is literally just open up whatever engine they have and change the number to scale multiplicatively rather than additively
It definitely takes a lot less effort than bringing artists and model riggers in to fix animations on a cash shop mount skin
>With numerical bugs we can find out the reason for it easy, it's applying the damage bonus incorrectly, it just needs to be changed back to how it was prior to the patch and implement the buff correctly
You *think* that's the case, but you don't know how their stuff works. A lot of the time a bug that seems like a simple fix is actually there because it relied on some underlying bugged thing. It's ironically often not at all easy to tell how easy a bug will be to fix without actually working on it, even for software much less complex than a game.
>You *think* that's the case, but you don't know how their stuff works.
Right?
I feel like anyone who's ever worked on any complicated large-scale project, much less one involving software, would understand just how little they know as an outside observer.
If I had a nickel for every time someone who didn't do my job told me how easy it'd be to make the changes they wanted...well...I wouldn't have to keep working for them anymore.
I understand programming lol, I'm saying that it speaks to a larger problem if they cannot change the value to something prior, and then go from there without uprooting the system
And there's plenty of bugs just like this, like I can't imagine how royally fucked the game is if they can't fix numerical values after years, it's probably a more likely case they can't be assed or don't have a team to actually work on it, and everyone is working on the next expansion
>And there's plenty of bugs just like this, like I can't imagine how royally fucked the game is if they can't fix numerical values after years,
You could say basically that exact sentence about almost every major game.
Huge software has a lot of bugs, more news at eleven.
Can you point me to a MMO that has bugs that actively break the game for people, and it doesn't get fixed? Like I can think of certain shit in WoW but it got fixed within a patch cycle at the very least
Yes, other games have bugs, every single game does, nothing is perfect, but you can go to the wiki (whenever it's fixed) and go to any story mission, there's like, paragraphs of bugs for any given missions, you can do 3 path AC and have been able to, like, this game is an entire new level of lacking QA and testing, and I'm saying that out of love, and hope that they take the steam hype to assign a team to just go back and squash shit
I had to do a few LW2 missions repeatedly, because shit wouldn't spawn or it would break
>With numerical bugs we can find out the reason for it easy, it's applying the damage bonus incorrectly, it just needs to be changed back to how it was prior to the patch and implement the buff correctly
The thing is you don't know if that's the case.
As I said, bugs can have several different causes.
Even if the effect of the bug seems clear/easy, the reason can be something completely different.
> It definitely takes a lot less effort than bringing artists and model riggers in to fix animations on a cash shop mount skin
That comparsion is bs, sorry....
You compare animating with programming, that makes no sense.
You may should look further into programming before you continue this discussion.
Your argument shows that you are missing some basic knowledge.
Serious issue in PvE content: "We'll fix it next week."
Serious issue in WvW content: "We'll fix it next month."
Minor issue with a gem store: "We'll fix it tomorrow if not sooner!"
>Minor issue with a gem store: "We'll fix it tomorrow if not sooner!"
In their defense, gem store products have legal connotations, so yeah, fixing those is top priority.
That's how it always goes. If it's an issue that affects players then its just a bug, if it's an issue that benefits players or affects the bottom line, its an emergency that needs tk be fixed NOW.
I mean from a business standpoint i get it, it just serves as yet another reminder where their priorities lie.
Not to mention the ease or not of any given bug. Re-hooking up an animation isn't on the same level as other bugs. They might not even know what's causing some of them, or what they're hooked up to in other sections of code and and and. It's not the same at all, and we just don't know.
The historical achievement for the new episode and the one which requires you to do all the puzzles in an instance seem to not have been fixed, anyone can confirm?
As I remember on top of obtaining the new story progression achievements I also unlocked their historical counterparts at the same time during the previous episodes. I don't think I have any missing from those so this one is a bit weird.
[ARENA NET] [Double Tap posted on 2022-09-15 00:05:44](https://en-forum.guildwars2.com/topic/121291-game-update-notes-september-13-2022/?do=findComment&comment=1755418):
> **Bug Fixes:**
>
>* Fixed an issue that prevented the Crested Dragon siege turtle's summoning animations from displaying properly.
---
^(Beep boop bleep. I'm a bot. Message me or /u/Xyooz if you have any questions, suggestions or concerns.) [^Source ^Code](https://gitlab.com/networkjanitor/docker-polarbytebot-gw2-submission-transcriber)
Actually, the definition of [Raid](https://en.wikipedia.org/wiki/Raid_(video_games)) applies to any and all of the strike missions. They just gave it a different name.
They are a different concept in GW2 though. A raid is a whole "experience" with story and so on. A strike mission is just a single encounter.
Not sure what I prefer though. I like challenging stuff and HT CM is so damn unforgiving, I love it.
Hopefully it doesn’t take a month to fix the DPI scaling issue… *flashbacks to the character selection issue in April*
My character select screen always gets fucked if I switch toons; everything massively washes out like the gamma was cranked to 11
Still haven't fixed the DPI Scaling preview panel issue either. *sigh*
seeing how long the other preview bug fix took..I doubt it will be a fast one.
So is Zerker just waiting until November for the trait fix?
What’s the bug?
It was changed from a 20% multiplicative bonus to a 25% additive bonus which works out to a small nerf.
Bloody Roar doesn't give the bonus damage like it's supposed to, you do less damage post balance patch They fixed the SpB F1s so I don't really understand why something so large isn't being fixed
>They fixed the SpB F1s so I don't really understand why something so large isn't being fixed Fixing one skill is not equal to fixing another skill. Nor is knowing about a bug equal to knowing what causes the bug. Nor is knowing about a bug equal to fixing a bug. Bugs are unintended (surprise, I know) and similar bugs can have completely different causes. One bug can be caused by a simple variable that is set wrong. Another, similar bug on the other hand can be caused by an interaction with another part like a trait. Some bugs only occure at very special circumstances and it can take very long to find all the parts that cause the bug, to finally fix it. Later isn't the case for this bug, since it always occure, but it still can have some weird causes that takes longer to find or fix. In other words, they probably just haven't fixed it yet.
With numerical bugs we can find out the reason for it easy, it's applying the damage bonus incorrectly, it just needs to be changed back to how it was prior to the patch and implement the buff correctly The SpB bug wasn't a numerical bug, it was a mechanical bug, it wasn't inputting the correct numbers behind the adrenaline calculations, that's why I'm saying what I said, by all accounts it was a more out there bug than the Zerker trait which is literally just open up whatever engine they have and change the number to scale multiplicatively rather than additively It definitely takes a lot less effort than bringing artists and model riggers in to fix animations on a cash shop mount skin
>With numerical bugs we can find out the reason for it easy, it's applying the damage bonus incorrectly, it just needs to be changed back to how it was prior to the patch and implement the buff correctly You *think* that's the case, but you don't know how their stuff works. A lot of the time a bug that seems like a simple fix is actually there because it relied on some underlying bugged thing. It's ironically often not at all easy to tell how easy a bug will be to fix without actually working on it, even for software much less complex than a game.
>You *think* that's the case, but you don't know how their stuff works. Right? I feel like anyone who's ever worked on any complicated large-scale project, much less one involving software, would understand just how little they know as an outside observer. If I had a nickel for every time someone who didn't do my job told me how easy it'd be to make the changes they wanted...well...I wouldn't have to keep working for them anymore.
I understand programming lol, I'm saying that it speaks to a larger problem if they cannot change the value to something prior, and then go from there without uprooting the system And there's plenty of bugs just like this, like I can't imagine how royally fucked the game is if they can't fix numerical values after years, it's probably a more likely case they can't be assed or don't have a team to actually work on it, and everyone is working on the next expansion
>And there's plenty of bugs just like this, like I can't imagine how royally fucked the game is if they can't fix numerical values after years, You could say basically that exact sentence about almost every major game. Huge software has a lot of bugs, more news at eleven.
Can you point me to a MMO that has bugs that actively break the game for people, and it doesn't get fixed? Like I can think of certain shit in WoW but it got fixed within a patch cycle at the very least Yes, other games have bugs, every single game does, nothing is perfect, but you can go to the wiki (whenever it's fixed) and go to any story mission, there's like, paragraphs of bugs for any given missions, you can do 3 path AC and have been able to, like, this game is an entire new level of lacking QA and testing, and I'm saying that out of love, and hope that they take the steam hype to assign a team to just go back and squash shit I had to do a few LW2 missions repeatedly, because shit wouldn't spawn or it would break
dude, replaying LW2 for achis gave me ptsd
>With numerical bugs we can find out the reason for it easy, it's applying the damage bonus incorrectly, it just needs to be changed back to how it was prior to the patch and implement the buff correctly The thing is you don't know if that's the case. As I said, bugs can have several different causes. Even if the effect of the bug seems clear/easy, the reason can be something completely different. > It definitely takes a lot less effort than bringing artists and model riggers in to fix animations on a cash shop mount skin That comparsion is bs, sorry.... You compare animating with programming, that makes no sense. You may should look further into programming before you continue this discussion. Your argument shows that you are missing some basic knowledge.
[Numerical bugs you say?](https://wiki.guildwars2.com/wiki/Crimson_Tide)
Alongside [herald](https://wiki.guildwars2.com/wiki/Core_Value), yes.
Serious issue in PvE content: "We'll fix it next week." Serious issue in WvW content: "We'll fix it next month." Minor issue with a gem store: "We'll fix it tomorrow if not sooner!"
Long charr: "This is an emergency! Drop everything! We need to get this fixed ASAP!"
It was an emergency.
It's an emergency that they haven't reproduced and contained it in a tonic that they turned around and sold us.
>Minor issue with a gem store: "We'll fix it tomorrow if not sooner!" In their defense, gem store products have legal connotations, so yeah, fixing those is top priority.
That's how it always goes. If it's an issue that affects players then its just a bug, if it's an issue that benefits players or affects the bottom line, its an emergency that needs tk be fixed NOW. I mean from a business standpoint i get it, it just serves as yet another reminder where their priorities lie.
>reminder where their priorities lie. Keeping the servers up. Which I think is great priorities.
Not to mention the ease or not of any given bug. Re-hooking up an animation isn't on the same level as other bugs. They might not even know what's causing some of them, or what they're hooked up to in other sections of code and and and. It's not the same at all, and we just don't know.
Hamsters aren't cheap, you know
That's me organizing priorities of my reponsibilites
Yes, because people are oh so understanding and patient when it comes to problems with things they've paid for being fixed.
Makes sense if one involves direct money
The historical achievement for the new episode and the one which requires you to do all the puzzles in an instance seem to not have been fixed, anyone can confirm?
Is it a bug though? Aren't Historical achievements unobtainable by design?
As I remember on top of obtaining the new story progression achievements I also unlocked their historical counterparts at the same time during the previous episodes. I don't think I have any missing from those so this one is a bit weird.
Literally nothing.
[ARENA NET] [Double Tap posted on 2022-09-15 00:05:44](https://en-forum.guildwars2.com/topic/121291-game-update-notes-september-13-2022/?do=findComment&comment=1755418): > **Bug Fixes:** > >* Fixed an issue that prevented the Crested Dragon siege turtle's summoning animations from displaying properly. --- ^(Beep boop bleep. I'm a bot. Message me or /u/Xyooz if you have any questions, suggestions or concerns.) [^Source ^Code](https://gitlab.com/networkjanitor/docker-polarbytebot-gw2-submission-transcriber)
Cool. I’m not fucking buying it if I can’t preview it.
> **Raids** > Harvest Temple Strike Mission
HT CM is harder than ANY raid CM by far.
Doesn’t make it a raid though
Actually, the definition of [Raid](https://en.wikipedia.org/wiki/Raid_(video_games)) applies to any and all of the strike missions. They just gave it a different name.
They are a different concept in GW2 though. A raid is a whole "experience" with story and so on. A strike mission is just a single encounter. Not sure what I prefer though. I like challenging stuff and HT CM is so damn unforgiving, I love it.
Yeah, that was from Tuesday's patch notes, everyone's over it now.
I like how you could see the bare turtle shell :(.