As most people are aware, A27 has some technical bugs: extreme stuttering and OOS on rejoin. The extreme stutter makes many players drop down to 3fps or even freeze and crash the game completely. We have determined that  it is caused by full hash. Wraitii has a fixed version with quick hash that solves this problem. I and @real_tabasco_sauce have tested it out and large battles with 4 players were able to run smoothly.  My question is, can we do a quick re-release like we had in A25-b or just call a new version A27.5 / A28, where we at least fix the hashing stutter.  If this is too much to ask, all we need to do is compile this: https://gitea.wildfiregames.com/wraitii/0ad/src/branch/quick_hash_only/ into .exe or appimages then distribute it to the player base so that people who aren't capable of building the solution can also play. Of course it might not be compatible with the rest of A27 players but if everyone could update easily, then it won't be a problem.  The solution can be popularised by advertising on the forum and the lobby heading message. We can do a release candidate every time a bug is fixed, just to get games going. This current version is almost unplayable for many medium spec users and a few players I know have quit because of the stutter issue.   

My intention is to be able to get a more or less accurate idea of the players' preferences by giving them the possibility of choosing multiple options instead of holding a vote in which only one option can be chosen, which would force each user to exclude some of their preferences from their vote. As an example: So far, there is a clear preference for the addition of Building Hotkeys over Players' Stats Overlay, with a difference of approximately 18% percentage points (17 votes/22voters = 77% vs 13 votes/22voters = 59%. ). Of course, here we have to take into account the different preferences between single player users and multiplayer users. We could infer that a single player user does not have much interest in seeing the economic information of his allies as a multiplayer player does. Same for hosts features which has even more difference (23% over hotkeys). And this "could confirm" that right now most voters are single player users. Evidently, this seems to be the case. However, taking into account what I expressed in the previous paragraph, we should consider which of these features are more suitable for the two game modes (single/multiplayer). Taking Active Pause as an example, it doesn't seem right that a player can execute commands while the game is paused in a multiplayer game, and in this regard I would put more emphasis on how to modify the pause system in multiplayer in such a way as to mitigate pause abuse, something we know can be quite irritating.   Finally, I would like to add that beyond the "democratic spirit" of any vote, it is difficult to take the results as an absolute and definitive truth. Rather, I believe they serve as valuable feedback for those who, with effort and dedication, develop 0 A.D. and make the decisions they consider most appropriate (and feasible) to continue improving this great game, incorporating Autociv features that have contributed a lot. It could also be a nice tribute. =)

Updates for A27: To enlarge training icons: larger-icons.zip   Ranged Overlay without OOS: rangedoverlay.zip   Previously, the ranged overlay mod caused OOS with community mod, because the stats of units are different. Now, community mod no longer exists so your templates will not be touched by other mods and hence no OOS issue. 

please give the vote more time

"Active pause" should not ever be a feature for multiplayer, I'd like to see that fixed when its merged. Perhaps single player users would want it to try to win super challenging scenarios akin to a 1-sided chess match, so I assume that is the demographic where we get those votes from.

Which at this time would tell you that all features are desired in base game (by majority voting).

I guess divide all categories by numbers of voters.