Thank you, dev team, for addressing this issue!
Printable View
Thank you, dev team, for addressing this issue!
Yes I have been to your server and many others and seen how crowded it gets. Your server is not a special case. Anyone who server hopped can verify if my next claim is true or false. One hour before the FATE was a good time to go into the firmament with a high chance of it not being congested. Before then, have all your mats prepared so you can craft while you're inside. The FATEs don't pop up every hour or so to the point you don't have time to restock before the other server FATE is up. If you didn't have time to restock between the many hours for each FATE, then that's a "you" issue.
In my case, I have many sample point to draw a conclusion from. But in yours, you're only sticking to one server, which means you didn't do the FATE as much as we did to know exactly what are the optimal times to go in.
The heart of the matter is you shouldn't HAVE to camp out in the zone an hour out, and even so, if a world's Firmament is clearly overcrowded, the gracious thing for Wanderers to do would be to bow out and let the natives fill up the slots. There are no shortage of crafters and gatherers on many of these worlds, and I don't recall Midgardsormr collectively sending out invites for other worlds to come help us out, so even under the guise of "helping", that argument falls flat. Besides, hopping worlds just to experience content is a meta that shouldn't be expected of the average player.
But it's all a moot point, now, so oh well.
You just keep digging yourself a deeper hole, you realise? Encouraging server hoping, and admitting to tracking times, entering only an hour before? And yes... my server was always packed well before, with wanderers happily (and seeming astonished) that they got in, because of early congestion. Server natives shouldn't have to camp out in hopes of accessing their own server's content. We didn't ask, you came anyway and claimed to be "helping". Please, it's obvious what you actually came for.
Exactly this. For crying out loud, you'd think we committed some terrible crime by pointing this out. People still keep trying to justify it. It's the cutscene exploit in the MSQ roulette all over again...
Its pretty absurd to have to do this, but on Crystal, if you arent in the zone slightly before the 2 hour mark (unless its into waaaaaay-off-hours) you wont be getting in. Coeurl's firmament was soft-locked (locked for people but you could get in as people were wandering in and out) within minutes of us hitting our 2 hour warning last night at right around midnight est, and it only had a smattering of wanderers who had been waiting there since we were at 75%. Tthere were 3 servers that were due to hit fates around the same time, so people from the other servers were camping out between those 3 for most of the night.Quote:
One hour before the FATE is when you should start crafting and not leave the instance. Not 1:30 to 2 hours.
The way the system is set up is stupid, at least as far as the fate is concerned (but again, the fates are basically worth 20 minutes of gathering and crafting, so its kind of moronic for people to sit there for hours if they arent going to be actively contributing during that time). That you can see what other servers on your datacenter are close to completion and just park yourself in the Firmament afk, or functionally afk, for a couple hours needs to be changed. If you're contributing, sure, fine. If you're camping out for a spot, no.
Theres not really any low-pop servers in NA, and only 2 in EU.Quote:
Low-pop servers? We aren't complaining one bit. I'm finding that no one in a low-pop server is complaining about the change at all, and welcoming it.
If you even look at just level 80 active population, theres all of 1 NA server under 8k, and thats at 7.9k. EU outside Sprigtania averages just under 10k, Japan is at ~6k.
Is there a problem in doing that? Is this against the TOS or some sort of exploitation that I'm not aware of? Because this argument fails to address anything I pointed out and just seems like you're strawmanning now.
You have an event with more than 300 wanting to partake in, but they know that it will be locked if they're not early. What do you think would happen? Of course people will camp it. That's the only option they will do. Because the main issue that some are blind to, is that you only got one instance per server with a hardcap of 300 (correct me on that number if I'm wrong). Wanderer's or not is just a silly argument against the main issue. People still camped instances for Ixion FATE back in SB because it got congested in 1-2min after it spawns. Thanks to the random timer, there were no cases of it being congested for an hour, except at one time when the respawn timer was over 70hrs.
Not sure if you mean the reason Moogle is at 40% is because off-worlders helped contribute before and can't do that now.
On ragnarok it's barely around 50% right now. The third stockpile seems to be much bigger this time around. Looking at the website I don't see any server having hit the malmstone for the third fate series.
There was nothing wrong with wanderers participating. Many of them crafted while waiting. There are plenty in world who sit around and simply wait for the fate as well and don't contribute either To somehow try and impart bad motivations to those visiting is wrong in my opinion. The real problem wasn't the visitors it was the design of trying to funnel way too many people into one instance. That was and still is the issue. SE appears to have taken a quick fix and whether or not it'll be fine in peak hours remains to be seen.
If I'm not mistaken an instance holds roughly 350 people or there about. That number many still be well below the demand during peak hours and on weekends. It was just poorly implemented and everyone who was locked out paid the price for it.
You seem to have not understood what I said. But anyways, server hopping for the FATE was not the issue they wanted to prevent. Else they could easily do a simpler approach that would not affect other worlds' progression, which is giving 0 rewards to wanderers. Thus, their initial design intent to have other worlds help each other would be preserved in this case. The issue they wanted to stop was the congestion from those who would just park in the instance for 3-4hrs being AFK (which they can go around if an AFK timer was implemented). See the difference?
With the world transfer, 1hr was a safe time that you can go before it gets congested. Now that it's restricted, I'd probably say 5-10 min would be the time the instance will get congested on a medium populated server. So again, server hopping for the FATE itself was not the issue. Read it on their own official statement.
What’s interesting with the numbers posted earlier for NA is they matched as far as I could imagine with my DC in that similar servers were around the 30% mark, high pop servers around the 40% mark. So the pacing seems to be the same for population size. So I don’t feel like we are slower and if we are we were all slowed to the same rates if that makes sense
FYI, one hour before FATE, Balmung is already congested even without world visit. So really amazing fix, locking out the actually active people interested in content.
If the population cap isn't going to be increased in the Firmament with the area now locked to home-worlders only, can we please have a Potkin-NPC outside that can accept turn ins? I dunno how tough it'd be to code this, but it'd be nice to be able to continue turn ins even while the zone is locked down while people wait for fates.
If the Firmament is going to continue to be locked to Wanderers, we really need to bring back the AFK kick timers.
Being locked out while a ton of people are AFK inside is frustrating. At least before, I could just go to another server and do the FATE there, but now I can't even do the FATE at all thanks to the lockdown on World Visits and AFKers.
Multiple instances need to be implemented, or a timer needs to be implemented. High-pop servers' Firmaments are still getting congested hours before a concerted work due to people AFKing in the instance.
Agreed. There's a huge mass of people AFK at the builder's board here on Balmung who haven't moved for hours and who are keeping people from even zoning in to do turn ins. Having an NPC outside the Firmament or even just a re-instituted AFK kick timer would go a long way to ensure the people clogging the area for the sole purpose of doing the Fate aren't preventing people who genuinely want to do the turn-ins from doing so.
We need either:
1. More instances for that single zone.
2. The AFK timer to stick around for another patch.
3. A turn in NPC outside.
4. Or all of the above.
Locked out of the firmament due to congestion. Please consider opening multiple instances. At the very least, I would like to do turn ins and buy stuff from the scrip vendor from outside the firmament if its going to be locked at peak hours.
The AFK timer would do nothing because they could just start crafting and sit on the craft doing nothing to bypass the timer. This has been a common way to beat the timer forever now.
I see what I predicted would happen is already happening on Balmung. Now I hope some that were blind to this would see why locking was just a terrible band aid solution. This is worse than Ixion camping, since people already know when the FATE will start so they will just camp the zone.
Not everyone is aware of the way to circumvent the kick timer; and it would help alleviate some of the congestion. At the bare minimum, re-implementing it doesn't really hurt anyone, but does potentially help people in addition to other measures they could take.
Just scrap the fate. Was a nice idea but if it still doesn’t work...
Just make it upgrade automatically when the bar is full and anyone who turns in a certain number of points towards it get ls a ticket to turn in once complete the bar for 500scripts. Kinda like cactpot I guess but not scheduled every Saturday lol
Also just that how many crafters who already got the rewards they wanted are willing to stick around and keep pushing the progress bar?
A second hand-in NPC would definitely be a good idea. Perhaps they could put it at the guildleve counter?
While the AFKing does sound like a problem (and maybe a difficult one to solve without manual policing of the zone) the change DOES have the intended effect of letting more people participate because now a full 300 natives of each server are able to be there.
Say there are eight servers - this should mean 2400 people get to experience the event.
If a group of 50 people is server-hopping:
50 people do the event eight times each.
8 x 250 = 2000 people do the event once.
A total of 2050 people got to participate, while 350 people miss out on joining in because their spots were taken by the people who did it repeatedly.
Increase the server-hopping group to 100.
100 people take multiple turns.
1600 people do it once.
1700 have participated and 700 have missed out.
Whatever other effect these changes have, it will undeniably return that participation to a full 2400 people getting one turn each, and not being able to take a second one.
It’s ridiculous that I keep getting locked out on my home world because of World Hoppers! There was a whole group who even said next World is xxx. I work to put I. Supplies and can’t do the fate because it’s full of people, I want to be able to do content and get rewards too, this is an unfair advantage and something needs to be done. Square obviously doesn’t care, as that point was made from Yoshi-P so I’m starting to thing it’s time to find another game to spend time and money on.
They might not be able to add instances for this type of content. What happens if one of the FATEs were to fail? If they add instances to only servers with congestion issues, that would allow for double dipping and would not be fair to the other servers. If they add instances to all servers, then servers without congestion issues would be able to double dip easier than those with.
Ok, so, amidst all the back and forth drama, can we all maybe just pause for a second, take a step back, and appreciate some of what's going on here, too? As far as I'm aware, despite the major congestion and congregation, I haven't heard of any servers or data centers buckling under the pressure. The World Visit system likely saw a significant stress test through the past couple days. The instance was fairly stable, not much of a lag factory. Haven't heard any complaints about long load times or anything getting in.
All things considered, wanderers aside, this has all gone off incredibly smoothly. Gotta say, I'm impressed at what the system/hardware surely must've handled in a short time frame.
And I also choose to appreciate, despite all the bumps along the road, that SE is experimenting here with giving us new forms of content. I should say they definitely deserve a little leniency here as they figure out how this content fits with the game's community. Tried something, didn't work the way they wanted, had to change direction. It's surely still a learning process for them as well. No matter how you're impacted by how things are going one way or another, I say at least enjoy/respect that this is all new territory for them, too, and we're all learning together.
It's been a bit chaotic, but I hope that doesn't turn them off from trying other new ideas in the future.
Quoting this because more people need to see it.
The change is having exactly the effect it was supposed to - preventing server hoppers from flooding other servers.
While SE (again...) should have implemented an instance system on higher pop servers to begin with, not being able to enter ones' firmament does not entitle someone to crashing another server's firmament, preventing server natives from accessing it. I don't know how I can explain this any more simply than I already have, over and over. It was just a ridiculous spiral of off-worlders screwing over server natives, then those server natives hopped to another server to do the same thing, deciding to keep it going because they wanted to reap the rewards... an endless cycle of nonsense. However, since [i[that[/i] was dealt with, poke SE until they implement instances... which, again, should have been done from the start, but this is SE, and it's hardly the first time they've made an oversight like this.
Before the hotfix is applied:
1. People blamed wanderers for getting them locked out.
2. People blamed campers who were AFK that they are getting locked out.
3. People blamed that those mentioned in #1 and #2 are not contributing turn-ins to the server.
4. People were not able to interact during the event
5. FPS drop
After the hotfix is applied:
1. People still blaming campers who were AFK that they are still getting locked out.
2. People blaming those who were AFK are contributing turn-ins to the server.
3. People were not able to interact during the event.
4. FPS drop
About the people who were AFK, as most people might not know about it...they might be resting after doing several things like: (gathering mats / crafting, quick synthesis for the event, did other dailies/weeklies and newer content) maybe they're just tired and don't want to miss the event due to timezone difference as well then just waiting for the Concerted Works to commence. You never know that those people did the work too and just needed to rest from IMO. I mean, give them a chance, they contributed and won't get something from it? Anyway, it's up to SE.
I think the following should help to address the situation:
1. If you're on PC, press and hold X to hide playernames and all so you'll see what to click. If you're on PS4, just hide the names in settings. That should help with the "can't see what to click".
2. SE should allow us to turn off weather effects like snow, rain and other effects as it tears down the fps framerate. I had like over 100 fps at maximum settings and seeing it drop to 30 during this event with wanderers or not. If you're getting it lower than 30 fps during the event, I guess it's time for you to upgrade with gaming specs.
3. SE should indicate what is the maximum # of players allowed for the Concerted Works just for everyone's reference. A disclaimer is a must before entering the Firmament.
4. Put in some requirements inside the Firmament before people can start joining the Concerted Works. That way if people see any AFKers in-game they would just say, they're just waiting for the event to start after they did their part.
5. Or as an alternative to #4, why not create another 'dungeon instance' like what you did in Baldesion Arsenal wherein the Firmament is like Hydatos then the Concerted Works is like Baldesion Arsenal. Make the event a multiple instanced dungeon happening at the same time during peak hours. The rewards should be one-time if you participated within that timeframe until we get to the next stage. That way people can experience the event without getting locked out regardless if there's a wanderer or not (how they execute this depends on SE, just giving out an idea).
Multiple instances wouldn’t work in this kind of content unless they divided the server progress in the fates by the number of instances