This is a non-breaking change (and, in fact, a bug fix
) as far as the official build is concerned, but it will
affect packagers of custom Windows builds in the next release (currently scheduled to be 1.31.0).
A new class, net.pms.configuration.Build, has been added as a one-stop location for settings that custom builds are most likely to customize. The next release will optionally re-enable update checking, which previously used an update URL hardwired in PMS.java. This is now defined in Build.java, along with some other build-specific settings.
By setting IS_UPDATABLE in Build.java to false, update checks (manual and automatic) can be unconditionally disabled for Windows builds that can't/won't use the update mechanism. (There is no need to disable update checks in builds for other platforms as they're currently only supported on Windows.) Alternatively, custom builds that do want to take advantage of this mechanism can substitute their own server URL by setting UPDATE_SERVER_URL to an appropriate value. Finally, custom builds can define a build-specific profile directory name by means of the PROFILE_DIRECTORY_NAME field. This can be used to ensure that a custom build's profile files don't conflict with those used by the official build.
See the Build.java
source for more details.