Please make it so you aren't kicked for inactivity in a solo dungeon

[kongajinken]

Kind of silly that I was kicked for inactivity when I was literally the only one in the dungeon, especially since it took me 45 minutes to get that far in.

[Stepjam]

They aren't likely to change it because it's another way to keep cycling instances out. They don't want people AFKing in random instances because that means more work for the servers.

[Rongway]

They aren't likely to change it because it's another way to keep cycling instances out. They don't want people AFKing in random instances because that means more work for the servers.

Instance timers make this a non-issue. They're not going to change it because they won't want to add an extra conditional that they might get wrong and break duty idle kicks altogether.

[Jojoya]

It's got nothing to do with you inconveniencing other members of a party. The party can always kick you if your AFK is an issue.

It's because you're taking up space on the instance servers that could prevent new instances from being formed for players who aren't AFK and trying to get their own duties completed.

Remove the timer and many players who don't want to log out when they AFK would move into a dungeon, making it harder for others who actually want to do a duty.

It's better to try to plan ahead and take care of anything that might interrupt you while in the duty before the duty starts, or postpone doing the duty if necessary. I've been AFK kicked myself a few times because I had to step away longer than expected. I just restart the duty when I'm able to return. There have been other occasions a delivery or phone call was due so I put off doing the duty until after they were done. It's not a big deal.

Instance timers make this a non-issue. They're not going to change it because they won't want to add an extra conditional that they might get wrong and break duty idle kicks altogether.

They're not going to change because they don't want players who are AFK preventing other players from starting their duties. Space on the instance servers is not infinite.

[Iscah]

Would the game be reserving the player's spot in the overworld population on top of their location in the instance? They need to be able to move back into the overworld when they're done, so it would get tricky if the world is full because more people were let in while they're in the instance.

So, assuming that's the case, that makes it even less likely that they'd let you idle in an instance because you're taking up space in two places at once.

[Rongway]

It's got nothing to do with you inconveniencing other members of a party. The party can always kick you if your AFK is an issue.

They can't "always". Initiating a vote kick puts you on cooldown for four hours. The 10 minute duty idle kick boots you so the party doesn't have to wait for you, nobody has to put their kick on cooldown, and you'll still get kicked even if everyone's vote kick is on cooldown.

Remove the timer and many players who don't want to log out when they AFK would move into a dungeon, making it harder for others who actually want to do a duty.

This is a bad argument for two reasons:

1. People in dungeons can still auto-logout after 30 minutes.
2. The duty still has a duty timer preventing idling indefinitely.

It's better to try to plan ahead and take care of anything that might interrupt you while in the duty before the duty starts, or postpone doing the duty if necessary. I've been AFK kicked myself a few times because I had to step away longer than expected. I just restart the duty when I'm able to return. There have been other occasions a delivery or phone call was due so I put off doing the duty until after they were done. It's not a big deal.

Of course it's better to plan, but life does not always go according to plan. This is why there's a duty idle kick in the first place: to prevent your party members from being overly inconvenienced when your plans to BRB don't always go as planned. But in the absence of party members to inconvenience, the duty idle kick should be disabled. Just let the 30 minute auto-logout handle them.

Space on the instance servers is not infinite.

And that's why every instance has a duty timer.

[Breakbeat]

Can I just suggest auto-running into a wall...or do you need to do something besides move for it not to kick you?

OP is talking about the inactivity timer (10 mins), right? Not the duty timer.

I won't really get into the moral debate of whether auto-running into an object and thereby taking up an active instance slot is "a good thing to do." Maybe yes, maybe no. Objectively, I will say that the overall impact of people running into instance walls to beat AFK timers isn't significant from a technical standpoint.

And, regardless, the duty timer (the max amount of time they want you in an instance) will run out anyway; you can't beat that by auto-running into a wall.

'Swhat I would have done if I was 45 minutes into a solo instance and I knew I was going to be pulled away for more than 10.

[Ilisidi]

Afaik, keyboard activity is what prevents the timer, not character movement.

[Rongway]

Can I just suggest auto-running into a wall...or do you need to do something besides move for it not to kick you?

Afaik, keyboard activity is what prevents the timer, not character movement.

Ilisidi is correct; you can't just tape down a key or tie your stick to one side. You'll still idle out of a duty 10 min or logout 30 min after the last keyboard/controller state change.

[Stepjam]

Can I just suggest auto-running into a wall...or do you need to do something besides move for it not to kick you?

OP is talking about the inactivity timer (10 mins), right? Not the duty timer.

I won't really get into the moral debate of whether auto-running into an object and thereby taking up an active instance slot is "a good thing to do." Maybe yes, maybe no. Objectively, I will say that the overall impact of people running into instance walls to beat AFK timers isn't significant from a technical standpoint.

And, regardless, the duty timer (the max amount of time they want you in an instance) will run out anyway; you can't beat that by auto-running into a wall.

'Swhat I would have done if I was 45 minutes into a solo instance and I knew I was going to be pulled away for more than 10.

I'm pretty sure that loophole was closed at the start of Endwalker along with other methods to get around the afk kicker like opening the hud editor.