Manual: Setup/Update

From OpenMPT Wiki
Jump to: navigation, search
Update tab of the settings dialog

OpenMPT is being developed constantly and new versions are released every few months. Thus, if you are using OpenMPT on a computer that is connected to the internet, you might want it to check for new versions automatically. If an update is found, it is never installed automatically, so you can decide on your own if you want to upgrade or not.

Check for Updates[edit]

Choose an update interval that suits your taste from this list. It is recommended to check for updates weekly, but if you are running OpenMPT on a machine without internet access, you can completely disabled automatic update checks here. In that case, you will have to look out for new updates by yourself. ;-)

Privacy Settings[edit]

In this section, you can decide whether a unique (but anonymous) ID should be sent with every update check or not. The ID is merely used to get rough statistics about the number of people that make use of this feature and the distribution of the different OpenMPT versions. However, the ID cannot be linked to you our your computer in any way, as it is completely random and does not contain any information about you or your computer setup. OpenMPT only sends the currently used version number, Windows version and build type to the update server – no personal data is sent along.

Advanced Settings[edit]

Here you can change the URL under which OpenMPT will look for new versions. You should not change this address under normal circumstances. However, brave and eager testers may want to change the address to https://update.openmpt.org/check/testing/$VERSION/$GUID in order to receive update notifications for test builds. Please note that is is generally not recommended to use test builds, as it is not guaranteed at all that they are stable (data loss cannot be excluded) or that they behave the same as final versions - for instance, pattern effects might be treated differently (buggy) in a test version but not in a final version. In that case, the buggy behaviour will not be emulated in future releases.