ChiYuri.6943

I know that you guys are saying to "blame Apple", but the issue is with ArenaNet. They've been providing a service to Mac users that have machines using Intel processors. Now that Apple has moved forward with their own proprietary ARM processors, it is harder to make a launcher for two different types of machines. Yes, they are using the same MacOS. However, the difference in the processors can impact how the game is programmed and functions. I will say again, that I understand ANet not wanting to program and make the game work for the new ARM processor machines. However, they've happily provided service for those of us with Intel Macs for years. I believe they should continue to do so until the machines are obsolete, which would be years from now. They could just put a disclaimer that the launcher may not function with ARM processor models. Instead, they are abandoning Mac altogether without any consideration to those of us using those Intel Macs (which Apple was producing until only just recently).

Actually, VirualBox doesn't work on the current MacOS if you're up to date on Big Sur. It only worked until Catalina. Same for Wine. The only option I've seen so far is boot camp and dual boot your system to also run Windows 10.

I think that this is completely awful. I literally bought my Intel Macbook Pro last year. Before purchase, I checked to make sure that GW2 would still run on my Mac. For them to stop support and abandon an entire user base is ridiculous. I understand that they don't want to try and code for the new ARM processors, but what about the users who still have the Intel Macs? We're just hosed? I've been playing Guild Wars since around 2005 and was a tester for the 2nd one and have been playing ever since. Long term players left to rot... just because of the system we choose to use. I have to say that I'm completely furious at this decision.

It has been down for about 20 minutes and I only just now was able to log in to the forums and the game client. I also had the"the game client was unable to connect to the login server" error message.