136195-why-is-it-so-hard-for-them-to-understand

== Content ==
			You're not correct but at least you're attractive.	
----
			the login loop is because the instanced zone we are trying to log into is full. The ones that get in are the first ones to get the spot when a spot opens.  Its so *cupcake*ing simple and only total idiots would not understand it by now. Make it so we log in opens a fresh instance at 50% capacity instead of 100% capacity problem solved.	
----
			oh and be sure the instanced zones are releasing our toons as we disconnect otherwise you will have it trying to log us back into the instance we were in before and if its full we will never get in.	
----
			I don't think it's just that. What if you're loading into an empty instance? Like as an example I was on not too long ago and I went to harvest an iron node. A big worm popped out and I killed it which revealed a glowing hole I could jump into. Going into that hole, that instance, put me in a loading screen and then thrown back to character select. Now my character is in an empty instance by himself and cannot get back in.	
----
			Yeah... you have no idea what you're talking about.	
----
			
{| class="blockquote"
Its so *cupcake*ing simple and only total idiots would not understand it by now.
----
			I'm always amazed at how many people are suddenly experts when something goes wrong. :X Rule of thumb, if you think a problem that persisted for a while has a really simple solution, someone else probably already thought of that - and it didn't work.	
----
			
{| class="blockquote"
What an angel. :)
----
			
And where's your... you know... proof of this?
 
Because I sincerely believe that if it was this simple it wouldn't take over 4 days to fix. The people working at this are much more capable and competent than you are.	
----
			
{| class="blockquote"
I don't think it's just that. What if you're loading into an empty instance? Like as an example I was on not too long ago and I went to harvest an iron node. A big worm popped out and I killed it which revealed a glowing hole I could jump into. Going into that hole, that instance, put me in a loading screen and then thrown back to character select. Now my character is in an empty instance by himself and cannot get back in.
----
			ok if its cuz of the instanced zones then how come the loop still happens even on a band new just made toon??	
----
			Maybe not the actual instance but the instance servers	
----
			
{| class="blockquote"
And where's your... you know... proof of this?
 
Because I sincerely believe that if it was this simple it wouldn't take over 4 days to fix. The people working at this are much more capable and competent than you are.
----
			It was stated during the WildStar Launch Update @ 11am PDT Oct. 2 stream that if your character did not load in properly, you got kicked back to the Character Selection screen. The recommendation was to try again. Sort of a fail-safe so you wouldn't load in with a broken character, missing gear, etc.
			
				
	Edited October 3, 2015 by Alysion	
----
			
{| class="blockquote"
the login loop is because the instanced zone we are trying to log into is full. The ones that get in are the first ones to get the spot when a spot opens.  Its so *cupcake*ing simple and only total idiots would not understand it by now. Make it so we log in opens a fresh instance at 50% capacity instead of 100% capacity problem solved.
----
			Most of this shit should have been worked out prior f2p went live but it wasn't so now everyone has to deal with the dev's *cupcake* ups so the only ones to be mad at are the devs and the programmers and the idiots that let other countries in our realm	
----
			
{| class="blockquote"
Unless it is this simple and they just don't know how to fix it... Nobody ever considers that the devs could actually be incompetent.
----
			
{| class="blockquote"
I would bet when you get back in you are no in the cave you are in the main instance
----
			
{| class="blockquote"
You don't have a single clue on how software programming works, do you?
----
			
{| class="blockquote"
You don't get a game this far on incompetence.  
----
			
 
So, the wife made some cookies with Raisin Bran Crunch in them. Dang, those were some good-ass cookies. 
 
I was all like NOM NOM NOM NOM 
			
				
	Edited October 3, 2015 by TexArcana	
----
			
{| class="blockquote"
It's really simple to understand when you decide to not only not bother learning how it works in the first place but deny that you did.
 
Then EVERYTHING you say must be true.
----
			
{| class="blockquote"
Just like how people think they're internet lawyers when they know next to nothing about laws?
----
			 They already stated the daemon isn't doing his job right..  	
----
			
{| class="blockquote"
 
So, the wife made some cookies with Raisin Bran Crunch in them. Dang, those were some good-ass cookies. 
 
I was all like NOM NOM NOM NOM 
----
			
If you go watch their stream this morning, you might be able to understand how "one does not simply fix the instance zone issue". The problem arose from fixing something else. This is how it usually works on the backend.. fix something and something else completely unrelated breaks. 
 
There have been multiple threads where lead engineers/designers have commented. It's known that they're all exhausted and that their office is full of tired bodies and tons of red bull/mtn dew cans. They've probably gotten little to no sleep since launch. 
 
They're going through code trying to fix it, but it takes time. They've told us they tested this on the PTR and had no issues, but then again, they didn't have the population on the PTR they have now. While I DO think they should have figured out a way to "worst case scenario" this launch before it happened, they are trying to fix it now. Name calling and getting angry because a video game that most of ya'll arent paying for is only going to *cupcake* you off, not affect the dev's attempting to fix this, and ruin your opinion of this game. Take a deep breath, go to bed, and come back tomorrow and see if any progress has been made. Rinse, repeat. 
 
TLDR:
You don't actually know whats going on in the back end of their servers and they're trying to work it out. Yes, they messed up. Yes, they're trying to fix it. Relax, its just a game. Go drink a beer.	
----
			
{| class="blockquote"
How far? The game is unplayable since, ya know, infinite loading screen.
----
			
{| class="blockquote"
It was stated during the WildStar Launch Update @ 11am PDT Oct. 2 stream that if your character did not load in properly, you got kicked back to the Character Selection screen. The recommendation was to try again. Sort of a fail-safe so you wouldn't load in with a broken character, missing gear, etc.
----
			
{| class="blockquote"
You don't get a game this far on incompetence.  
----
			
{| class="blockquote"
I would bet when you get back in you are no in the cave you are in the main instance
----
			
{| class="blockquote"
 
So, the wife made some cookies with Raisin Bran Crunch in them. Dang, those were some good-ass cookies. 
 
I was all like NOM NOM NOM NOM 
----
			
{| class="blockquote"
 They already stated the daemon isn't doing his job right..  
----
			
{| class="blockquote"
the login loop is because the instanced zone we are trying to log into is full. The ones that get in are the first ones to get the spot when a spot opens.  Its so *cupcake*ing simple and only total idiots would not understand it by now. Make it so we log in opens a fresh instance at 50% capacity instead of 100% capacity problem solved.
----
			
{| class="blockquote"
Just like how people think they're internet lawyers when they know next to nothing about laws?
----