It's quite the shock how readily people won't believe the word of the people that work on the game, but will believe the word of a few players.

Assuming that the players are right in that the flourish is acting wonky, it's probably a side effect of whatever tweaking OOO did to the engine, or how the client/server relation works. Though that would beg the question of why it isn't effecting everything. So I'd assume nothing is wrong and people are just inherently suspicious of OOO when they say that nothing was changed, and are seeing what they want to. After all, why didn't Chris post this immediately if it was so obvious?

This is kinda sad, tbh. It's the whole shield hissy fit all over again. Or Basil binding. Seems the most effective way to troll these forums now is to make up a stupid rumor.

I would like to believe that if the range of the flourish changed, then it might be because the net code possibly improved. I like to think that the range of weapons is artificially increased by the net code predicting where we're going to be, but then we swing our weapon and oops! We've got more range than we should have! There are already errors in the prediction because sometimes I'm standing in one block, but the server thinks I'm as much as 1.5 blocks away from my true (client-side) position! This is with internet that's pretty good, no less! (Granted that Alaska does have some of the lower-end broadband in the country, even if we easily have the money to instantly have the best. x.x)

Personally, I believe the devs. If my Flourish acts up and doesn't connect as it should on the 3rd strike again I will just file a bug report.

~Gwen

Suck up? Oh no you didn't.

The only reason I'm bothering to defend them this time around is because people are contesting the very mechanics of the game. Who the hell can give the final word on such a thing? Some random nobody, or the very damn guys that designed it? It's like taking a car to a mechanic, and then disregarding everything he says in favor of whatever verdict is of your friend that works in accounting and has never worked on a car in his life. It makes no goddamn sense.

Now, as I stated on Chris' thread and here, it is possible that some of the back end stuff is indirectly interfering with how the blades work. However, it also wouldn't make sense that such a thing would effect only *one* specific type of weapon, and not all of them. Maybe they are effecting every weapon and people just aren't noticing them as much. I don't bloody well know. I don't work at OOO so I can't pin this crap down. At any rate, I lean more to the "mass hysteria" side of things rather than "players got a point," especially given that some of them have recently believed that shields were nerfed and flipped out over Basil recipies being bound. Call me jaded, I don't care.

The final note to take away is that OOO didn't withhold anything they knew about, nor did any *DIRECT* changes to rapiers. -_-

Thanks Nick for clarifying this. So much for self-entitled "experienced" players claims.

"At any rate, I lean more to the "mass hysteria" side of things rather than "players got a point," especially given that some of them have recently believed that shields were nerfed and flipped out over Basil Recipes being bound."

Seeing Posts from my Thread, I said it MIGHT have gotten Nerfed. I never did FSC but some people did. I would Trust what they said.

The other Thread about Recipes being Bound was about that Person's Friend probably Trolling them or not knowing any better.

EDIT:I've always been meaning to Ask you a Question, too...

I agree with the mass hysteria too. It might be the excitement of waiting for weapon changes or the mission system to come out, but people seem to be jumping on the first rumor like there's no tomorrow, instead of waiting for a confirmation or confirming it themselves. I'm surprised people are even getting preemptively upset about the sun shards on the test server -- it's a place to test things, for crying out loud.

At the end of it all, OOO has their own story to tell, and if some player suggestions/preferences don't mesh with their vision, then they won't implement them. Ex: with the sun shards, they were originally intended for fiend sniping but happened to work better for constructs in practice, and maybe OOO wants to change it so that it works better for its original purpose, and balance another bomb for constructs. Or not. It's still their game, and if we were playing a console game and found that a weapon worked better for something else than its original purpose, we adapt and enjoy it and move on. Not everyone will like the change, but then if OOO did everything that everyone liked, we wouldn't have a game at all, we would have a Jackson Pollack painting. And I would rather have a game that someone made in their own vision, that I can explore and adapt in.

The guy who runs the game, or the guy who tries to game it? I'm going to go with the former.

It's all in your head Chris, you probably stuck to many accessories on it or something.

I tested my DTB in the training hall, and I can't reproduce any range reduction in the second or third hit. For example, I can still hit the switch behind the gate by using the second or third hit over the low wall, which is just out of range of the first swing. I also tested it in the conveniently placed wolver dens on the vana gate, and again noticed no change in range or accuracy.

I should note that the piercing swords have always had issues with connecting the second or third hits (never both, for obvious reasons) against mobile targets, due to their knockback and high speed. If anyone is observing this particular phenomenon now, what you are seeing is not new, and was definitely not introduced in any recent patch.

I'm going to chalk this one up to confirmation bias. If Nick says the swords haven't changed, then the swords haven't changed. The patch was most likely just tweaking the appearance of the love aura in preparation for the release on valentine's day. (since the love aura was not released in its previous overbearing form, changing it doesn't count as a user-facing change)