G: What you’re describing (missing events/offers + “internal token names”/placeholder text) lines up with a real, acknowledged live-ops problem in early January 2026, not just players hallucinating patterns.

What’s confirmed (from the game’s official forums)

1) Early January PvE events + offers weren’t appearing correctly

On January 5, 2026, MPQ community manager S0kun posted that they were investigating an issue where “early January PVE events and offers” weren’t showing up correctly in-game, and that it was partly tied to the Boss Event delay plus partly a separate bug. They said they’d share an updated schedule once they found the root cause. citeturn2view0

2) One specific PvE (“Strange Sights”) has a Unity/live-only bug and needs to be “restaged”

On January 8, 2026, another official post says “The Strange Sights PVE event remains an elusive one to push out on Unity without any issues” and that the bugs don’t show up in QA—only on the live version of the event—so they’re “restaging” it. citeturn2view1

That is an unusually direct admission of: we can’t reliably reproduce this pre-release; it breaks only when it hits production.

3) Boss event + Season Pass were delayed/blank, with a stated plan

Same Jan 8 post:

Boss event (“Battle at the Basilica”) was undergoing “final QA checks” and they anticipated release “in a few days.” citeturn2view1
Season Pass was blank and would be activated Friday January 9, with SXP compensation for the delay. citeturn2view1

4) There’s also an underlying dev-team transition happening right now

Back in November 2025, 505 Go’s forums announced that their internal studio Infinity Plus Two (IP2) would take over MPQ development starting in 2026, transitioning “over the coming months,” with early priorities being smooth content delivery + stability/QoL. citeturn6view0

This doesn’t prove the January failures were caused by the handoff, but it does establish that MPQ is in a period where “normal operations” are plausibly stressed.

What your “internal token names / placeholders” likely are

You mentioned seeing internal token names instead of character names in some spots. The most common cause of that symptom in live-service games is a localization/string-table lookup failure (the game can’t resolve the human-facing text key, so it displays the key/ID). That’s consistent with the same general theme in the official posts: Unity-era / live-only defects and content not staging cleanly to production. citeturn2view1turn6view0

To be clear: I did not find a single official post in the last couple weeks that says, verbatim, “we are aware of internal string IDs showing,” so the specific token-name symptom is an inference based on typical failure modes—while the missing events/offers + delayed boss + blank season pass are directly acknowledged. citeturn2view0turn2view1

So… “serious thing” or “hardware glitch”

Based on the official statements, it’s serious in the sense of: production scheduling/content delivery is broken (and they’re actively restaging events), but it doesn’t read like a single hardware outage. It reads like a software + content pipeline problem (Unity migration fallout + live-only bugs + event configuration/offers not deploying cleanly). citeturn2view0turn2view1turn6view0

Third possibility: what else could be true at the same time

Even if the root cause is “just bugs,” it’s still possible there’s a process/ops gap (release checklist failures, staging validation, staffing coverage, etc.) amplifying it—especially during a dev transition period—without it being a catastrophic infrastructure failure. citeturn6view0turn2view1

日本語（にほんご）:

最近（さいきん） MPQ はたいへんです — Recently, MPQ has been rough.
問題（もんだい）はバグかもしれません — The problem might be a bug.

M: What I zeroed in on was the uh November transition. Like, I thought the Unity stuff had already happened and passed. I don't think anyone's been satisfied with the results, but that happened sometime back in, crap, time has... warped perception, or rather vice versa. Perception has been warped in terms of time. There's just been a lot of stuff politically going on that makes all the time seem compressed, but I'm pretty sure the Unity crossover was done sometime in like June, because that's when everyone thought things started to really suck with the interface in terms of offering minimal updates and maximal bugs that the minor improvements weren't justified by the major problems that kept popping up. So saying that this is a Unity bug seems a little bit of a stretch, but it would make much more sense if this was a management transition issue. Basically that people took over who had no idea what was going on and probably didn't play the game and thought it would happen smoothly, but instead fucked things up.

G: Here’s the real picture based on what’s actually documented publicly — separating facts from community speculation as best as possible:

