Faultline

@BlackSpectre No changes to how veteran levels work, from a player POV. It was just code cleanup.

No, the IO sets won't get anything extra. This is something where I overrode the powers team (who wanted to change the procs entirely) so you can blame it on me. The reason is simple: at the moment the changes to supremacy are just in testing, and even if they make it live, the powers team is not shy of reverting things every now and then. By only lowering the ATO numbers without changing them in any other way, it is easy to bring them back up to the original values if needed. If they get something else, then people who got the IOs because of the new thing will be rightfully ticked off if they are changed back. Yes, the Mastermind ATOs will feel pretty underwhelming now. That's fine. If you think they're a waste of a slot now, then congratulations, you now have an extra slot to put something more useful in.

None of the levels will require more experience, it's always a downward adjustment (the last two digits of the cumulative column in the wiki become 00, or 000 for levels >= 50). There's nothing too significant about the change; the experience table needed to be redone with numbers up to level 60 to fix an issue with the higher level critters (and veteran levels now directly use the experience table instead of a hardcoded value) so while rewriting it I rounded everything down to make it look nicer. The reason there's a patch note is just so people wouldn't be confused about a stealth change. Now you're confused about a documented change.

You don't need to keep Winter Essence at 0 to get Icebreaker; it just can never hit 100. Winter Essence at 100 causes Lord Winter to become invulnerable; if that ever happens, you won't get the badge.

They got missed when the entire event was rewritten for this year. Already fixed on Brainstorm. No ETA on live patch.

It doesn't work because the idiots in charge didn't understand why Kirk was chewing the scenery so much in that scene; it's not Shatner who is overacting, it's *Kirk*. Kirk knows that Spock is working on getting the Enterprise running in a few hours, but he needs Khan to think he's won, so he yells over the comms as is he's really angry and out of control -- because he's trying to sell it to *Khan*. Note how after they are off comms, Kirk is perfectly calm and talks to everyone casually. Shatner understood what was going on and played it well. *Kirk* is not a trained actor, so when he's trying to oversell how upset he is, he overacts. The Spock scream in ST:ID is just Spock himself being genuinely upset and screaming like an idiot, because the idiots in charge of the movie just know that the scream is iconic, but not *why*. It was an example of Kirk beating the "superior intellect" by playing with him.

Here you go. This is all the stuff that we expect will need more than a couple of weeks in beta for proper testing and feedback gathering.

You are making things harder on yourself. If the cooldown is over, the present will spawn on the first available spot. If you did a loop around the zone and you didn't see it, click one present and wait for it to respawn; if the cooldown is over, it WILL spawn as a Suspicious Gift. Clicking every present just means you have to check every spot again. Be aware that presents don't spawn if players are too close (200ft; it's always been that way). Camping a gift spot makes it not appear. The cooldown is on the same timer as the snow. If the present didn't spawn after your first loop and the snow state hasn't changed, don't bother doing another loop until the snow state changes, just go to a different zone. I will make some changes to the snow in the next patch to make it more obvious when a Suspicious Gift spawns. Running around repeatedly on the same zone is the worst way to try to get this badge. Explore different zones. Even on Excelsior there are often two presents simultaneously up in low activity zones. My plan if it turns out that there are not enough Suspicious Gift spawns, is to reset the timer if a character without the badge uses a Lump of Coal inspiration, giving them a use -- but so far, I am seeing plenty of presents available in all servers.

That's just the power that applies the snow effect to you. The next patch to live will allow you to delete the power by right clicking it from your powers window if you find the effect too distracting.

The snow is tied to the same hourly cycle, so you can use it as an indicator to know if the present has recently spawned. If you do one cycle around the zone and you don't see the present, you're better off trying a different zone; when the snow goes away, it's been 45 minutes since the last special present spawned; when the snow comes back, a special present has just spawned or will spawn shortly.

The bug was caused by a buffer overflow which was dependant on many factors, and 100% reproducible on your machine didn't mean 100% reproducible on everyone's. I could never get it to crash; Number Six only managed to get it to crash last night, and once he did so, he had a fix within the hour. The crash reports didn't really help with this particular crash because the game crashed when something tried to access the memory overwritten by the overflow, not when the overflow itself happened. Please do continue sending crash reports, but be aware that sometimes, it just takes time to find out what's going on. I had people send me their entire architect folder with examples of arcs that 100% crashed on their computer, and mine loaded every single one of them just fine.

The word is "we know this is happening, we thought it was fixed already, will keep trying to fix it". It's in the high priority bucket alongside the -1 level setting reportedly not working.

The hour cooldown is not after the Winter Lord is defeated, it's after the box spawns. There can be, and often are, multiple boxes in a zone.

Badges are not "flagged preatorian", so no. Badges have requirements, and some badges require that your character has some flags set, while other badges require that those flags aren't set. So any option that shows "all badges I haven't earned" will show badges you cannot earn, because there's no way for the system to check that you will never meet those requirements; only whether you meet them at this time. The specific flag being used in those badges is "PraetorianProgress", and it is a flag that can, and does, change.

Set Bonuses are the ones you get from slotting multiple enhancements of the same set. If the bonus comes from slotting a single enhancement, it's not a Set Bonus and not part of the change.

That is somewhat difficult because of the Praetorian badges, you would see badges your character can never earn. There's no clean way for the game to know the difference between a badge you haven't earned, and one you cannot earn.

This is news to me and I have no idea why this would be happening. The Incarnate critters were expanded to level 60. Further investigation needed.

This is an excellent post, thank you. Could you test again with today's patch, please?

That has been done for Task Forces, which are considered the highest priority for the change.

The intention is for them to have increased rewards, and Cobalt did expand the reward tables for critters up to 60, but it isn't working correctly right now; the rewards code is capping things at 54 and I haven't figured out exactly where yet. This is not considered a show stopper for live, because we want this patch out before we all take our break in December.

No, you just need to get to the core, which you can do by teleporting to a player already in there or by earning the history badge for the zone.

None of those parts require a raid. You can do repeatable missions that reward 10 or 15 Obols and aren't even that hard if you downgrade AVs to EBs. It took me less than an hour to unlock all the parts while solo. I'm not a fan of locking costume pieces either, but let's not overstate the difficulty here.

Level shifts are given by powers and they cannot be transferred to sidekicks because they don't actually affect the real combat level, you're still combat level 50. In order to fix that we would need to make the level shifts actually increase the player level to 51, 52 or 53 so the sidekicking code can correctly match it, and that change is hard to accomplish.

It's been running out of memory in Excelsior and Everlasting; the max memory will be increased on Tuesdays' patch.