Movement Speed Bug

[Gumbercubes]

I did not catch this bug, a guildie did (Solaar) but I felt like the community (and hopefully Devs) should be made aware of it.

You will notice that every time you change specs you will toggle from fast mode to sluggish mode.

The Speed-o-Meter addon clocks me at 6.5 in fast mode and 5.4 in slow mode (I don't know the units). This is a pretty large (20%) difference in run speed and could leave you scratching your head as to why everyone else could run out of the fire and you couldn't.

To avoid being a slowbie, get the Speed-o-Meter and change specs until you know what your top speed is (will vary based on buffs, PA, conquest power, etc). Then whenever you change specs you will have to change twice (once to toggle slow mode on and once to toggle fast mode on).

We have seen this bug on every class, not sure if it affects different specs differently (ie those with runspeed bonuses).

[xanduin246]

Just to confirm, my Speed-o-Meter picks up the same difference Gumber finds.

And I checked whether or not it was a speed buff issue by this method:

Start in Spec 1: 6.5
Spec 2: 5.4
Spec 3: 6.5
Spec 1: 5.4
Spec 2: 6.5
Spec 3: 5.4

So all 3 specs got both speeds depending on the order.

[Shoggoth1890]

This bug has been around since the double dipping bug. It was fixed on the PTS just like double dipping, but not sure why it didn't get pushed out.

[Nestran]

Nice find. I noticed I was slow sometimes and would log out to fix it. Never made the connection to changing specs.

[Daglar]

The fix for this is pretty involved - its done, but we didn't want to push it up before 2.2 due to how many little things it touches.

~Daglar

[Chantillary]

Something to check is whether your different specs have speed boosts to them as part of the soul tree. Like the Harbinger tree has Natural Swiftness which increases your movement speed by 4%/8%.

If different specs are to provide relevant data, then things like speed boosts should be removed -- PA boosts to speed aren't necessary to bring into the discussion, as the speed boosts from that are the same across all your roles.

Also, if your role changing is changing out equipment, check to see if the equipment has any sort of speed boost on it.

[Woftam]

The fix for this is pretty involved - its done, but we didn't want to push it up before 2.2 due to how many little things it touches.

~Daglar

Am I reading this correctly?
You have fixed a bug.
You know the fix will have impact on "many little things".
But you would prefer to impliment the fix along with a patch (which contains multiple changes).

Damn, that makes so little sense. Do you NOT want to examine the impact of the fix or do you want to hide it's flaws under a multitude of other changes in the hope that no one will notice?

Had you a reputation for applying fixes that didn't break existing features of the game I wouldn't even contemplate a post like this.

Bat sadly, Trion, such a reputation if it ever existed is now just an historical curiosity.

[Talila]

Am I reading this correctly?
You have fixed a bug.
You know the fix will have impact on "many little things".
But you would prefer to impliment the fix along with a patch (which contains multiple changes).

Damn, that makes so little sense. Do you NOT want to examine the impact of the fix or do you want to hide it's flaws under a multitude of other changes in the hope that no one will notice?

Had you a reputation for applying fixes that didn't break existing features of the game I wouldn't even contemplate a post like this.

Bat sadly, Trion, such a reputation if it ever existed is now just an historical curiosity.

Something always breaks when at patch is deployed, it's not just local to Rift, it can happen and usually does happen in -any- game. Just be happy the Rift-team is pretty quick with their hotfixes, and even willing to put in a hotfix several times over the course of a week if that is what is needed to stop something from spontaneously breaking.

[Woftam]

Something always breaks when at patch is deployed, it's not just local to Rift, it can happen and usually does happen in -any- game. Just be happy the Rift-team is pretty quick with their hotfixes, and even willing to put in a hotfix several times over the course of a week if that is what is needed to stop something from spontaneously breaking.

You are probably correct, about all games being subject to patch breakage. From what I've read in forums here it appears to be the justification.

My experience prior to Rift was WoW.
It became common practice to avoid doing anything vital in game for a week following a patch.
BUT it was only a week. Within a week all bugs were usually ironed out. I remember on one occasion Blizzard crediting its players with a week of sub to compensate for a breakage that lasted over a week.

Rift still contains breakage caused by patch 1.11 and additional bugs installed by attempted fixes of that breakage. Some of the 1.11 installed bugs have actually been denied by Trion.

An interesting example of Trion's band aid fix procedure is the Quest "I Hope You Like Surprises". This quest was originally broken by a seasonal event that dumped an Elite on top of the quest objective. A hot fix removed the Elite. A subsequent patch reinstalled the Elite. The final solution was to move the quest objective.

Rift is currently wrapped in so many band aids it has become reminiscent of something you'd expect to find in an Egyptian Sarcophagus.

Over a year ago my move to Rift from WoW was like going from a Ford to a Porche.
Trion announce Storm Legion such that I expected my new ride to be a Ferarri.
Now I find myself in a Volkswagon, with a broken transmition.

[Fearnada]

I believe that this bug also appears in WF's when you are snared. The snare seems to take away all of your speed buffs completely.

[Daglar]

Am I reading this correctly?
You have fixed a bug.
You know the fix will have impact on "many little things".
But you would prefer to impliment the fix along with a patch (which contains multiple changes).

You are reading it correctly, but misinterpreting my words.

The fix touches many aspects of the code, some aspects of which are not fully compatible with the version of the game that is on live servers today. When I asked the engineer how risky trying to integrate the change into the current live version of the game he said he wasn't comfortable trying to do so, as this was actually a series of many different fixes.

2.2 isn't that far off. I'm not going to tell an engineer to push out a fix for this issue that they feel is risky with the current version of the game.

~Daglar

[Methadras]

The fix for this is pretty involved - its done, but we didn't want to push it up before 2.2 due to how many little things it touches.

~Daglar

Yeah, i don't like it when bugs touch me. Keep your cooties away from me please. Thank you.

[hardy83]

Am I reading this correctly?
You have fixed a bug.
You know the fix will have impact on "many little things".
But you would prefer to impliment the fix along with a patch (which contains multiple changes).

Damn, that makes so little sense. Do you NOT want to examine the impact of the fix or do you want to hide it's flaws under a multitude of other changes in the hope that no one will notice?

Had you a reputation for applying fixes that didn't break existing features of the game I wouldn't even contemplate a post like this.

Bat sadly, Trion, such a reputation if it ever existed is now just an historical curiosity.

Uh no. He basically said they have a fix now, but want to test it before releasing it because it's a complicated fix and thing can break, thus plan to release it in 2.2 after testing.

I don't know why you think that's a bad thing. Would you rather them release it now and potentially break a bunch of stuff so you can complain about how they released a fix without testing it? lol

[Woftam]

You are reading it correctly, but misinterpreting my words.

Really? The following clarification, had it initially been given, would imply misinterpretation on my part.

The fix touches many aspects of the code, some aspects of which are not fully compatible with the version of the game that is on live servers today. When I asked the engineer how risky trying to integrate the change into the current live version of the game he said he wasn't comfortable trying to do so, as this was actually a series of many different fixes.

I applaud the engineers stand on this, and appreciate that you'd be guided by his area of expertise.
I wonder how much of this sentiment was considered while applying recent changes.

Perhaps a realization, on the part of your engineers, that current coding is incompatible with existing game code is the reason why so many required fixes have not been addressed.

2.2 isn't that far off. I'm not going to tell an engineer to push out a fix for this issue that they feel is risky with the current version of the game.

~Daglar

Well good luck with the new content, which I understand is in demand by a majority of your player base.
Personally, I'd prefer to see existing content stabilized before adding anything new.
An opinion Trion obviously feels is of the minority.

[Woftam]

Uh no. He basically said they have a fix now, but want to test it before releasing it because it's a complicated fix and thing can break, thus plan to release it in 2.2 after testing.

I don't know why you think that's a bad thing. Would you rather them release it now and potentially break a bunch of stuff so you can complain about how they released a fix without testing it? lol

Totally the opposite.

What I'd really like to see is some fixes or changes that HAVE been thoroughly tested before release so there would be no reason to complain about a "bunch of stuff" that broke.

Currently, and for the last three months or so, the Live version of the game plays like an untested beta.

lol