Filter "Recommended version" between 1.29, 1.31, and 1.32 maps?

[Daffa]

Can we have the Recommended version to reflect these 3 patches properly? At the moment, they all said 'Current', but the thing is 1.31 cannot be accessed by 1.29 and 1.32 cannot be accessed by 1.31 nor 1.29. This will help a lot of people who work around these patches like the ones who use 1.24-1.28 patches (since they can see it recommends 1.24-1.28).

 

[3dris]

Yes! I agree with Daffa, a lot of people will save his time with this filter.

 

[Ralle]

@TriggerHappy, can you help me get the versions and IDs?

 

[Daffa]

Some help I can provide:
W3i has different values for 1.31 and 1.32. It's 28 for 1.31 and 31 for 1.32 (not sure about the latter, I think it was that)

 

[Strydhaizer]

Basically you cannot access maps saved in newer version in the older versions of thr game

I agree with this, very helpful for those who still resist to download reforged patches. So far we only have "Reforged" filter in the categories.

 

[IcemanBo]

TriggerHappy's site has the mapping built in, inside the filter on the left: EditorVersion to patch version.

 

[TriggerHappy]

@TriggerHappy, can you help me get the versions and IDs?

You can view them in the editor build filter here: Warcraft III Maps

 

[Ralle]

Thanks for the responses guys and thanks for letting me take the numbers from your site @TriggerHappy. You rock.

I will update the site tomorrow night. It's 16 minutes to bed time, the worst time to update the site .

Next step would be to allow filtering. That will have to come later.

 

[Ralle]

It's updated.

 

[Daffa]

Thanks @Ralle!
I truly appreciate it. Helped me spare my time.

 

[Drake53]

Is there a reason for using editor version? Before 1.31 it makes sense, but since format version 28 the game version is also included in the war3map.w3i file.
I'm asking because my tool sets the editor version to 827208535 (W3N1), which seems to make the site default to 'Current', even if a map can be played on 1.31 too.
(side note: a map can still be unplayable on 1.31, even if game version is set to 1.31, if the map uses 1.32 natives, but this problem would also exist if the editor version was set to 6072 instead of using a custom value).

 

[Ralle]

Recommended is a suggestion. It’s the best the site can do.