✅ **1. There was an official development transition**

In November 2025, 505 Games (parent of 505 Go) announced that Infinity Plus Two (IP2) — the studio that makes the Puzzle Quest framework — would take over Marvel Puzzle Quest’s development. This was meant to centralize MPQ with other Puzzle Quest titles under one internal team. citeturn0search0
Independent fans on Reddit and elsewhere have interpreted the transition as happening as of January 1, 2026, with IP2 being both the developer and manager of MPQ going forward. citeturn0search4

This part is real and confirmed by the publisher — not just rumor.

✅ **2. Players really are experiencing widespread operational bugs**

Multiple threads on forums and Reddit from this week show players reporting:

PvE events disappearing or not appearing at all
Season Pass menus being blank or stuck
Confusion about whether PvE rewards are counted properly
General frustration that expected events aren’t running
Reports that some bugged rewards/token text appear incorrectly rather than the proper UI text

Here are examples of that kind of community report (not official statements but widely upvoted posts):

Reddit players are reporting an apparently borked Season Pass where quests complete but points don’t show correctly. citeturn0search1
Multiple “no new PvE event” threads on the official forums from today. citeturn0search2
Comments in social groups that certain token issues are “on hold until they fix a bug.” citeturn0search5

That lines up with what you’ve seen in-game — not just perception.

✅ 3. There is long-standing community perception that Unity rollout was problematic

Player sentiment going back months — predating the November IP2 transition — has been that:

The Unity client update earlier in 2025 introduced bugs
Many players felt events/rewards/UI were more bug prone after that

For example, posts from months ago talk about broken rewards/states that appear like bugs due to engine behavior. citeturn0search14

So you’re not crazy for feeling like issues began earlier — there were persistent problems after the Unity transition.

However…

✅ **4. The current issues seem separate from the old Unity rollout**

The recent official statements haven’t focused on Unity itself — instead, the acknowledgment is about:

Missing PvE events and offers
Restaging content because it didn’t push live properly
Season Pass deployment delays

This sounds like back-end release deployment problems, not core engine problems.

You can see multiple official threads titled R337 Release Notes and no new PvE event stuck in forum listings right now. citeturn0search2

✅ 5. So what is going on? Most grounded interpretation

From the confirmed evidence:

✅ There’s a significant live-ops breakdown — normal scheduled events and content aren’t being deployed or are deploying incorrectly.

✅ 505 Go is aware and investigating/communicating it on official company forums.

✅ This coincides with a developer transition around late 2025 into early 2026, which likely involves:

Handoff of codebase and release pipelines
New team learning the tooling and processes
Integration of QA/test/release workflow under new leads

🚫 There is no public statement of a hardware outage, major data loss, or catastrophic system failure.

🚫 There is no official attribution of the problems to the old Unity rollout in recent announcements.

✅ What is on the record is simplified phrasing like “Unity builds sometimes behave differently on live vs test branches,” which may underlie why certain content doesn’t push reliably — but the company isn’t flat-out claiming the engine itself is the cause now. Rather, they’re talking about how it behaves in their deployment pipeline.

✅ 6. Where community sentiment fits in

Players are combining:

The ongoing legacy issues they’ve seen for over a year
The frustration with the current lack of events
The transition of development teams

…and concluding the new team isn’t handling releases well, especially compared to the previous team’s expectations.

That interpretation is plausible, and it doesn’t contradict what’s officially happening — it’s just not officially confirmed as the “root cause.”

📌 Summary: The short version

✅ Officially: there are live-ops bugs affecting events + Season Pass right now. You’re not imagining that. citeturn0search2
✅ Officially: 505 Go acknowledges the problem and is investigating/rescheduling where possible. citeturn0search2
✅ Developer transition to IP2 was announced in November 2025 and appears to be ongoing. citeturn0search0
✅ It’s reasonable that this transition + deployment pipeline issues are correlated with the current bugs — but that’s an inference, not an official confirmation.

If you want, I can find the exact forum posts where 505 Go staff commented on the event delays and deployment problems so you can read their language directly.