View Issue Details

IDProjectCategoryView StatusLast Update
0004109The Dark ModCodingpublic05.05.2020 21:02
Reportergnartsch Assigned To 
PrioritynormalSeveritymajorReproducibilityN/A
Status acknowledgedResolutionopen 
Product VersionTDM 2.03 
Summary0004109: Updates not showing up in the internal downloader if 'VERSION' of a mission isn't updated
DescriptionFor the problem of the internal downloader barely ever noticing that a mission has been updated, a fairly simple fix should be possible.

Let me recall the current problems first:
- the VERSION field is a simple Integer, which barely ever gets updated, since missions most of the time receive only updates to the minor version
(e.g. 1.0 -> 1.0.1 and then 1.1, etc)
Because of that the mission-database still reads nothing else but the major version, and the downloader is clueless about any updates,
- to make it more complicated, there is no consent about how the version schema should look like.
Some author insist on having arbitrary conventions, such as 1.1 --> 1.1b or 1 --> 1.01 --> 1.1
Figuring out how to detect which version would be newer would actually become a mess.

- Because of these limitations, the version number doesn't get updated in the database and players are asked to manually delete the previous version from their harddrive


Current MissionInfo in the XML:
<mission id="14" title="Business as Usual" releaseDate="2010-01-14" size="16" version="3" internalName="business3" type="single" author="Bikerdude">


Now, the solution I propose for these problems would be quite easy, and at the same time would allow authors to use whatever custom versioning schema they want.

- The Integer VERSION should be changed to an INTERNAL_VERSION number, which doesn't require to be visible to any user.
It will in fact be nothing else but a counter which gets updated with each new version.

- A new String DISPLAY_VERSION will be added, which can hold whatever the author wants it to read like. This field will be displayed whereever the user can SEE a version number.

With that you have the flexibility to make sure you get the updates to the players without giving away anything.
And another bonus is, that the actual Update-Check in the Internal Downloader does not need to be touched at all,
because the logic to detect a higher version number on the server is already there.
Only the few places where users can actually see the VERSION info need to be updated.



New MissionInfo schema:
<mission id="14" title="Business as Usual" releaseDate="2010-01-14" size="16" internal_version="3" display_version="3.0" internalName="business" type="single" author="Bikerdude">
After next Update:
<mission id="14" title="Business as Usual" releaseDate="2010-01-14" size="16" internal_version="4" display_version="3.1" internalName="business" type="single" author="Bikerdude">
After yet another Update:
<mission id="14" title="Business as Usual" releaseDate="2010-01-14" size="16" internal_version="5" display_version="3.1.1" internalName="business" type="single" author="Bikerdude">
<mission id="14" title="Business as Usual" releaseDate="2010-01-14" size="16" internal_version="6" display_version="4.0" internalName="business" type="single" author="Bikerdude">
Additional InformationSee the corresponding thread for discussions

http://forums.thedarkmod.com/topic/15333-some-enhancements-to-the-internal-downloader/#entry343291
TagsNo tags attached.

Activities

user81

28.03.2018 09:44

  ~0010206

the fix is to use underscores in the file name eg elixir_1_3.pk4
Bikerdude

Bikerdude

05.05.2020 21:02

reporter   ~0012472

This tracker should be probably be closed, as the fix is in the above forum thread?

Issue History

Date Modified Username Field Change
28.02.2015 10:43 gnartsch New Issue
28.03.2018 09:44 user81 Note Added: 0010206
28.03.2018 09:44 user81 Assigned To => user81
28.03.2018 09:44 user81 Status new => acknowledged
28.03.2018 09:44 user81 Assigned To user81 =>
05.05.2020 21:02 Bikerdude Note Added: 0012472