The freezing seems to have gotten worse lately. I'm on iOS and used to happen once or twice a week. It now happens 3 - 4 times during a twenty minute session. Not sure what might have changed but it definitely has taken backward steps.

What's odd is that it just started in the past several days. No real issues since August at all until the past couple PVEs. Same phone, etc. I wonder if iOS 26.2 update is the culprit?

PS, my iPhones are running iOS 17.x.

Both are also affected by this issue, so it's not an iOS 26.x thing.

I powered off my iPhone and turned back on. Game hasn’t froze today, but was freezing every other mode before

@LavaManLee said:
So odd. Unity really f'ed up so much stuff and then they dropped the ball and ran. Or dropped the ball and were forced out. Or were forced out and then dropped the ball. We will never know the true story.

I assume they got fired because they messed up the rebuild.

I've actually been through a lot of these. Any time a new developer takes over any project, no matter how well it was done, they immediately start agitating to rebuild it from scratch. You'll hear stuff like "how did this ever work?" or "what could they have been thinking?"

This is because developers are good at writing code and generally terrible at reading code. The answer to "let me start over" is ALWAYS no. Go back and figure it out. It's fine, it works, we're not throwing it away.

In this case, BCS did the same thing everyone does, but somehow convinced someone higher up that it was the right thing to do. At that point the whole thing was doomed -- there is no universe where a total rewrite of something this big and this old succeeds, for any definition of "success."

They went way over time and (probably) way over budget, they pushed out something broken that was half done because they were out of time, and then scrambled to fix it. After 6 months of this the higher ups got sick of them and fired them, because none of the stuff they promised actually got delivered.

@Zarqa said:

@entrailbucket said:

@LavaManLee said:
So odd. Unity really f'ed up so much stuff and then they dropped the ball and ran. Or dropped the ball and were forced out. Or were forced out and then dropped the ball. We will never know the true story.

I assume they got fired because they messed up the rebuild.

I've actually been through a lot of these. Any time a new developer takes over any project, no matter how well it was done, they immediately start agitating to rebuild it from scratch. You'll hear stuff like "how did this ever work?" or "what could they have been thinking?"

This is because developers are good at writing code and generally terrible at reading code. The answer to "let me start over" is ALWAYS no. Go back and figure it out. It's fine, it works, we're not throwing it away.

In this case, BCS did the same thing everyone does, but somehow convinced someone higher up that it was the right thing to do. At that point the whole thing was doomed -- there is no universe where a total rewrite of something this big and this old succeeds, for any definition of "success."

They went way over time and (probably) way over budget, they pushed out something broken that was half done because they were out of time, and then scrambled to fix it. After 6 months of this the higher ups got sick of them and fired them, because none of the stuff they promised actually got delivered.

To the best of my and at least many other’s knowledge, they didn’t rewrite the code. I thought it was generally agreed upon that they copied/translated the original code into Unity rather than rewrite it. This is evidenced by some old artifacts like FB friends rewards still popping up during PvE for example.

It could very well be we mean the same thing (I am not an engineer), but I think you’re the only one here who has consistently said they did rewrite the code. I don’t think BCS started over.

Could you clarify what you mean?

This is all based on guesswork, btw, but it's informed guesswork -- I've been doing this stuff for 25 years. Nobody knows exactly what happened and they're never going to tell us, so guesswork is the best we'll ever do.

"Translating" or "copying" code is not really a thing.

If Unity was capable of running a copy of the old code as it was, there is no "rebuild." You drag and drop the old stuff into Unity and it just goes. Since we know they worked on it for a really long time, this wasn't that.

Translating code, like like by line from one language or platform into something else, is theoretically possible but insane. It'd take forever and the end product probably wouldn't even run. I would classify that as a "rewrite" anyway -- you are literally rewriting the program line by line.

Most likely what they did was something more like an interpretation -- reimplement all the lower level functions/methods/whatever one by one in the new platform, hopefully also taking advantage of some stuff that the new platform gives you for free. This is ALSO a rewrite, because even if you're just doing exactly the same stuff you were doing before, you still had to rewrite everything to work in the new platform.

@entrailbucket said:
Think about this as if it were a novel, and we want to translate the novel from English to Spanish.

Just copying the English text and calling it Spanish is unlikely. Maybe some Spanish speakers understand English, though, so we could have them read the book in English! That's the easiest, but it requires a very specific audience.

Ok, so what if we just take every single word and replace the English word with the Spanish translation? You'll probably get something that a Spanish speaker could understand (mostly!) but things like idioms are going to be very messed up. You may screw up major plot points this way, and some parts may be unintelligible. It would also take forever! You've got to look up every single word!

What you'd really want to do is translate the book sentence by sentence, or paragraph by paragraph, using native Spanish phrases and idioms where appropriate, and what you're doing there is essentially rewriting the book from scratch.

(And in general, going from whatever MPQ was in 2013 to Unity is not as simple as translating English to Spanish. Especially with something as old and weird as MPQ, it'd be more like translating Ancient Egyptian hieroglyphics to modern Spanish).

Or, you use an automated online translation tool to change it from English into Spanish, then only check that the page numbers and chapter order all make sense, and publish it. I think that is more aligned with what I was talking about.

Appreciate your explanation though! And I agree that we might never know.