This isn't new though, I that cost of repeating myself, SE has had issues with housing since housing came out, other older games have managed to have housing without the major flaws and yet SE can't seem to figure it out and the folks who have houses are always the first to say working as intended. There are other issues as well that folks just seem to gloss over.Quote:
Originally Posted by Jadedsins
Why even bother queing, what a joke system
Printable View
-
12-07-2021, 11:47 AMZyama
-
12-07-2021, 11:51 AMKalinas
I got down to 1 in the queue and then 2002'd.... and back to 4800 when I re-opened the client. I waited and fought multiple 2002s from 6:15pm until 8:30pm for nothing. :mad:
-
12-07-2021, 11:54 AMShurrikhanAre you implying only half of us get got?Quote:
Originally Posted by Greenshaw
(Seriously though, I tend to either get dropped upon attempting to connect to Data Center, within the first 5 minutes of my queue, or not at all.) -
12-07-2021, 12:01 PMTanis_Ebonhart
... To play the game? I've been getting on just fine.
-
12-07-2021, 12:34 PMRelisa
How a modern queue system should be implemented for all game servers / any game data center access points / website with heavy loads:
1. Initial https account authorization (load balanced, which does indeed seem to be the case for the actual launcher currently).
2. Send an https async request to queue system (again load balanced web queue system, can also incorporate DDOS protection via known services).
- By the way there are already known services that provide async queue systems available. (Playstation direct uses such a system and other online stores have started to as well, saw several during this Black Friday. They even referenced who it was powered by.)
3. Queue system sends back a queue token identifier.
4. No need for an always connected tcp / udp connection running to data center / servers yet.
5. The queue token provides the following: An unique Queue ID. Your assigned position number. Estimated wait time. Async Retry time.
6. No need to close out the client due to error 2002, because there is no active connection at this point. Client sits waiting to re-query the queue async callback, based on the provided retry time, until it is given the okay to establish a primary tcp / udp connection.
- Position number can be returned from the async callback so client gets an updated position view.
7. If you try to connect via tcp / udp without a queue token or queue token is not allowed yet then the connections are simply ignored and instantly closed.
8. If it is your Queue ID turn and you fail to establish a direct tcp / udp connection after x minutes, then and only then is your queue token nullified. At this point you would indeed have to start over.
9. Your queue token will also be nullified after successful entry into game.
10. Once in a game, a new identifier is created to allow you to bypass queue system for a one time use in the following cases: Improper Network Disconnect or Client Crash.
11. If you exit game normally then the one time use queue pass is revoked.
12. the one time queue pass expiry time is constantly updated as long as you are really online. Once a improper disconnect event has happened, does it no longer update. Giving you about a 2-5 minute window to reconnect your account and get back in game.
It is not complex to implement. And once again, there are already services designed and are available specifically for this and in use by websites all over already in the ecommerce space. However, these queue services do not require it to be a website only, as they are just API services.