Oh I know this will never happen again because they will never use this method early in an exapnsion and in the MSQ. That will be the true fix.
Now.. if only I can get past the Steps of Cold Steel....


Oh I know this will never happen again because they will never use this method early in an exapnsion and in the MSQ. That will be the true fix.
Now.. if only I can get past the Steps of Cold Steel....


Been hammering at this for hours (I logged in the moment servers went up) and I am determined to get through it. I kind of wonder if we will get any sort of compensation for this.
This may just be grumpiness from a lack of sleep, but I find this to be very bitter. We moved the datacenter to a rather unfavorable place for a larg number of players; and those players swallowed this bitter pill in hope for a more stable launch/early access, but the launch/ea turned out to be a disaster anyway. I also really feel for the people who took time off work just to run into this.
On a different note, considering how other instanced content seem to be working fine, I wonder if they are able to take resources from maybe less popular instances and use them to let more people into coldsteel.
Also, if they seen this ahead of time, I felt like they could have at least implemented a queueing system so people really could hold a spot in an actual line and do other things while waiting for their turn instead of having to hammer away at Raubahn. Raubahn basically became the moogles of Stormblood.
Last edited by Yahallo; 06-17-2017 at 06:53 AM.

Other instanced content isn't working fine. It's d/c every couple of minutes. The amount of PotD losses we had yesterday due to time running out (0-70) was insane. One person would get in, someone else would d/c, then everyone gets kicked and can't get back in because it's the duty server. I am currently at 2.5 hours of trying to get back in after a PotD d/c. It's far from just being that one quest that's jacked up. I got on at 4 am yesterday, didn't go to bed until 10pm. I got RDM to 56 which is just freaking stupid. Today I got 2 more levels before the crap kicked in again.
Hubby took a day off work yesterday to get a jump start on things, that was a wasted vacation day of epic proportions.




And now I'm really glad I didn't take any days off for this. I get the situation, I really do but I might make my weekend centered around playing my leftover PS4 games.
Healing DRK is literally... the same since ShB. The reason why people think it's a meme to heal nowadays because DRK receives very little to no buff to their sustainability vs 3 other tanks getting something useful. If you're capable of healing DRK back in ShB (or any tanks), then you'll heal EW DRK just fine.



I'm wondering if the reason for the throttling is to force players to slow their pace through Stormblood's content.
At least, it would be the first time I've seen a JP dev show concern over player completion speed, IE, Nintendo's open worry about early Splatoon players hitting level cap in a few days, when they expected it to take weeks to months.
Which wouldn't be a problem except for everything that is locked behind the MSQ.I'm wondering if the reason for the throttling is to force players to slow their pace through Stormblood's content.
At least, it would be the first time I've seen a JP dev show concern over player completion speed, IE, Nintendo's open worry about early Splatoon players hitting level cap in a few days, when they expected it to take weeks to months.

My problem with this apology is that this has happened before. This was an issue in Beta... in ARR.. Yoshi said the team learned from this. They should understand based on the past that these styles of content does not work for their current server structure. The team needs to learn from the past already and stop saying sorry already.
I remember that. We were stuck at an instance in Central Than and had to form a line.My problem with this apology is that this has happened before. This was an issue in Beta... in ARR.. Yoshi said the team learned from this. They should understand based on the past that these styles of content does not work for their current server structure. The team needs to learn from the past already and stop saying sorry already.



I could at least play the game during Heavensward early access.
The issue is this. Solo MSQ instances work like this. Proceed>>>>>>>Instance, Proceed>>>>>>>> No instance, pushed out. 50 people try to get in, none get in, time passes 200 try to get in, non get in, time passes 600 try to get in, 1 gets in, time passes 1k try to get in 3 get in. This is the snowball effect occurring at the comment
They seriously need to just admit they should of added a queue to solo instances a long time ago rather than apologize, the answer is so simple it just comes down to implementing it. Proceed>>>>>Queue>>>>>Instance, now you have control over the faucet of people entering the instance and the risk of any sort of crash occurring from congestion should be limited.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.
Reply With Quote





