Results 1 to 10 of 26

Hybrid View

  1. #1
    Player
    Eclipse's Avatar
    Join Date
    Mar 2011
    Location
    Gridania
    Posts
    383
    Character
    Eclipse Haven
    World
    Hyperion
    Main Class
    Astrologian Lv 70
    Yes please fix this.
    (0)
    TMPST Est. 1.0
    Tempest Free Company of Hyperion

  2. #2
    Moderator Xophious's Avatar
    Join Date
    Feb 2011
    Posts
    351
    Hello everyone!

    The thread was moved from In-Game Bugs to General Discussion since it's more feedback/suggestions related. The time it takes to re-log after being disconnected is very inconvenient, so I know how frustrating it can be. Hopefully the concern will be addressed to minimize re-log downtime!
    (0)

  3. #3
    Player
    Moth's Avatar
    Join Date
    Mar 2011
    Location
    Valkurm Dunes
    Posts
    474
    Character
    Taiga Inktooth
    World
    Midgardsormr
    Main Class
    Marauder Lv 50
    Quote Originally Posted by Xophious View Post
    Hello everyone!

    The thread was moved from In-Game Bugs to General Discussion since it's more feedback/suggestions related. The time it takes to re-log after being disconnected is very inconvenient, so I know how frustrating it can be. Hopefully the concern will be addressed to minimize re-log downtime!
    /hurray
    And I also agree with n0cks, DCing during a leve and loosing it is horrible, I know i've lost more than just a few good rewards simply because this has happened >.<
    (0)

  4. #4
    Player
    Joe_Cool's Avatar
    Join Date
    Mar 2011
    Posts
    115
    Character
    Jojo Cool
    World
    Hyperion
    Main Class
    Conjurer Lv 15
    Quote Originally Posted by Moth View Post
    /hurray
    And I also agree with n0cks, DCing during a leve and loosing it is horrible, I know i've lost more than just a few good rewards simply because this has happened >.<
    Hello! You can re-try any failed leves when the Leve-Reset happens. So, those good rewards can be acquired then!
    (0)

  5. #5
    Player

    Join Date
    Mar 2011
    Posts
    13
    Quote Originally Posted by Xophious View Post
    Hello everyone!

    The thread was moved from In-Game Bugs to General Discussion since it's more feedback/suggestions related. The time it takes to re-log after being disconnected is very inconvenient, so I know how frustrating it can be. Hopefully the concern will be addressed to minimize re-log downtime!
    I am sorry, but I have to respectfully disagree...

    If my Microsoft Word program crashes, and I have to wait for 15 minutes, or even 5 minutes to restart the program, then it is a bug with the program. The same thing applies to FFXIV... not being able to re-log in a reasonable amount of time is a bug with the game. Especially knowing that FFXI does not have this long wait time, there must be an easy fix.

    Please return this thread to the In-Game Bug forum and fix this bug with FFXIV.
    (0)

  6. #6
    Player
    Rhomagus's Avatar
    Join Date
    Mar 2011
    Location
    Limsa Lominsa
    Posts
    1,076
    Character
    Rhomagus Asclepiot
    World
    Ragnarok
    Main Class
    Weaver Lv 51
    Quote Originally Posted by Larther View Post
    I am sorry, but I have to respectfully disagree...

    If my Microsoft Word program crashes, and I have to wait for 15 minutes, or even 5 minutes to restart the program, then it is a bug with the program. The same thing applies to FFXIV... not being able to re-log in a reasonable amount of time is a bug with the game. Especially knowing that FFXI does not have this long wait time, there must be an easy fix.

    Please return this thread to the In-Game Bug forum and fix this bug with FFXIV.
    I don't agree that it is a bug but a heightened security measure that SE has purposefully implemented. On the up side to this method, if your account is compromised and your character is active in game, they can never log into your character. In XI, they could get access to your account, kick you out in the middle of your own session, then change your information so that you cannot get back in fast enough to counteract the cyber assault. This way, the compromiser cannot access your account right away and change all of your information. It's a bit of a moot point though as all the compromiser has to do is wait for you to log off.

    Unfortunately, the downside to it is what people have been noticing. Increased times to relogging when kicked from the server. Considering that this "security measure" ends up being moot anyways, as I've addressed above, they should change it back to kicking your character from the server if someone tries to log in.

    The downside to removing this "security measure" is that the character can be compromised more easily. The upside is there is a security token to keep such a thing from happening, which brings up a whole different topic.

    It may be a bit depressing to think that it's not a bug, I know, but considering an official forum moderator moved it from the bugs forum gives me the inkling that it's a purposeful security measure. I don't know what is required to be an official forum moderator but I'm leaning towards the minimum requirements being that you are on a localization team and may be privy to such information. It's a blind guess though.

    The good news is that absolutely no one is arguing that this method is somehow better or should maintain it's continued existence in the game. Even potential staff, as noted from the moderator's post, find it incredibly frustrating. Hopefully by having it in GENERAL DISCUSSION it will be seen as a design flaw that is having an adverse effect on all players rather than an isolated incident that would have to be addressed client side first then escalated later to a design flaw.
    (0)
    Last edited by Rhomagus; 03-24-2011 at 10:33 AM.

  7. #7
    Player

    Join Date
    Mar 2011
    Posts
    13
    I don't believe this is a security issue, as with coding, there is some place in the software that has a count down of sorts from the last time data is received. Currently the count down or timer is set to a longer time than needed. Although hard to believe, it is as simple as reducing the timer. Programming 101.

    The problem is as long as SE believes this is acceptable... as in a suggestion, they will keep it on the back burner, and work the bug list instead. It should be seen as a bug in order to raise the importance higher on the "to do list", otherwise it will not get fixed.
    (0)