Leaderboard

I've attached this image that shows the option you need to have enabled when exporting your mesh to .dae. It's something you need to fix in Blender. See this wiki page for additional solutions for this error: http://trac.wildfiregames.com/wiki/ExportingErrors

Then it would be "bonus/penalty" if something can be either/or. I do not know why you take personally. English can be studied after all, so it does not matter where the critique come from, a native or non-native speaker as long as the critique is founded well.

Actually it's the other way around: the engine needs triangles while you have quads. There is an option you need to tick in Blender when exporting to .dae

@av93 I'm not familiar with the terminology, but I interpret "micro" as "I have to think about lots of very minor steps", is that right? But how does this apply to my suggestion? Maybe I just don't see the full picture, but if implemented as above you aren't forced to do anything special. Maybe you shouldn't send single units into the enemy's territory, but you don't want to that anyway. If only cavalry can capture, capturing will be a quite rare event, especially if the enemy still has some defence towers which would most likely kill your units before they could be captured. Concerning formations/heros/females: these would require micro actions (as I interpret it), but they already do so. @wackyserious I see two issues. First, the gap between Champions and basic rank units grows even wider. (Also, I don't think it's fair to say a farmer had a lower moral than a champion soldier.) Second, binding the state of a unit to the current owner requires some extra storage/logic. However, this might be not too problematic.

I agree. I also hadn't heard of "malus" before. I'm fairly confident that at least ninety-nine percent of native English speakers haven't either. For those speaking Latin-based languages, it may very well be a different story. The ordering of "bonus-malus" does make more sense as generally positive things are listed first.