Best Of

The first 2 Idol champs look lame asf imo, so I had no interest in them what so ever… especially because they’re MCOC original characters and not from real marvel characters.



However… this XL transformer looking MFer looks cool asf. He also has the type of animations that I love… which is throwing hands and haymakers! 🥊🥊 These Idol champs went 0-100 real quick 💯 This champ looks fire 🔥 Good work whoever designed this guys aesthetically (idk how good the kit is yet, we’ll see).

This dude look ugly asf. Lumatrix has unmatched aura. Forgot the name of the first dude but he looks horrible as well.

Technically the first is a female, based on her voice, but in general, Eidols are genderless

Bro just making stuff up now.

Is the team radio silent right now? There have been some very good and relevant suggestions and discussions in forums recently and no communication. There’s also still unaddressed bugs. Here’s an overview from last 2 weeks to this week:

Unaddressed:
- If you didn’t wait to claim the twitch drops until after the event started, you didn’t get the points
- Still no cumulative comp the team was “discussing”
- No news on Titania (wasted r3/r4s with the AI). Still whiffing hits on SP1 as well.
- AI is probably the worst it’s ever been (at least I can intercept now) by holding specials until debuffs fall off, etc. It’s almost as if they react to what’s in their kit/counters and it’s learning. But it should never be to the point of unregistered hits landing and then after the second one AI throws a special to the face…
- Lack of mysterium for first two weeks of crossover
- QOL request pertaining battle groups (they seem to be just suggestions at the moment)

Not asking for all the answers, but some insight/acknowledgement from the team would be nice. Even just a blanket statement saying “we hear you as a player base”.

• If you didn’t wait to claim the twitch drops until after the event started, you didn’t get the points
  

This was addressed. We will be comping the points.

• No news on Titania (wasted r3/r4s with the AI). Still whiffing hits on SP1 as well.
  

Wasted is a very, very, very strong word here.
Her Special 1 is still whiffing, I'll poke on that one, but in general there are many cases resulting from 60 FPS where this is happening, and an overall fix is being worked on, this has been on Trello and addressed many times.

• The AI bit
  

I don't exactly understand what you're saying on this one, in any case, the AI is not "learning."

• Lack of mysterium for first two weeks of crossover
  

Mysterium has been addressed multiple times. It wasn't around for 1 week in the build, and the quantities were increased in the latter weeks. The discontent for the Mysterium shift has been passed along to the team.

• QOL request pertaining battle groups
  

I will also need specific examples here if you want something addressed.

The "wasted" part is from intimidate working as a taunt, not from whiffing 1 hit of her sp1.

Her Intimidate is not "working as a taunt."

This has been talked about countless times on the forums at this point - Intimidate is not a Special Lock.
It decreases the chance for the Opponent to use a Special, but it isn't guaranteed - and the potency of this chance does not stack with multiple Debuffs.

Try chaining heavy in the corner with Champions who don't have Intimidate, and then do so with Titania - I guarantee you, Titania will prevent it significantly more times than a Champion without the debuff.

Titania, above all other Intimidate users, has added safety built into her kit with her Unstoppable and Indestructible, where if the Opponent uses a Special, you're pretty much in the clear.

From a player POV, I recommend going for a 4 hit combo after SP3 before going for a heavy, as I anecdotally find it has a strong chance to get the Defender to turtle up for the incoming Heavy.

Big post incoming

Let's address everyone's points here. It's 2am, so forgive any slight errors.

Mysterium

It was stated that Mysterium would be absent from the build in the first week of the month, yet the overall amount of Mysterium would remain the same throughout the month.
The feedback is heard that you don't like the lack of Mysterium during the first week of the month - that has been passed onto the team a few times now.

Intimidate

Intimidate reduces the Opponents chance of throwing a Special by 30%.
The additional potency listed is for block penetration - if multiple stacks exits, the block penetration increases.
Intimidate simply is not a Special Lock - that effect exists and is different from Intimidate.
If we ever do a Tech version of Titania 2099, there's a solid chance she'd have a Special Lock instead of Falter & Intimidate (no, this is not a WOW LEAKS moment).

I don't understand why multiple people are referencing her Deep Dive.
The Deep Dive states "take advantage of her Intimidate to KO the Opponent," and that's about it, while showcasing her utilizing her heavy attacks after her Special 3 with an appropriate amount of Power on the Opponent.

Silk Lock Knock-ons

This is absolutely a valid concern and something I brought up internally.
At this time, the team feels the changes made to prevent Silk (and others) from breaking the game are too important to revert, even if it's impacting Titania if she happens to push the Opponent red. As an avid Titania user, I fully understand the impact when closing out a fight and you need to continue using your Heavy after your Haymakers have come and gone.
I can poke at this again, but I would recommend using her Special 3 when the Opponent isn't at 3 bars of power.

Further AI Concerns

I understand the AI can be frustrating at times - it can be frustrating often. Don't forget, I'm a very high level player as well and run into all the same AI, I believe the kids call it "clown fiesta moments" that you all do. "Fixing the AI" is a very touchy subject, and as outlined in our previous AI Dev Diary, there are lots of talented people working behind the scenes to try and make this as amazing an experience as possible. That reminds me, we need to get a follow up to that Dev Diary out soon. All that being said, the AI is not "learning" or waiting for debuffs to fall off before using Specials. I understand why it could feel that way, and I've often found myself saying "oh, come on now" when it happens to me. Think about how many fights you do in MCOC per day; if you're on the forums, you probably play a lot. The times when the AI feels bad are, unfortunately, going to be more memorable to you than the times things go smoothly and as expected.

QOL Requests

These requests are larger than you might imagine. Unfortunately, there isn't just a "lock players to the Battlegroup" button we could press to make that happen overnight. There are additional knock-ons to consider as well. What happens if, for some reason, a player needs to join a different Battlegroup due to backup concerns?
Unlikely, I know - but it's something that needs to be considered if that imaginary button did exist.
Fwiw, I understand the request and I agree it would be better if it operated that way.

Conclusion

If you think you're being ignored, or we aren't reading what you're saying - that's incorrect.
Again, it's 2am, and instead of winding down for bed I'm sitting at my desk trying my best to address everyone's concerns and make sure they know they're heard.

We aren't always going to be able to address the same questions or topics in multiple threads when multiple exist.
The forums are huge, and things get lost easily. I think a solution for that could be combining threads more often, but regardless, the point here is that I'm actively scanning the forums all day, all of your concerns are always heard, and passed along where they need to be.

All of THAT being said, goodnight, sleep tight, don't let the bed bugs bite.

Thanks for the write up ... One thing i also want to point out is that there are other persistent or reoccurring bugs that are was resolved for a couple of weeks but have since returned..
One example is the Kingpin on the AW mutant showcase map. Degen in the node is applying to the attacker again after this was fixed.

I'm suspecting one of the bug fixes mid month brought this back as the code for the degen fix was not tracked into the code push and reverted that segment back.

Can you please look into this again? thanks.

This is happening recently?