hyperion

This feels a bit like an online shop where you can hover for getting a zoomed in picture of the product. If you feel the picture needs to be bigger just make it bigger I'd say, increasing width of this particular dialog shouldn't be an issue.

Was fixed in svn. If you need a26 you can backport https://code.wildfiregames.com/rP27657

berries_04 duplicates specific name. Also the sentence "These berries have not ripened until autumn." Doesn't add anything meaningful (spec name is Berries after all), so I'd drop it and just inherit the parent. About formatting, here an example of what I mean: <History> Since ancient times, wild berries have been a viable source of food. While caution had to be taken so that poisonous fruit were not gathered, the berries, whether they be strawberries, raspberries, or blackberries, were one of the few sources of sweetness. Not limited to consumption whilst fresh, berries could be dried or squashed and their juice fermented. </History> If you need multiple paragraphs and maybe other markup you can file bugs. Images should be possible to implement.

ResourceSupply element can also be moved to the berries template, the only difference between berries should be the actor.

Yes, deliberate game design. In the past the only way to train a ram as Mauryan was to capture an enemy fort for instance. Feel free to discuss this in a dedicated thread. My personal take it is fine as is.

Athens might be the originator but by the time of 0ad I believe it already spread across Greek, so giving it to others doesn't feel that wired to me. If it was a named theater used as a wonder then it would be a different story.

@sarcoma is obviously on the right track, this isn't about modesty, else we would talk about modest fanatics ...

The parent attribute for the Entity element specifies where to inherit from all that isn't explicitly stated in the current template. So yes, my suggestion is to create a berries template inheriting fruit and then inheriting the generic berries one in berries_XX templates. It probably should have been done already but requiring translators to translate the same over and over pushes it past the acceptable limit in my view. One or more white space, be it space tab or newline are all the same. You can simply continue on the next line whenever reaching the 80 chars boundary. Lines that wrap in the editor are to be avoided whenever possible in programming. Well, a sentence like "The soil around the grapes had to be aerated and the vine branches had to be pruned so that more grapes could grow." reads like they already had basic knowledge of wine production, which isn't surprising and not much info at all to be honest. So I'd rather elaborate on the role of wine in antique society, given there where even gods for it that role can't have been shallow. This one isn't a formal issue and so not a blocker, just mentioned it to give a hint as to how to possibly beef it up. Make of it what you want.

Just a quick look at pull 11, to much duplication, probably should introduce template_gaia_berries and inherit from it in berries_xx. About grapes, I'd expected a reference to Bacchus/Dionysus. Also xml is supposed to allow you to format your text without having an effect on the rendered result. So I'd suggest you split your one liners at around the 80 chars boundary. -- Stoa was part of the game and bolt tower was intended to be part of it, they are available in atlas for use in maps. There are quite a few atlas-only entities.

Pathing and targeting algorithms. OAD puzzle: kill 100 spear inf bunched together with two sword cav. Use atlas to try, the 100 aren't controlled by a player. Two sword cavs so most peoples micro skills should be able to pull it off.

Halt (H) Can be thought of as doubling dps when used correctly or a mighty tool against dancing.

Well, there is little strategic depth to 0ad. The discussion around proGUI shows this clearly once again. Sure you should be allowed to play to pop cap in p1 but shouldn't expect to be competitive with that. That's what I mean by forcing. Anyway I play for the visuals and the great sound tracks, so I don't care enough to debate this to death.

A player has to be forced to move to p3 at some point, tho there should be tradeoffs wrt to timing. Having reaching popcap be viable before p3 is also problematic.

@Lion.Kanzen did some related work. I don't know the state but maybe he can use help.

@andy5995, just a random thought, might be a case of snap curl vs apt curl.

For me the lowest is turtle at 0.1 speed? But that might be more comfy anyway because commands are for the next turn (in mp some more), so with 0 speed you won't see the results of your action until you speed up again.

This active pause sounds a lot like simulation speed 0, which you can set via console or add an option for via mod.

Yes, and in this context it's an Americanism among maybe some others, translating acknowledging a command for my native language / military would be something like "understood" or "copy" which is also gender neutral.

user.cfg has higher precedence than local.cfg which has higher precedence than default.cfg. So default.cfg are sort of system defaults and local.cfg are user defaults, so if a property is set in user.cfg 0ad won't check there. If it's not in user.cfg it will first look in local.cfg and if that doesn't yield a result check in default.cfg.

0ad-git? Your package script might need to build the spir-v shaders or use the 0ad-spirv mod.

In theory yes, but with line of sight in RTS this is probably not that meaningful.

The main game has airplanes! There is also a dragon.

That's the UnitAI, not the AI player, still unquestionably worth fixing, maybe file a bug if there isn't one already.

System print screen is all about your system, if it's broken fix your system (compositor). About screen shooting error messages, you can do that but never show them to others, they much prefer them as plain text. Any error message you see in game is also logged to stdout and the logfiles and allows for easy copy paste.

Dynamic input delay probably feels much worse than static somewhat lengthy one. At least for competitive play this seems a no go. That's a good idea anyway, nothing to do with turn lengths.