4-linking an item is much harder now.

I noticed this after a few recent patches. This is not the case when the Ambush and Invasion league starts and last season. Last season they buff this already.

Did GGG lowered the rate of 4-linking an item? My friend also noticed it. They should investigate this.

I can confirm this. Especially jeweling for 4S seems to be hard these days.

A little while ago I was doing some testing and needed to 4l some boots. I got it in 6 jewelers and 1 fusing. I generally have bad luck too. I think you were just had bad luck. I'm pretty sure they'd mention if they reverted it back.

Obstervation Bias.

It really is easier, but RNG is RNG

I noticed also you'll get more chances to have 4 unlink repeated. it's like every time you apply fusings, you're chances of getting higher number of links is reset.

"

Moosifer wrote:

A little while ago I was doing some testing and needed to 4l some boots. I got it in 6 jewelers and 1 fusing. I generally have bad luck too. I think you were just had bad luck. I'm pretty sure they'd mention if they reverted it back.

If they reverted it they might not even know.... that is the funny thing about breaking a team up to do minor patches and revisions or when they shelve and rework on old projects. Sometimes old code sneaks back in from these shelved projects and undoes something that was modified after that project had been shelved.


edit- not saying it is what happened, just that old code can come back and haunt you over and over and over when you have multiple coders working on multiple projects.

Anyone remember when 4Ling took 10-30 fusings on average?

......count your blessings

"

Jiero wrote:

"

Moosifer wrote:

A little while ago I was doing some testing and needed to 4l some boots. I got it in 6 jewelers and 1 fusing. I generally have bad luck too. I think you were just had bad luck. I'm pretty sure they'd mention if they reverted it back.

If they reverted it they might not even know.... that is the funny thing about breaking a team up to do minor patches and revisions or when they shelve and rework on old projects. Sometimes old code sneaks back in from these shelved projects and undoes something that was modified after that project had been shelved.


edit- not saying it is what happened, just that old code can come back and haunt you over and over and over when you have multiple coders working on multiple projects.

Good coding practises mean this should not be possible.

Any changes made to code should be logged and recorded, what changed and why. This is fairly basic shit when you look at large coding projects with more than one person. Or even small web development work where you might not have looked at a part of code for a while, so you can easily revert said changes if they break.

"

Real_Wolf wrote:

"

Jiero wrote:

"

Moosifer wrote:

A little while ago I was doing some testing and needed to 4l some boots. I got it in 6 jewelers and 1 fusing. I generally have bad luck too. I think you were just had bad luck. I'm pretty sure they'd mention if they reverted it back.

If they reverted it they might not even know.... that is the funny thing about breaking a team up to do minor patches and revisions or when they shelve and rework on old projects. Sometimes old code sneaks back in from these shelved projects and undoes something that was modified after that project had been shelved.


edit- not saying it is what happened, just that old code can come back and haunt you over and over and over when you have multiple coders working on multiple projects.

Good coding practises mean this should not be possible.

Any changes made to code should be logged and recorded, what changed and why. This is fairly basic shit when you look at large coding projects with more than one person. Or even small web development work where you might not have looked at a part of code for a while, so you can easily revert said changes if they break.

Should be impossible yes, and in a 8 hour fixed day with no over time and working on just a few projects that you yourself created and documented extensively upon then maybe.... in theory its not just possible, its GOING to happen a few times. At this point of a project's life its pretty much impossible to not have had it happen and need repaired again at least once if not several times, and probably with more times it happened but have yet to be discovered.



Add some heavy crunch time, prolonged lack of sleep, juggling dozens of separate projects at once, undocumented/misdocumented/underdocumented code that another person overworked on and serious time constraints and other issues..... in the end your just praying it works and actually compiles...



crap happens and we're just human...

"

Real_Wolf wrote:

Obstervation Bias.
It really is easier, but RNG is RNG

Going with this theory too.