Might develop a patch for the Barb compass range Options

[ScrapyardBob]

This goes back to my work from Oct 2004 on the compass range issue in the initial release of CoD:UO:

http://www.iwnation.com/Forums/index.php?showtopic=10222

The default value for CoD:UO still seems to be 1024 units for the compass range. You can check this in-game by opening the console and typing ([TAB] means to hit the tab key):

/cg_hud[TAB]

You'll notice that cg_hudCompassMaxRange indicates the radius of your compass. It's read-only so you can only change it by applying server-side mods.

One of the fun things is that if the gametype or map that you're playing does not specifically set the compass_range variable in its GSC files, it will inherit it from the previously played map. This is why some of us noticed that sometimes Ponyri had a good compass while other times the compass was messed up. (It all depended on what map we played previously.)

More in a bit...

[ScrapyardBob]

Note that these PK3s are designed for server-side use. Since they have the "_svr_" within their filenames, they do not get downloaded to client-side. The server admins would have to add these to the Barb/Smolensk servers. Putting them on a client PC does nothing.

As a bonus (with server-side mods), it's easy enough to change the settings in the PK3, and then upload it to the server during a restart to get new compass settings to take effect. (No worries about clients having outdated versions.)

Here is the compass fix for Smolensk. I went with a larger scale for BAS compared to the Barbarossa map.

BAS - 6000
CNQ - 3000
CTF - 4500