I was wondering if we could get some context on the change to the GroupMovement flag being disabled in the confluence. This is a nice feature to have in the confluence when leading a group, especially due to the variable roundtimes one can encounter there.

In my experience, when GroupMovement was turned on, I would occasionally get hit with RT when trying to move when my group was not out of RT yet. I think this was the game simulating the RT associated with movement in this area, even if it didn't actually happen. It was pretty easy to spot that I needed to wait, and then one can simply move again.

With the flag disabled, it is back to guessing the RT of others of course.

Could the folks who do not like this flag, just turn off their own GroupMovement flag, rather than disable it for the entire game? Or maybe another solution so we can take advantage of this great flag in this area? I admit I have no idea on the behind-the-scenes coding mechanics here.

You struggle against the shifting, rubble-strewn terrain...
Roundtime: 4 sec.
[The GroupMovement flag is disabled for this area.]
[Elemental Confluence]
The air is thick with soot and ash and the sky is nearly as black as a starless night, only periodically broken up by flashes of crimson fire streaking above. Rocks can be heard colliding and breaking apart in the distance and tremors rumble faintly underfoot.
Obvious paths: north, south, southwest