Cobalt Arachne

There are seven motes in the Labyrinth that can be found and provide small buffs when approached that last until you leave the zone, these are also key to another puzzle that ends in another reward. These puzzles are most reasonably tackled solo, but could become a group activity if everyone is working on the same goal. What purpose do the mote anchors serve? They pulsate with most malevolent energy... There's also unique Labyrinth-themed prizes, one prestige costume (that has six customizations) and two vanity pets to figure out their unlock methods and earn. Finally; I added special lore text to almost every single thing's description in the Labyrinth, if you're a lore nerd, there's a LOT here to begin piecing together, there's a story here, it's just not fed cleanly to you in a story arc directly. If you want the full picture of the lore, read those item descriptions! 😄

I've always been of the opinion that using voice-overs was not inherently / objectively bad, only their original usage in the Galaxy tutorial that people didn't like. So, I've been experimenting with them in ways that don't detract much from the content if you decide to turn them off (flavor dialog in the Labyrinth, encounter cues in LGTF). As long as you are constantly moving, the Minotaur will likely never catch up to you as he moves to a players position when he hunts, but doesn't dynamically follow them; He's most dangerous when his target is currently in the middle of something else and he shows up uninvited to complicate things. This will be most noticeable when a raid is clearing mobs to build Level Shifts and he appears while clearing a floor. Hint: From the starting point of the Endless Colonnade, use a Draught of Fog inspiration (or have somebody else in the zone use one, anybody using one anywhere will trigger it) and the path will become clear, but only briefly. Alternatively: Have somebody else run / clear the maze for you and recall to them. If it's the fog maze inside the Endless Colonnade, the only escape is using your recall power... That being said, I can include an escape door at the beginning, so people who aren't interested can re-randomize their location. I've received some feedback that it's a bit too common to end up there as well, so may reduce that chance slightly. The purpose of the Malevolent Fog pinatas are to increase the zone-wide level shift counter, as well as be a source of Reward Merits for a league that has people searching for them and using Incandescent Destiny to move the league to them for clears. Think akin to Giant Monster clearing during Halloween Leagues, where some people are searching the zone for Eochai / Jack-In-Irons. The Malevolent Fogs are a side-prize to strive for that adds Reward Merit income to the League's earning totals if hunted.

We're aware of some sort of crashing issue with the Minotaur's Hoof Stomp attack; I am looking into it. Source of the crash was an FX flag error in Hoof Stomp, should be fixed next build.

One click = petting. One death = feeding. Click Blarf enough times to be consumed and the badge should ding.

Very, very few limitations. Right now, there's just LGTF's final mission on Advanced Mode, and the mission inside Sister Psyche's mind in SSA1.4.

Team credit for Safegaurd Mission objectives was on a to-do list; I'll see about getting that done sooner rather than later.

You are most welcome! 🙂Thanks to everyone who's played my stuff! 😄 It's been real great seeing players engaging with the advanced content, I'm glad they're an experience people can find fun with and enjoy together.

Vandal and friends use a giant max/min donut radius to locate a suitable pre-existing spawndef point on the map that is far enough away the from the 'instigator' player (whoever triggered the phase transition) and then spawns the ambushes with a behavior to run to their instigator, which accounts for the delay between their trigger and them arriving. What this means, is that there is no pre-set locations where they spawn, and the exact spawn def the ambushes could change every run depending on where the team is positioned when the ambush trigger fires. I would assume the game would just pick the very first, closest spawn point that meets all the eligibility requirements, meaning you might be able to manipulate where he spawns, but that's just conjecture on my part, so it may not be as helpful.

Fixed both the suppression volumes in Kings Row and Brickstown, they were using the wrong alignment's AE setting so the suppression was not targeting heroes correctly. Will go out in a future patch. Thanks for the report!

Fixed this, her Pocket D contact was missing flags to exclude her from introductions. Will go out in a future patch. Thanks for the report!

Digging into some of these map bugs from the bottom-up, will use an emoji when I've fixed them. Pineapple = Fixed. Pepperoni = Was not fixed, either due to it not being actually being a map issue, not being something I can fix by myself, or not without a significant time investment that exceeds the scope of quickly getting as many of these done as possible.

