Error 1018: Lame

[Simon Belmont]

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]

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

[odizzido]

yeah if you keep the char in for 3mins, but allow people to log back in that would be great.

[Abacab]

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?

[Zordana]

instant disconnect is exploitable, exploitable things suck, ergo instant disconnect sucks [You must be logged in to view images. Log in or Register.]

[guineapig]

It's not a bug people!

Haven't you ever played EQ on Live?

Can you imagine just getting instant do overs whenever you want by typing /q when the situation looks bad?

Please....

[Datante]

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]

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.

[Modal]

It's not so bad when everything is humming along, but on mornings like these, where folks are crashing every 2-3 zones, this is super annoying.

I'd rather see a few people exploiting /q now and then than spend 5-6 times the normal travel time due to constant crashes/1018 errors. This is an emu server, after all. It's not going to run as stable as a live server, so mitigating downtime due to the regular crashes the emu presents ought to be just as important as presenting the live experience.

[Leolan]

I, too, have been experiencing the Error 1018 message when trying to log-in. I have seen it before after crashing, but it happens when I /camp and then try to re-login. I know it's only supposed to take a short time for the server to synchronize but it is taking at least 20 minutes every time...