Announcement

Collapse
No announcement yet.

YOU HAVE BEEN DISCONNECTED.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • YOU HAVE BEEN DISCONNECTED.

    I think I'm going to write Sony to see if they can make that message stay up a bit longer, I don't think the 2-3 minutes my screen is all black and those words are in bold white in the middle is long enough to read it.

    (/sarcasm)
    Draggar De'Vir
    92 Assassin - Povar




    Xzorsh
    57 Druid of Tunare - Povar
    47 Druid of Tunare - Lockjaw

    Hark! Who is that, prowling along the fields! It is Draggar De'VIr, hands clutching two hardened pitas! He cries gutterally: "In the name of Thor the Mighty, I hereby void your warranty, and send you back to God!!!"

    "No one can predict the future, so we all should eat our desserts first!" - Gaye from 'The Maelstorm's Eye" (Cloakmaster's Cycle book 3)

  • #2
    I agree that this message displays just a wee bit too long.

    I've yet to understand why EQ takes as long to close down as it does. Most all of my other programs/games take from 2-5 seconds to go from clicking 'exit program' to it being cleared from memory. Everquest takes 30 seconds or more AFTER the screen freezes following 'Your camp will be ready in 5 seconds'

    Even /q takes quite a long while.

    While I suppose there might be some reasons to avoid exploits and the such, but if that is their goal then why not just make it so you can't log back in again for 1 minute after you log out (Perhaps a forced 1018?)

    Kitchi Behlakatz
    65th Season Feral Lord of Rodcet Nife
    Proud Owner of the 8th Coldain Shawl

    Comment


    • #3
      Actually, EQ tries many many many times to re-establish a connection to the world-server, then the login-server before finally dying to the desktop.

      That's part of the reason for the delay.

      ~Lothay
      Lothay retired from EQ in 2003
      EQ Traders - Moderator - MySpace or LiveJournal

      Comment


      • #4
        One would think they'd have learned that once the connection goes bad it's GONE.
        Similar thing in Warcraft III. Try to connect to a custom map game and gotta way 15-some-odd seconds unable to do anything while it times out.

        Connection bad = quit and dump program from memory... this ought to at least be an option you can chose in the program settings.

        Kitchi Behlakatz
        65th Season Feral Lord of Rodcet Nife
        Proud Owner of the 8th Coldain Shawl

        Comment


        • #5
          Actually I don't think desperatelly trying to reconnect is a bad idea.
          For example my DSL connection drops every 24 hours to aquire a new IP address, over 50% of the time EQ surrives the reconnection even if the DSL has to 'dial' twice. This saved me from CR a few times.

          Comment


          • #6
            It tries to reconnect you say? really, so why does it never succeed?

            my experience:
            I live in the UK, my ISP cuts me off every 2 hours and I have to reconnect. Normally I time it and log out to reconnect, but occasionally I just dont notice untill the packet meter (or whatever its called) starts to drop. At which point I will alt-tab out to my dialler and redial. It never lets me continue playing, ever. I allways get either back to server select or to character select (though the latter only happens very rarely). Or would you consider that a reconnect, I wouldn't, it stops me from playing the game for a while - even though my ISDN box takes about 3 secconds to get connected I still am dropped.
            Kcalehc K'Venalis
            Teir`Dal Overlord
            Officer, Trader and Gentleman
            Order of the Raven's Tear
            Tholuxe Paells (Bertoxxulous)

            Comment


            • #7
              Originally posted by Pojodan
              I agree that this message displays just a wee bit too long.
              /a-frickin-gree

              Everquest takes 30 seconds or more AFTER the screen freezes following 'Your camp will be ready in 5 seconds'

              Even /q takes quite a long while.
              they say SOE has 'fixed' this bug, so it works for all classes now? haven't played eq since early june...

              i play a casting class, so i have a spellbook, so this worked for me even before the fix. /camp desktop. that, combined with my ubah new processor (pardon my stupidity, i was never very good with remembering numbers), lets me log to desktop approximately 5-7 seconds after the '5 more seconds to camp' message.

              BUT. none of the other, normal, methods work. and no, it does not make any sort of sense as to why.


              While I suppose there might be some reasons to avoid exploits and the such, but if that is their goal then why not just make it so you can't log back in again for 1 minute after you log out (Perhaps a forced 1018?)
              ...... how could logging around very quickly help someone engaging in exploitation? just don't understand.

              -- sanna
              Mistress Tinkbang Tankboom - Ak'Anon, Tarew Marr
              Gneehugging Chantaranga of the 66th Mez Break - AA:59
              Assisted by Nakigoe Sennamida, Druidess of 65 Foraged Steamfont Springwaters - AA:8
              Quartic, Darkie Wizzy of 52 Self-Snares - Best Crit: 1680.
              [BK-210 // BR-250 // BS-203 // FL-200 // JC-240 // PT-200 // TL-200 ]---[ TK-179 // RS-182 // FS-165 ]-- Points: 1503/1750 -- Shawl: EIGHT and wearing it ^_^.
              Icon by Kenshingentatsu

              Comment


              • #8
                how could logging around very quickly help someone engaging in exploitation? just don't understand
                Many monks and shadowknights use /q to leave the game when they pull too many mobs, and the mobs are not losing aggro when they feign death. It is a tactic that players have used for years in raids. Maybe it is seen as an exploit by the folks in charge? Players see the not losing aggro as a bug, and the folks in charge see it as a feature (since it was put in deliberately).

                Comment

                Working...
                X