That also happened for the 1_27 tag, it was actually also created before the 1_27 commits were pushed.

I think there is something bugged in your release process!

Hi @Geez

Sorry, I fail to understand your comment. Are you saying that the 1_28 tag points to the code for 1_27!?

The types and other important changes for 1.28 were pushed after the 1_28 tag, which is very confusing. Especially when you setup a dayz server the first time, you would expect to find the files for 1.28 in the 1.28 tag - which is not the case. This is totally odd.

Please consider using a versioning / tagging scheme that follows at least slightly common software development standards.

Or just use branches and keep them updated for the appropriate release, then you could also provide the appropriate changes for experimental without messing with the last stable release.

Thanks,

Bernd

What we are saying is that usually we update CETools when creating new release. As there are no changes in CETools the source code for 1.28 is same as the latest update for 1.27.
You can always download latest/specific update.

@Geez not talking about CEtools here, but about the mission files.

Thank you.
The tag issue has been fixed and our update process will be edited to prevent this issue for future updates.