Quote Originally Posted by Sove92 View Post
Those maps don't actually use the normal aethernet system to begin with, so they never got the update. It has got nothing to do with spaghetti code and fates.
Huh. If they treat the Firmament under the hood as a dynamically allocated field zone (as opposed to a static instance, a'la housing wards), it would actually explain that.

I wouldn't have thought they did, because I remember when the Firmament launched we had problems where people could not get into the Firmament -- if I recall right, it's why they blocked folks from participating in the Firmament FATEs on servers other than their own, because people were server-hopping and flooding whatever server would have a FATE up next. Whereas Eureka/Bozja zones, if one is too full (or if an instance has gone 'stale' -- e.g., all the various NMs/Skirmishes/CEs have been expended and everything's on cooldown) it stops funneling people into that one and creates a new one.

But that change note does certainly imply that the Firmament acts that way under the hood. I wonder if that was a later change -- if they retrofitted it quickly into a dynamic field zone to make it potentially spawn new Firmament instances -- to address those overloading/crowding issues. If so, that'd definitely explain why it uses the older aethernet system still.