The same as so many are experiencing, I waited for hours in the queue on one of my FEW free days. Hours. Then it silently crashed. Queue upon re-opening it? 2199. You NEED to create a queue reinsertion hold. You accomplished this with LD relogging WHY wouldn't you have included it in the QUEUE place holder?

I guess I'll try to play DAoC in a month and hope you've gotten this fixed, because I can't waste my days HOPING to play.

I agree and I am totally ****** right now. I waited 2 times for 2+ hours. And also silently crashed at both times. Last time when being number 10 in queue. Seriously? And now I am back to number 2400 in queue. Please fix this so if you crash when in queue you get sorted back in line to where you crashed. This is some major BS!

Just did for me to now

1 thing i noticed about this silent crash:

When you are in the queue waiting, try to ping some website continiously (f.e, http://www.google.com). How do this: Run > cmd > ping /t http://www.google.com.

Why doing this ? Very simple, i noticed that when my network connection is lost for a few seconds, the application (the queue, whatever) quits. How to see if your network connection has an issue ? If you get something like this, this may be your problem:

64 bytes from xx.xxx.xxx.xxx: icmp_seq=0 ttl=56 time=11.632 ms
64 bytes from xx.xxx.xxx.xxx: icmp_seq=1 ttl=56 time=11.726 ms
64 bytes from xx.xxx.xxx.xxx: icmp_seq=2 ttl=56 time=10.683 ms
64 bytes from xx.xxx.xxx.xxx: icmp_seq=3 ttl=56 time=9.674 ms
64 bytes from xx.xxx.xxx.xxx: icmp_seq=4 ttl=56 time=11.127 ms
Request timed out
64 bytes from xx.xxx.xxx.xxx: icmp_seq=6 ttl=56 time=15.123 ms

(Just a random example, ofc)

The "request timed out" can cause that you are kicked from the queue. What is the solution ? Well, no simple answer possible. Check your internet connection, your local network (WIFI, PoL, etc ...)