{"id":1726,"date":"2026-04-17T14:04:59","date_gmt":"2026-04-17T13:04:59","guid":{"rendered":"https:\/\/grimms3dworlds.ddns.net\/?page_id=1726"},"modified":"2026-04-17T14:04:59","modified_gmt":"2026-04-17T13:04:59","slug":"1726-2","status":"publish","type":"page","link":"https:\/\/grimms3dworlds.ddns.net\/index.php\/1726-2\/","title":{"rendered":""},"content":{"rendered":"\n
\n\n

\n Call of Duty 2 \u2013 Client & Server Side Files Explained\n <\/h1>\n\n

\n In Call of Duty 2 modding, understanding which files belong on the client<\/strong> (players), the server<\/strong>, or both<\/strong> is essential. \n Mods are packaged in .iwd<\/strong> files (renamed ZIP archives). Files that must be on both sides must be identical<\/strong> (byte-for-byte match). \n Any difference causes “iwd\/sum name mismatch” or purity errors when sv_pure 1<\/code> is enabled.\n <\/p>\n\n

\n Key Rule:<\/strong> Any file listed as Both<\/strong> must be exactly the same on the server and all connecting clients. \n Even a single byte difference will prevent players from joining.\n <\/p>\n\n

\n File Types Overview\n <\/h2>\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
File Type \/ Folder<\/th>\n Extension<\/th>\n Primary Side<\/th>\n Description<\/th>\n <\/tr>\n <\/thead>\n
Images<\/td>\n .iwi<\/td>\n Client<\/td>\n Textures, skins, HUD icons, and menu graphics.<\/td>\n <\/tr>\n
Sounds<\/td>\n .wav, .mp3<\/td>\n Client<\/td>\n Actual audio data for weapons, voice lines, and ambient sounds.<\/td>\n <\/tr>\n
Models<\/td>\n .xmodel<\/td>\n Client<\/td>\n 3D meshes for players, weapons, and map objects.<\/td>\n <\/tr>\n
Animations<\/td>\n .xanim<\/td>\n Client<\/td>\n Movement and animation data for models and weapons.<\/td>\n <\/tr>\n
Effects<\/td>\n .efx<\/td>\n Client<\/td>\n Particle effects for smoke, fire, explosions, etc.<\/td>\n <\/tr>\n
Sound Aliases<\/td>\n .csv<\/td>\n Both<\/td>\n Links sound names used in scripts to actual audio files (soundaliases folder).<\/td>\n <\/tr>\n
Scripts<\/td>\n .gsc, .csc<\/td>\n Server (.gsc)
Client (.csc)<\/td>\n 		.gsc = server-side game logic and rules.
.csc = client-side scripts (visual effects, UI, etc.).<\/td>\n <\/tr>\n
Weapon Stats<\/td>\n (no extension)<\/td>\n Both<\/td>\n Damage, recoil, clip size, etc. Located in weapons\/mp\/<\/code>.<\/td>\n <\/tr>\n
Menus<\/td>\n .menu<\/td>\n Client<\/td>\n In-game UI layout and menu design.<\/td>\n <\/tr>\n
Materials<\/td>\n (no extension)<\/td>\n Client<\/td>\n Shader instructions (how textures reflect light, scroll, etc.).<\/td>\n <\/tr>\n
String Tables<\/td>\n .csv<\/td>\n Both<\/td>\n Text used for rankings, weapon names, UI labels, etc.<\/td>\n <\/tr>\n <\/tbody>\n <\/table>\n\n

\n Important Caveats & Best Practices\n <\/h2>\n\n
    \n
  • Both-side files must match exactly<\/strong> \u2014 Sound aliases, weapon stats, and string tables are the most common causes of mismatch errors.<\/li>\n
  • .gsc vs .csc<\/strong> \u2014 .gsc files run on the server (game logic). .csc files are client-side only and are used for visual\/effects scripting.<\/li>\n
  • Pure server logic can stay outside of .iwd files in the mods\/yourmod\/<\/code> folder on the server \u2014 these files are never sent to clients.<\/li>\n <\/ul>\n\n

    \n Using \u201csvr\u201d in IWD Filenames (Server-Side Only)\n <\/h2>\n\n

    \n To keep client download sizes small and avoid sending unnecessary files, place server-only content in IWD files prefixed with svr<\/strong>.\n <\/p>\n\n

    \n Example: svr_mymod_logic.iwd<\/code>\n <\/p>\n\n

    \n Benefit:<\/strong> Clients will not<\/strong> download IWDs that begin with svr<\/code>. This is perfect for pure server scripts, configs, or internal data.\n <\/p>\n\n

    \n Recommended approach:<\/strong>\n <\/p>\n\n

      \n
    • Client-visible assets (images, sounds, models, menus, etc.) \u2192 normal IWDs (often prefixed with z_<\/code> to override stock files).<\/li>\n
    • Server-only files \u2192 svr_*.iwd<\/code> or leave them extracted directly in the mod folder on the server.<\/li>\n
    • Always test with sv_pure 1<\/code> to catch any mismatches early.<\/li>\n <\/ul>\n\n

      \n This method keeps your mod fast to download for players while giving you full control on the server side.\n <\/p>\n\n

      \n CoD2 Modding Guide \u2022 Client vs Server Files \u2022 Verified April 2026\n <\/p>\n\n<\/div>\n","protected":false},"excerpt":{"rendered":"

      Call of Duty 2 \u2013 Client & Server Side Files Explained In Call of Duty 2 modding, understanding which files belong on the client (players), the server, or both is essential. Mods are packaged in .iwd files (renamed ZIP archives). Files that must be on both sides must be identical (byte-for-byte match). Any difference causes […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-1726","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/grimms3dworlds.ddns.net\/index.php\/wp-json\/wp\/v2\/pages\/1726","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/grimms3dworlds.ddns.net\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grimms3dworlds.ddns.net\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grimms3dworlds.ddns.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/grimms3dworlds.ddns.net\/index.php\/wp-json\/wp\/v2\/comments?post=1726"}],"version-history":[{"count":3,"href":"https:\/\/grimms3dworlds.ddns.net\/index.php\/wp-json\/wp\/v2\/pages\/1726\/revisions"}],"predecessor-version":[{"id":1730,"href":"https:\/\/grimms3dworlds.ddns.net\/index.php\/wp-json\/wp\/v2\/pages\/1726\/revisions\/1730"}],"wp:attachment":[{"href":"https:\/\/grimms3dworlds.ddns.net\/index.php\/wp-json\/wp\/v2\/media?parent=1726"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}