Unofficial AppImage of Open CoD:UO, reconstructed source for the Call of Duty: United Offensive multiplayer client and dedicated server. Client is launched by default. Rename the binary or make a symlink named opencoduo-server to launch the dedicated server.
The icon is upstream's own assets/coduomp-icon-master.png, resized to 512x512.
AppImage made using quick-sharun, which makes it extremely easy to turn any binary into a portable package reliably without using containers or similar tricks.
This AppImage bundles everything and it should work on any Linux distro, including old and musl-based ones.
This AppImage doesn't require FUSE to run at all, thanks to the uruntime.
This AppImage is also supplied with a self-updater by default, so any updates to this application won't be missed, you will be prompted for permission to check for updates and if agreed you will then be notified when a new update is available.
Self-updater is disabled by default if AppImage managers like am, soar or dbin exist, which manage AppImage updates.
The client is the default, so it starts with no arguments or by double clicking:
./Open_CoD_UO-*-anylinux-x86_64.AppImageThe server is selected by the name the AppImage is invoked as. Make a symlink named opencoduo-server pointing at the AppImage and run that instead:
ln -s Open_CoD_UO-*-anylinux-x86_64.AppImage opencoduo-server
./opencoduo-server +set dedicated 2 +exec server.cfgThe dedicated server entry is also bundled, at share/applications/opencoduo-server.desktop inside the AppDir, together with its icon in share/icons/hicolor/512x512/apps/. Extract the AppDir if you want to install it into your menu; it expects an opencoduo-server symlink to exist.
This AppImage contains the engine binaries and their modules only. Call of Duty: United Offensive must already be installed, because both binaries read your existing game data in place and do not copy it.
On launch both binaries look for a retail root containing both main/pak0.pk3 and uo/pakuo00.pk3:
- the
CODUOMP_DATA_PATHenvironment variable, if set; - the working directory, so running the AppImage from the game directory works;
- a previously saved path;
- Steam app 2640, across all configured Steam libraries.
If you pass +set fs_cdpath yourself, that is used as-is.
If nothing is found, set the path explicitly:
CODUOMP_DATA_PATH="$HOME/.steam/steam/steamapps/common/Call of Duty United Offensive" \
./Open_CoD_UO-x86_64.AppImageEach binary keeps its own saved path, so they are configured independently: the client writes ~/.config/opencoduo/data-path and the server writes ~/.config/coduo_lnxded/data-path. CODUOMP_DATA_PATH is the same variable for both, since it is the same game data.
Client configuration, logs, downloads and screenshots live in ~/.local/share/opencoduo (or $XDG_DATA_HOME/opencoduo). Server configuration, logs and screenshots live in ~/.callofduty. Neither is ever written inside the AppImage.
AppImage made using quick-sharun, which makes it extremely easy to turn any binary into a portable package reliably without using containers or similar tricks.
This AppImage bundles everything and it should work on any Linux distro, including old and musl-based ones.
This AppImage doesn't require FUSE to run at all, thanks to the uruntime.
This AppImage is also supplied with a self-updater by default, so any updates to this application won't be missed, you will be prompted for permission to check for updates and if agreed you will then be notified when a new update is available.
Self-updater is disabled by default if AppImage managers like am, soar or dbin exist, which manage AppImage updates.
raison d'être
More at: AnyLinux-AppImages