XXX is too far away!

[Greatguardian]

He's not sticking up for SE... it's a common fallacy that coding is easy and quick, and anyone can do it better then the guys actually doing it.

There's a Dutch saying: "The best helmsmen are on shore." (De beste stuurlui staan aan wal.)

Those of us with training and experience in the field can tell the difference between "Okay, code isn't magic. They can't just change this at will" type code and "Why can't they just go in and change a 1 to a 0? This is stupid" type code. Both exist. They're not something we need to see SE's code to figure out.

[Kristal]

Those of us with training and experience in the field can tell the difference between "Okay, code isn't magic. They can't just change this at will" type code and "Why can't they just go in and change a 1 to a 0? This is stupid" type code. Both exist. They're not something we need to see SE's code to figure out.

I don't know what your 'training and experience' might be, but you just described the difference between messing with the inner workings of a complex interlocking piece of 10 year old code and adjusting the contents of a resource.
The slightest mistake, and you got a low level NM dealing 20k Magic Mortars or WAR30/WHM1 dealing 99999 dmg Cure I to undead.

It's not going to be the most difficult of exercises, but neither is it very easy, even for experienced developers. It's not like every developer knows every last line of code.. if they were even employed at the time the code was written.

[Greatguardian]

Everything seems magical and arcane when you have no idea how computers work.

Changing code is hard, bro.

[Khajit]

I thought we were being quiet about this because in all likelihood SE would fuck this up and have the adjustment affect monsters too then refuse to fix the new problem?
Kind of like how curelocking was "fixed" to be worse.

[Byrth]

They obviously already do a check that determines whether or not you are close enough to WS the monster. They could change the code to refuse to WS instead of giving an "out of range" message, or not remove TP upon "out of range" WSing.

Anyone remember how Blood Pacts used to work?

[Dreamin]

They obviously already do a check that determines whether or not you are close enough to WS the monster. They could change the code to refuse to WS instead of giving an "out of range" message, or not remove TP upon "out of range" WSing.

Anyone remember how Blood Pacts used to work?

BP is still broken in many sense today. If your avatar is killed before it actually perform BP, your BP is resetted. So you cannot resummon a new avatar and then immediate BP. This is true for both Rage and Ward right now. Easiest way to test this is in WoE.

[Bulrogg]

BP is still broken in many sense today. If your avatar is killed before it actually perform BP, your BP is resetted. So you cannot resummon a new avatar and then immediate BP. This is true for both Rage and Ward right now. Easiest way to test this is in WoE.

I haven't been on SMN in a while but unless they adjusted it, that also happens if the mob dies before your avatar gets to complete their BP, making you wait for recast. My apologies if this has been fixed. And I think I'd rather see this fixed before "XXX is to far away"; but still pulling for storage access before both of those. At any rate, I believe SE will get around to it once they finish with the other stuff that was planned before moving onto user submitted adjustments...but that's just my line of reasoning.

[Bulrogg]

SE said that'd look into it. Is losing your TP so bad that it should trump over other adjustments already planned out? Honestly, I'd rather see storage access from everywhere before they get around to this.

[Byrth]

If it gets amnesia'd (Pil) before the BP goes off, your timer is also not reset.

[Camiie]

Also if you use Assault while your avatar is taking its time drunkenly staggering to your position (a.k.a. pathing poorly), you lose that timer as well.

I think basic quality of life or job performance issues like TP or job timer loss have to take precedence over pretty much anything. To put it simply, they need to fix what's broken before they start making new additions.