The Inquirer-Home

Call of Duty 2 community threatens strike, boycott

Shut servers for 24 hours, threat
Mon Nov 28 2005, 09:20
IF SOME questions don't get answered, most Call of Duty, Call of Duty United offensive and Call of Duty 2 servers will be shut down for 24 hours, users have threatened.

The Call of Duty gaming community appears to be united to carry on this strike. This could be the first massive online strike - boycott and is scheduled for December 17th.

It's the action of desperate chaps who claim they cannot get any kind of support from the game developer or publisher. Questions have been asked but the developer hasn't provide any answer, they claim. That's given rise to hurt feelings in the community, but the community wants to make them care.

The games developer and Activision as a publisher charged $49.99 or Euro from each and every Call of Duty 2 copy they sold. It's the kind of money game publishers are taking from the community for every single new game. Call of Duty 2 was no exception, with gamers waiting for a sequel for almost two years. But users claim some parts of the games were missing and now three weeks after, still didn't get any kind of answer.

The community reckons that the developer Infinity wards actually made Xbox 360 game and ported it back to PC. These are the questions gamers want answering:

1. When will you include an Anti-Cheat system for COD2?
2. When will you release your 1st patch for COD2?
3. What will it include?
4. What other plans have you for the support of the Call of Duty Games?
5. What will you do to ensure this situation does not arise again?

This is a huge slap for Nvidia's The Way it's Meant to be Played as the game is part of that programme and Call of Duty 2 is bundled with Nvidia 7800 GT cards. Perhaps Nvidia will twist some arms.

The community doesn't want to change entire game or to rush out a patch. Some fan sites are even suggesting people boycott games until they hear back from the publisher and developer. µ



Share this:

blog comments powered by Disqus
Subscribe to INQ newsletters

Sign up for INQbot – a weekly roundup of the best from the INQ

INQ Poll

Heartbleed bug discovered in OpenSSL

Have you reacted to Heartbleed?