hyperion

So you send a unit to trigger the alert and then sometime before the timeout ends you pass with your army Now you are worse off as without the alert in the first place. PS: changing the behavior after some minutes (8 here) sounds like broken design to me, don't care for mods tho.

Almost all your configuration is in ~/.config/0ad/config/user.cfg, not just hotkeys if you'd use a local.cfg you should know

Just some random guesses: * add doesn't sound right for _string, maybe append or replace * {civ} might be problematic * ProductionQueue/Entities/_string was refactored out over the years

https://github.com/0ad/lobby-bots echelon is the bot responsible for ratings

counters.js should be a decent starting point, then grep from there whatever you desire. Edit: if with rating you mean elo and not score, things obviously change

We had this in the past and was removed. The issue was that ranged units kept distance on their own. Melee inf had no chance to ever get close to ranged cav for instance. So this would need to be carefully designed.

You might want to clone the git mirror at https://github.com/0ad/0ad instead, beware there are no autobuilds for windows tho and you might be up to a day behind compared to svn.

best isometric RTS

Balancers (some at least) already try hard for all civs to play the same, if all maps play the same as well there is little to look forward to. Except for looks (tho not as bad as it once was) Anatolian Plateau is a great map!

I would like to see the bylaws say neither 0ad, pyrogenesis nor wfg shall be used for politics in any form or shape. The SPI likely doesn't want to see it's members pulling political stunts either for the sake of avoiding controversies.

That should be just some docs. At a cursory glance at the list libfreetype-dev seems to be what you need.

You need to install freetype first, was added as a dep to support font rendering in the future.

The argument for spear and bows to be available in earlier phases is the lower tech requirement for a civ to produce those weapons. I'd equate p1 to stone age, p2 to copper age and p3 to bronze age roughly. The high number of warhorses in p1 of a typical 0ad army is quite off

This would cover 90% if it works. Just imagine you have chained objectives and the second objective would be to capture a building, then you might want to disable can be damaged or captured till first objective is reached or you'd risk breaking the script/flow of the mission.

There should be a way to programmatically enable/disable capturability of an entity I'd say. I can think of quite a few scenarios this might be desirable in campaigns. Maybe there is even a clever way to do it already which I'm not aware of. Campaign support is very limited at this point, basically you are the first to be this serious about it and you are prone to run into many situations where you think this or that would be nice to have. So if you run into such an issue, don't be shy to ask for it to be added if it's not available to make your life and the life of future campaign creators easier. The first step to improve campaign support is to know what is actually needed/desired, then if it's reasonable the implementation should be only a small hurdle. An example of a feature that only makes sense for a campaign would be https://code.wildfiregames.com/rP25393 by @wraitii Anyway, much impressed by your work so far.

I only see two reasons for mercs, the civ predominately made use of them or for gameplay reason we need a unit that wasn't available "natively". Neither seems the case for Han.

Those 3 categories stand for generated, hand crafted and locked setup, mainland-like maps is orthogonal to them and as such a filter like "demo maps" is is a better fit.

There is eject health already defined and structures should switch to "damaged textures" at that point to give a visual clue for needs repairing to be garrison-able again. (Just that the art department only managed to get Carthage done in all those years ) One could make eject health the breaking point for can now be captured as well. This isn't that far apart form @Freagarach's suggestion me thinks.

Just to make sure I understood, you mean a mechanic based on territory influence / weight, instead of capture attack? If so sounds worth a try.

contains the problematic (to large) public.zip.backup, move that file up a level so the game won't see it here. Just make sure /usr/share/0ad/data/mods doesn't contain a public.zip neither and it might work.

Reporting the bug as was done is by far the best course of action

Capturing is the biggest reason, people playing tiny sized maps another and finally the ever reduced average game duration is what made territory less important than it was. This potentially breaks carefully crafted maps, acropolis bay might even be affected. Something else to think about here is build distance restrictions.

Mostly within, also imagine again the super ultra wide display where the exit button needs half a day of mouse moving to reach

If moving to the side due to ultra wide screens is undesirable this is the the next best solution to preserve art. Dead center is almost always problematic. I agree on this one.