FarmBoy
15th Sep 2003, 12:31 AM
I've been using the excellent WoRM2k3 mutator to test out some of the really cool custom weapons that have been released recently. So far, I've been doing this in off-line mode, strictly against bots. However, I'm the admin of a couple UT2003 servers, including a LAN server at work. For my LAN server at work, we want to be able to switch the default weapons to a custom weapon config (a mix of Remote Strike weapons, frnz Sniper Rifle, 9mm SMG, and G36 Assault Rifle). Basically, I'm putting together a custom real-world weapons pack with the weapons that I currently think play best. To that end, I want to use WoRM2k3 to switch all the default weapons to these weapons. I want to use WoRM2k3 because I've found it to be the best weapon switcher, including the fantastic support for placing a weapon in a particular weapon slot and having it stick there on the weapon bar. Kudos to the author for getting this to work, since the other weapon replacer mutator I tried doesn't do this.
Now, here's the crux of the issue. How do I get this to work properly on the dedicated server and on the clients? I'm a very experienced server admin and thought configuring it via the GUI on my gaming client, uploading the ini file and all pertinent files to the server, registering the mutator in the MD5 db, and adding it in to the mutators list on the server, would do the trick. I get all the weapons replaced properly on the maps, but the weapons don't properly go into each configured weapon slot on the clients. That feature (as mentioned above) is one of the main reasons I went with WoRM2k3, and I want to get it to work properly in a server/client scenario. Any ideas on what might be wrong or is this something that needs a little tweaking in the mutator code to work properly?
Now, here's the crux of the issue. How do I get this to work properly on the dedicated server and on the clients? I'm a very experienced server admin and thought configuring it via the GUI on my gaming client, uploading the ini file and all pertinent files to the server, registering the mutator in the MD5 db, and adding it in to the mutators list on the server, would do the trick. I get all the weapons replaced properly on the maps, but the weapons don't properly go into each configured weapon slot on the clients. That feature (as mentioned above) is one of the main reasons I went with WoRM2k3, and I want to get it to work properly in a server/client scenario. Any ideas on what might be wrong or is this something that needs a little tweaking in the mutator code to work properly?