Checked on this. Turns out there was a large number of details on Rikti_60_Layout_02 that were incorrectly grouped and were therefore not rendering. This will be fixed so all these details will be visible.

I just figured this one out, should be good for next Page; There were a handful of invisible map move markers for that door under the Founder's Safeguard map, that the original map artist must have lost when editing.

Becky now attaches to her owner as a command-able pet, and will auto-magically teleport to her owner if too far away. If her owner leaves the map, she'll attach/warp to the next oldest player on the map. This should make Becky 100% fail-proof next Page. When this goes out to test, give her a spin; In particular if you can verify that her fail-over tech works if her owner leaves the map; It was working for me, but we know how these things go.

I'll look into this; I'll move the glowie back onto the metal base of the globe instead of directly underneath and see if that improves things.

We're aware of this and looking into it. This one has been hard to pin down, there's a lot of costume pieces and weapons that do it, but it is not immediately apparent what the commonality is between them that's triggering the problem in the first place. This will involve some reverse engineering on why the check passes committing a costume, but fails loading it.

Figured this one out and fixed it; Should be good in an upcoming patch. Thanks! 💙

Thanks! Confirmed the sign texture is incorrect (Cygnus is in Galaxy City), and the correct texture does exist for Aquarius Medical Center; Will get that fixed.

This badge is bugged, an issue was identified when the script rolled onto the next mission; Will be fixed next patch. Thanks for the report; Should be good soon! 💙

If suggesting to a new player that a Blaster is a better pick than a Defender on teams for somebody who wants to be play Ranged Damage (which is an objective fact) is "forcing a particular plastyle" then there's not much room for discussion. That's not us changing the game, that's just literally how the game works. It's a rather odd take on the goal of trying to better passively educate players that certain ATs are better choices for specific team roles.

We're not, and many are looking at this the wrong way. Also worth noting, as it's something many people are getting wrong in this discussion: Your chosen playstyle is not the same thing as your AT's primary role on a team. Because the game allows players to run anti-meta builds, like a Defender who's specced into a taunt and fights only in melee, but that is choosing a playstyle. That does not make it that Defender's role on the team to tank enemy aggro. If I invite a Tanker to my team completely blind without looking at their powersets at all, what should I expect them to be contributing to my team? My answer would be that the expectation is that they are going to be the ones first into enemy groups and tanking their aggro alpha. If the Tanker instead sits at the back of the team using only ranged attacks and never taunting, they're choosing a playstyle that does not suit their Archetype, which is allowed, but it does not mean their Tanker is fulfilling the role of Ranged Damage. In-fact, by doing so they're contributing very little to their team, so even if it's technically allowed within the game, it's not behavior we are going to reward. It would be more productive if that Tanker who loves playing Ranged Damage instead was on a Blaster, as they'll contribute far more to that role while retaining the same playstyle. The distinction will hopefully lead players to play the ATs that are the strongest choices for the playstyle they enjoy, while also acknowledging the role they are expected to fulfill when on teams. This is the knowledge we're hoping to impart to new players with these more defined roles. The character creator even refers to this selection as 'Playstyle':

I'm gonna blame this one on the Rikti... I'll look into recovering that building, Striga has enough problems as it is. Thanks!

The new Vanguard compound was setup using vistrays so that if you're not currently inside of it, it doesn't render, so players doing Mothership Raids should not notice any performance impact. However, as always, if anyone notices anything suspect, do let us know!

Probably not, instanced zone maps are taken as copies from the original zone at the time of their creation, all zone functions stripped out, and then modified into mission maps. Adding the new sections to the instanced maps would essentially mean redoing them entirely from scratch. It's too much effort for what would change almost nothing for the missions on those maps. As for outdoor maps... The AE building shouldn't exist in those old outdoor maps because Rikti War Zone content was from Issue 10 and the Architect system wasn't added until Issue 14.

We've investigated this issue, which is a result of Blasters having access to 5+ possible weapons from sets and players only having 4 total weapon slots on their costume's data format, so this has now become a hard-coded problem requiring some involved adjustments to resolve. I can confirm it's on our radar, and we're looking into it, but this won't be fixed in time for Page 7 unfortunately, it's not possible to resolve with things setup as they are currently. This issue is due to a weapon slot overlap, it wasn't caused by any recent sheathed/holstered changes, just made more visible.