Entry evaluation process and Arma 3 version

[Rydygier 1302]

Regarding issues like this...

Let's say an entry, let's say SP gamemode, is well tested and working fine under one of recent A3 versions before deadline.

How would be handled in the evaluation process possibility of breaking things in the entry by changes/bugs introduced in the later A3 versions, released soon after deadline or just before it (no time for fixing/workaround for the entry)? Especially, that some entries may be severly handicaped by given bug/change while another may stay unaffected.

Edited September 7, 2014 by Rydygier

[Korneel 115]

Regarding issues like this...

Let's say an entry, let's say SP gamemode, is well tested and working fine under one of recent A3 versions before deadline.

How would be handled in the evaluation process possibility of breaking things in the entry by changes/bugs introduced in the later A3 versions, released soon after deadline or just before it (no time for fixing/workaround for the entry)? Especially, that some entries may be severly handicaped by given bug/change while another may stay unaffected.

Hi Rydygier, we will store the current build of Arma 3 around the submission deadline, and will use this build to evaluate the entries. Hope that answers your question :-)

[Rydygier 1302]

Yep, thanks. :) Just I hope, there will be enough time between chosen build release and deadline to react on changes and fix possible problems with them.

[Korneel 115]

Yep, thanks. :) Just I hope, there will be enough time between chosen build release and deadline to react on changes and fix possible problems with them.

Yeah, it's a good point - we'll most likely take the build as it is at the start of October.