BF1942 Battle Plan - No Client Mods

The Battlefield 1942 Website has details on what's to be included in the upcoming version 1.4 patch for DICE's World War II shooter. The update includes word that client-side mods are to be disabled in the future as part of their effort at eradicating cheating and exploits:
A note on cheating and exploits -- we've all seen how cheating can destroy the gameplay experience for everyone. EA and DICE take cheating seriously and we are taking an aggressive stance in preventing exploits which allow people to cheat. The biggest source of all BF cheats and exploits are client-side modifications. With the release of patch 1.4, we are disabling all client-side mods. Unfortunately, this means that the client side mods that aren't used for cheating will also be affected. DICE and EA have spent the past few months trying to engineer a solution which allows client-side mods to work while stopping the cheats. Ultimately it proved impossible to do so in such a way that prevented future client side mods from opening up new methods of cheating and exploitation. However, this doesn't mean that all mods are unusable. By making the mods into full server-side mods (Desert Combat for example), everyone can experience the cool factor that these mods offer.
View : : :
22.
 
Re: Let me try to explain this clearly....
Apr 19, 2003, 16:40
22.
Re: Let me try to explain this clearly.... Apr 19, 2003, 16:40
Apr 19, 2003, 16:40
 
I totally appreciate your condescending attitude, but I'm afraid it's you who doesn't understand. Of course, it's understandable since the update wasn't crystal clear.

According to EA's definition Desert Combat is not a client-side mod, DC is already, in its current state a "full server-side mod".

This is a bit of a weird nomenclature, I'd call DC a client/server mod, which are okay with the new patch. The patch only affects pure client mods, that is mods that are not mirrored on the server side. So custom skins, blood patches will be rendered impossible.
That's exactly what I thought when reading the news message, but Sarcasmo seemed so sure I searched around the BF1942 forums, and found a thread confirming this:
http://forums.bf42.com/showthread.php?threadid=24398
The thread includes posts by Desert Combat team members who have spoken to the developers.

Edit: Well it turns out I took so long to research and write my post that Sarcasmo found his own error. Apologies.
This comment was edited on Apr 19, 16:42.
Date
Subject
Author
1.
Apr 19, 2003Apr 19 2003
2.
Apr 19, 2003Apr 19 2003
3.
Apr 19, 2003Apr 19 2003
4.
Apr 19, 2003Apr 19 2003
5.
Apr 19, 2003Apr 19 2003
6.
Apr 19, 2003Apr 19 2003
7.
Apr 19, 2003Apr 19 2003
13.
Apr 19, 2003Apr 19 2003
8.
Apr 19, 2003Apr 19 2003
9.
Apr 19, 2003Apr 19 2003
14.
Apr 19, 2003Apr 19 2003
10.
Apr 19, 2003Apr 19 2003
26.
Apr 19, 2003Apr 19 2003
28.
Apr 19, 2003Apr 19 2003
12.
Apr 19, 2003Apr 19 2003
16.
Apr 19, 2003Apr 19 2003
17.
Apr 19, 2003Apr 19 2003
18.
Apr 19, 2003Apr 19 2003
 22.
Apr 19, 2003Apr 19 2003
    Re: Let me try to explain this clearly....
23.
Apr 19, 2003Apr 19 2003
24.
Apr 19, 2003Apr 19 2003
25.
Apr 19, 2003Apr 19 2003
15.
Apr 19, 2003Apr 19 2003
19.
Apr 19, 2003Apr 19 2003
20.
Apr 19, 2003Apr 19 2003
21.
Apr 19, 2003Apr 19 2003
29.
Apr 19, 2003Apr 19 2003
30.
Apr 19, 2003Apr 19 2003
31.
Apr 19, 2003Apr 19 2003
33.
Apr 19, 2003Apr 19 2003
34.
Apr 20, 2003Apr 20 2003
35.
Apr 20, 2003Apr 20 2003
36.
Apr 20, 2003Apr 20 2003
37.
Apr 20, 2003Apr 20 2003
      Dan
38.
Apr 20, 2003Apr 20 2003
       Re: Dan
39.
Apr 20, 2003Apr 20 2003
        Re: Dan
40.
Apr 20, 2003Apr 20 2003
         Re: Dan
41.
Apr 20, 2003Apr 20 2003
         Re: Dan
42.
Apr 20, 2003Apr 20 2003
          Re: Dan
43.
Apr 20, 2003Apr 20 2003
          Re: Dan
44.
Apr 20, 2003Apr 20 2003
           Re: Dan
32.
Apr 19, 2003Apr 19 2003
45.
Apr 20, 2003Apr 20 2003
46.
Apr 20, 2003Apr 20 2003
47.
Apr 21, 2003Apr 21 2003
48.
Apr 21, 2003Apr 21 2003
49.
Apr 21, 2003Apr 21 2003
50.
Apr 22, 2003Apr 22 2003
51.
Apr 22, 2003Apr 22 2003
52.
Apr 24, 2003Apr 24 2003
     Re: No subject
53.
Apr 24, 2003Apr 24 2003
54.
Apr 24, 2003Apr 24 2003