I just checked it in-game. I can only choose FSR 3.1 (+FG) or 1, not 4 (or 2, interestingly) which looked crap on my system anyway). Running Kubuntu Linux 24.04 on a Radeon RX 7600.
Any word on when the next hotfix is supposed to land?
4 Likes
Thatâs great! Youâre right, youâve been using three patch fixes to keep adding bugs to Arbites, and after introducing the bleeding dog in 1.8.3, you rushed to fix it within two days by releasing 1.8.4. You didnât even test it properly internally, resulting in almost all of Arbitesâ core talents having bugs where they donât work properly.
Then this critical bug has been around for a week, and you still havenât released a patch to fix it. (I guess you never wanted players to be too strong, but you donât care if theyâre too weak.) If you really canât fix it or just want to enjoy your vacation, roll back the code to 1.8.2 or 1.8.3. Honestly, the bugs werenât as severe as they are now.
3 Likes
You can look at the code for the latest patch on GitHub. Pretty sure it didnât cause the other issues with Arbites, but I could be wrong.
1 Like
What was this âpatchâ today?
Just tested and âMalocatorâ (50% cooldown regen after marked is killed) is still broken under Execution Order?
1 Like
Yea. This is not a good place to leave the new character you just released. People are noticeably shelving Arbites until itâs fixed. And new players buying a bugged character like this are going to get a terrible impression right out the box.
5 Likes
Bleeds stacks were being applied to any enemy in the trajectory of attack rather than the specific enemy being attacked, as well as how Puncture blessings on Bolt Weapons were exploiting a bleed âbugâ
1 Like
Despite what Fatshark is saying this is and was not a bug, since the release of those said blessing they worked that way for every ââclassââ. Them saying and removing it is., if i have to asume cause of negative feedback. (lets be honest, fatshark is dishonest about this cause they said in livestreams they wanted to expand on this)
I can equip it now on my zealot, trow a knife and it applies those blessings to the knife. Same for the other classes (except arb now).
1 Like
Fatshark is inconsistent. They removed the revolverâs Handcannon blessing (+rending on crit) interaction with blitzes.
I always found it strange when blessings worked on other attacks than those of the blessed weapon. It seems illogical for me, because that weapon was blessed, not any other one I happen to have in my hand when the blessed oneâs effect happens.
It may be an unpopular opinion, but I prefer game world consistency over metagame power. 
That, and if the devs of a software declare somehing a bug, it is a bug, because only they define the intended outcome of their own code.
1 Like
It is quite normal in games to have these interactions.
If they dont want it they should remove it for all classes not just one.
Itâs always rough laying bug-or-not especially with Fatshark games, because thereâs no real way to tell if it is a bug or bad design, with the two cases I remember being Counter-fire (initially said to be not-a-bug, but eventually designated as a bug and fixed) and the close range distance (undocumented change that made it the same as melee range, but not communicated anywhere, eventually reviewed and changed again).
2 Likes
How would you distinguish bugs from bad design? (just curious)
To me, a bug is an unintended outcome of code and thus, ultimately at the discretion of the coder who defines the intended outcome in the first place. In contrast, bad design is often defined (at first) by others than the designer who may or may not agree.
Both definitions can change over time as developers review their own code and design, so itâs not suprising to me when something is later reframed like in your examples. But it doesnât change my view that the devs are the ultimate instance for the definition, even if they may change it over time.
That said, my post was mostly a reaction to the statement âdespite what Fatshark is saying this is and was not a bugâ, which I disagree on fundamentally.
2 Likes
It is quite normal in games to have these interactions.
We may know different games, but I see effects limited to the items that have them much more often than not. E.g. in an RPG, if I shoot an arrow and then draw my flame sword, I canât remember any game where my arrow would ignite mid-flight. So, I canât confirm that such entanglements are normal in games. Do you have any examples?
If they dont want it they should remove it for all classes not just one.
While I agree in principle (seeing such effects not as normal after all), Iâd also leave it to the discretion of the developers who know much more about their vision of their game than any of us.
2 Likes
Normally i would agree, but consitensy isnt a strong suit of the developer
Pretty much it comes from inconsistencies (logical or otherwise) and how Fatshark responds to it.
For the Counter-fire example, only a single type of ranged enemy (scab stalkers, the sleeveless scab ranged mob that changes to a melee weapon) wasnât highlighted by Executionerâs Stance, when the tooltip specifically uses the term ranged enemies. Reapers are technically a ranged enemy but them not being highlighted by Counter-fire is neither bug nor bad design since there is a node specifically for highlighting ogryns.
When Counter-fire was initially ruled as not-a-bug, there was a thread raised to request that Fatshark either change the design, as having that lone exception didnât make sense, or have the tooltip changed to more accurately reflect the node. Then someone else reported it as a bug, it was acknowledged and eventually fixed.
It really does depend on the specific system or interaction, some are a lot easier or obvious to pick out as a bug or bad design, some are way too subjective to call one way or another.
But in the case of blessings affecting things other than the weapons they are on, I believe itâs a bug or design oversight since Fatshark have historically taken action to stop blessings affecting things outside of the weapons they are on, like the Handcannon interaction with Assail and Brain Burst.
As to why the Puncture interaction has stayed for so long, I think that Fatshark simply didnât know about it until people reported it in relation to the dog shenannigans and only now is there really any mention that it also affects other blitzes too. Unfortunately, Fatshark historically and currently still has some fundamental structural QA issues.
2 Likes
Thanks for the elaborate explanation. I actually agree completely. (And the many wrong or vague descriptions in DT are why I see the mod âEnhanced Descriptionsâ as absolutely mandatory. 
)
fat shark is also totally inconsistent on it. like they removed scattershot for affecting overall crit chance, but left brutal momentum for both types of melee attacks in for almost 2 years. then they added hot shot which is brutal momentum for all melee weapons (with a hellbore tax) but I guess fine because they havenât fixed that or the broken math that makes T1 80% hitmass reduction on weakspot hit at all times instead of 20% (T4 is 50%). the more likely explanation is that the unintended stuff that is good gets fixed and the unintended stuff that is benign and mostly funny is left alone (hopefully). theyâre just slow at it.
3 Likes
What are the chances for some updates to the store rotation? 
1 Like
remember when Fury of the Faithful was found to work on ranged weapons (obvious bug) but they called it a feature and left it for years and then took it out later without ever admitting it was a bug
3 Likes