Error 1018: Lame

odizzido · #1 02-24-2010, 03:26 PM

I know it's classic, but staring at a login screen for ages is just not fun. Honesty it was a mistake to ever be made in the first place and something I really don't think we need for the classic experience.

**Rogean** · #2 02-24-2010, 03:28 PM

It has nothing to do with classic and it's not a mistake. How else would you have us handle clients that are linkdead? Let people instantly disconnect themselves whenever they want? That would be hugely exploitable, as it was before.

Simon Belmont · #3 02-24-2010, 06:14 PM

Quote:

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

It has nothing to do with classic and it's not a mistake. How else would you have us handle clients that are linkdead? Let people instantly disconnect themselves whenever they want? That would be hugely exploitable, as it was before.

I am not good at all with computers, but is there a way to make it so you can log back in and take control of a LD character? It would fix the 1018 problem entirely and keep clerics or players from /q instantly to avoid wipes. Going LD while zoning and waiting for it to come back is kinda annoying.

**Aeolwind** · #4 02-24-2010, 07:06 PM

FYI, WinEQ2 will solve most of your crash problems. EQPlaynice helps tons and it is built into the Free Edition of WinEQ2.

citizen1080 · #5 04-15-2013, 10:19 PM

Quote:

Originally Posted by Aeolwind [You must be logged in to view images. Log in or Register.]

FYI, WinEQ2 will solve most of your crash problems. EQPlaynice helps tons and it is built into the Free Edition of WinEQ2.

I can't run eq without using WinEQ2..just loads a black screen. I think it has something to do with my hexcore cpu tho. Regardelss tho..wineq fixes most issues as stated above.

Abacab · #6 02-25-2010, 11:22 AM

Quote:

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

It has nothing to do with classic and it's not a mistake. How else would you have us handle clients that are linkdead? Let people instantly disconnect themselves whenever they want? That would be hugely exploitable, as it was before.

I liked the instant disconnect, if I had a bad pull or group was about ready to wipe I'd just /q log back in and hide without a scratch on me and save a HUGE CR.

Did you specifically change it because people would just /q and relog when shit got hot?

Datante · #7 02-25-2010, 07:22 PM

Quote:

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

It has nothing to do with classic and it's not a mistake. How else would you have us handle clients that are linkdead? Let people instantly disconnect themselves whenever they want? That would be hugely exploitable, as it was before.

The current timing for LD character poofing seems fine and classic (30 s or 3 min if aggro); however, back in 1999, I specifically remember the game skipping me past the character select screen and putting me directly back into the game if my toon was still active after I went linkdead. This could not be used for exploiting (character can still die or even aggro), but rather allowed a person to possibly recover from an unintended LD a bit quicker.

When did error 1018 become a regular issue? Possibly after 1999?

odizzido · #8 02-27-2010, 06:42 AM

Yeah originally it was that if you went LD your character would stay in the game for 3mins or whatever, but you were allowed to log back into the game at any point to assume direct control.

I cant think of any way this would be bad as it would get rid of the instant /q disconnect, as well as get rid of the annoyance of sitting around for 3mins every time you get dropped from the server.

Goobles · #9 02-24-2010, 03:33 PM

30 seconds to 3 minutes is an ETERNITY Rogean! Please have mercy!

President · #10 02-24-2010, 03:57 PM

Yea I dunno I understand not wanting people to instantly DC but I nearly ragequitted the other day before I even logged in. I crashed while zoning just after logging in, took about 3-5 minutes to get back on. When logging in I opened up Ventrilo which in windows 7 pops up the stupid "is this ok?" dialogue and crashed me again. Another 3-5 minutes to get back on. Then I somehow crashed after selecting char, no idea I normally don't crash like this but it just sat there forever and never logged me in... another 3-5 minutes..