Players connot join the party while you are engaged in combat

[Peregrine]

While I think it's important to control the environment the players play in, there's a reason companies like Blizzard are among the biggest developers in the world. Blizzard allows the community so much room to do pretty much anything because humans (as in human nature) love choices and options. Look at how popular modular applications are nowadays. People want the ability to do what they want. SE should definitely enforce rules but to restrict something like this is a little crazy. This is one of those reasons people would see and think "wow, I don't want to play a game where the developers tell me what I can or cannot do". Leave community moderation to the GMs. Develop the game for the general people, not for the minority 16 yr old that wants to ruin other people's experience.

Ironically it's the 16 year olds that want the right to get back in the party. They don't know or care what consequences that actually has to the game's quality.

[Peregrine]

Stupid enough to...

- Not let you invite someone to linkshell unless they are within 10 feet.
- Not let you boot someone from linkshell unless they are within 10 feet.
- Not let you promote/demote someone from linkshell unless they are within 10 feet.
- Not let you ALT Tab to do other things while in full screen (this is going to change).
- Not allow players to send mail.

I can keep going...

Theres a metric *** of "oversights" in this game. Yes, the developers tend to overlook them - it doesn't make them stupid. The only people that are stupid are those that would find ways to defend these overlooked features.

Ava, be careful mentioning Blizzard around here. Theres too much logic in their actions and thats isn't welcomed here.

Your wishes weren't an oversight that got forgotten. They are a mistake that got corrected. lol... Of course they still make oversights like ls management options. They're human. Not stupid.

I'll say this gain, they didn't forget you. They accounted for you. That's no oversight. It is...how does Blizzard put it? Oh yes "working as intended."

[Kurokikaze]

And you still defend it... My god, this conversation, if it was one, is over.

[Kam]

Again, how stupid do you think the developers are? Clearly pretty stupid.
Alt tab gets you out of the party in fulscreen.
Hitting the x button at the top right of the windowed screen gets you out of the party.

This is "harder" than logging off how exactly? Let's hear THIS one lol...

harder=/=elaborate.

You're thinking too much about XI, and not about XIV.

[Peregrine]

And you still defend it... My god, this conversation, if it was one, is over.

Dude, you never had a chance. If tanaka were still in charge, they'd just tell you to shut up. Of course they're not going to take screams that you should be let back in a party, swap jobs in a party, go in and out of a party seriously. They obviously nixed that from the start, and fully committed to keeping you from doing it for very good reasons.

Don't understand the reasons? Well, you don't have to. No one said you had to understand why the speed limit was 55 once you get near downtown on an interstate. Honestly wasting my time trying to explain it to you is...well...a waste of my time. That you even whine about it is probably proof that you'll never understand why.

So it's just the way it is.

[Sorel]

The question has been asked, and now answered. Technically, there's no reason for the discussion to continue unless it's about a different solution to the problem the OP brought up.

Otherwise, locking the thread is not unreasonable.

[Lerris]

They may be able to get around this by not booting the lost player for something like 10-20min. They could just have their name gray/red till they log back in.

This is how D&D Online handles it. In fact, if the entire party logs off and comes back, the party' actually remains intact even several days later, until the current party leader breaks it ( leader reverting to the first person to log on ).

[Kurokikaze]

This is how D&D Online handles it. In fact, if the entire party logs off and comes back, the party' actually remains intact even several days later, until the current party leader breaks it ( leader reverting to the first person to log on ).

It's actually how the vast majority of MMOs today handle D/Cs. Unfortunately, FFXIV is a hipster and cannot be asked to incorporate such mainstream technical features.

To be honest I don't its the devs themselves that don't want to do it. It's just that the spaghetti code that is FFXIV is so overly complex that the most mundane fix is made out to be monumental.

[Jinko]

Agree with what has been said, when a player disconnects they should be greyed out/ghosted until they log back on or a party leader removes them from the group.

It would save a lot of time not only for guildleve parties but dungeon ones as well.

It's just that the spaghetti code that is FFXIV is so overly complex that the most mundane fix is made out to be monumental.

Most likely, I hope this isn't a sign of what we have to look forwards to, SE you best get a second team working now to transfer your assets over to UE3 now, because the current engine just isn't going to last you another 5 years.

[Nuru]

If a player DCs, they should stay in the party, but to avoid being leeched, they will miss out on SP and Loot. Right now, that system isn't implemented. Main reason why I support their current system is because it can't be abused the way it was in FFXI. It possibly could be abuse, but the way it works right now would take chunks of time.

To the idea of keeping players within the party until they can log back on, well, imagine people force DCing just to chicken out of battles and claim loot. You can probably tell that I have a strong sense on how a community will be like and just how much they will abuse game mechanics just because they can.