Daily server resets are one of the only things that will have any significant effect

[Raiya]

Yeah I'd be lending my own voice to support the idea that they restart the data centers at 9am CET every morning for a week or 2. It would likely boot the long term afkers.

[Valkyrie_Lenneth]

Yeah I'd be lending my own voice to support the idea that they restart the data centers at 9am CET every morning for a week or 2. It would likely boot the long term afkers.

Nah, they'd have to randomize the time to a certain extent, or people would just log themselves back in immediately and go back to avoiding it.

[Catwho]

Nah, they'd have to randomize the time to a certain extent, or people would just log themselves back in immediately and go back to avoiding it.

What's happening is people are logging themselves in before they go to work, using their afk bot mod or crafting bot or whatever they have set up, and then coming home to a still logged in character.

Even if the reset was at a known time, as long as it was during the daytime hours, not everyone who is doing this will be capable of using remote desktop to log themselves back in.

[technole]

What's happening is people are logging themselves in before they go to work, using their afk bot mod or crafting bot or whatever they have set up, and then coming home to a still logged in character.

Even if the reset was at a known time, as long as it was during the daytime hours, not everyone who is doing this will be capable of using remote desktop to log themselves back in.

When you have raid groups meeting say at 7pm for just X amount of days of a week. Losing those time slots is depressing. So I side on anyone trying to actively 'prepare' for their show times.

[IdowhatIwant]

What's happening is people are logging themselves in before they go to work, using their afk bot mod or crafting bot or whatever they have set up, and then coming home to a still logged in character.

Even if the reset was at a known time, as long as it was during the daytime hours, not everyone who is doing this will be capable of using remote desktop to log themselves back in.

Most of these are keyboard / mouse macros.

[ForteNightshade]

They could announce it like an hour in advance, that ought to be enough time to prepare, and I don't think any cutscenes are that long.

Whether or not it would help any, I don't know. I do know there are a lot of people abusing automation to stay logged in.

Even an hour would be hollow when you're spent more than double than in a queue and will now have to compete with well over 10,000 people all trying to log in at once.

Not to mention, once Savage releases they'd have to avoid evening hours entirely for a forced shutdown. Otherwise, it'll completely destroy static schedules, which the dev team has readily acknowledged they want to avoid as they've said on several occasions they don't want to impede the World Race.

Please explain to me how server resets are going to help the 6k queues during prime time.

OH wait, they won't.

Exactly. Unlike Stormblood, not only are the population numbers significantly higher far more people are either working from home or can more readily remote into their PCs from work. They'll just jump back into the queue and go right back to AFK-ing with whatever macro or program they have that dodges the AFK timer.

[Chooty]

Even an hour would be hollow when you're spent more than double than in a queue and will now have to compete with well over 10,000 people all trying to log in at once.

The idea would be to get rid of AFKers before the queues start, so probably they would do the reset around noon. I don't think most people are suggesting they do a server reset at 6 pm, and that's not what they did in Stormblood.

[ForteNightshade]

The idea would be to get rid of AFKers before the queues start, so probably they would do the reset around noon. I don't think most people are suggesting they do a server reset at 6 pm, and that's not what they did in Stormblood.

Which won't necessarily solve the problem. While it isn't a bad idea to try, people have more immediate access to their PCs nowadays compared to Stormblood's release just by the sheer amount still working from home. Nevermind those who can remote into their PCs. They'd just get back in during their lunch break and setup their anti-AFK method of choice all over again—long before peak hours hit.

Nevertheless, that response was towards Valkyrie's suggestion of randomized server shut downs. In such a case, we could have a 6pm EST close which would destroy statics. There's absolutely no way SE would even consider it.

[Ayuhra]

My main takeaway from the OP was people are already BiS with the Extremes on farm. If I miss the window on learning parties for an entire expansion again... I'll... I'll...

Well I won't be doing Extremes again, I guess.

I feel like a kick to boot the bot AFKers is probably warranted, especially if they can somehow target player housing but I'm not sure how they can do that without kicking instance servers in general, I don't know their setup.

At the same time I sympathize with SOME of the botters. I can never support botting while at work or sleeping or spending a day out doing errands but I can almost understand doing it if you will be gone for 45 minutes, just long enough to get kicked by the timer but that kick will put you in a queue for waaay longer than you were gone for.

(Probably also worth mentioning that after the kick there will still be a massive queue as all live players mass log on again)

[Kes13a]

What's happening is people are logging themselves in before they go to work, using their afk bot mod or crafting bot or whatever they have set up, and then coming home to a still logged in character.

Even if the reset was at a known time, as long as it was during the daytime hours, not everyone who is doing this will be capable of using remote desktop to log themselves back in.

personally, at this point if someone is afk botting, or using some other work around and its provable.. since they arent playing the game anyway, a nice week long vacation from FFxiv should be in order...