Leaderboard

Why ? While 0 A.D has overall nice art, it looks a bit like a game from a few years ago (which makes sense as development started ~ 2000). This is reflected in the UI, which has many ornamental elements and especially in the main menu, where for my liking, the text is too small and it looks too crowded. Also I'm more a fan of minimal designs. Therefore I have been working on an alternative UI and may now introduce the shiny UI mod. ____________________ shiny.pyromod Installation note: When you use multiple mods it's probably best to enable this one last (after) everything else. See this comment: https://wildfiregames.com/forum/topic/54074-shiny-an-alternative-main-menu-ui/?do=findComment&comment=451016 ____________________ For the moment it's WIP, but everything should be fully functional. The main features are the easier access to the important options through the top panel and the much larger main panel in the middle. One problem with this design is that it works not with the backgrounds that are already in the game (white text on light background), which is why I include a new custom dark background. Credits to: @Langbart who gave me the idea and with whom I discussed much about the design/ who generally helped. The design works on big screens: and small screens: and everything is present that is in vanilla: Also: an updated loading screen So feel free to try it out and give some feedback/ to report any problems. possible discussion topics: button positioning, button highlights & visibility, text size, is the topbar useful ect...

In my opinion Graphic Artists of 0AD have achieved a tremendus success in defining the modern graphic style for modern RTS games. All units, Biome and scaling is better than all other RTS game of this time. In case of music,sounds 0AD can also be regarded as a masterpiece. Gameplay has also improved significantly after the latest release. Although I would recommend beetter AI for FFA single player. Therefore I would deliberately recommend/suggest/support a massive marketing campaign for 0AD in this situation when people are eager to choose a new RTS leader for the upcoming time. Thanks All Artists, Musicians, Programmers for creating an awesome game like 0AD.

shps.mp4

This thread has derailed from the start. I apologize for not closing it earlier.

The Stalfos The word Stalfos has its etymology in the ancient Akkalan language, and refers to bones of once living creatures. In modern times the term is applied loosly to almost any undead abomination and monstrosity. As a political entity, the identity of the Stalfos has changed just as dramatically as all the kingdoms that have risen and fallen across the history of Hyrule: due in part to the undead being the servants of many fighting lords and necromatic powers. HISTORY The origins of the rituals and practice of animated skeletons is lost to time. Many Hylian scholars agree that necromancy had its origins west of the Gerudo desert at a time when dragons still ravaged the land. In the ancient lore of the Gerudo and Akkalans, necromancy was common practice during the Ancient Age in the far west of Hyrule. The Kingdom of Ikana and Cobble Kingdoms were famously destroyed during the height of their necromancy practices. Many cults to the forgotten god Mudora practiced necromancy rituals deep in the Gerudo Desert. After King Nohans' conquest of Hyrule, the Ancient Akkalans enforced a complete ban on all forms of necromancy and thus the practice faded for hundreds, if not thousands of years. Petty necromancers and Gerudo Kings have occasionally tried to revive the practice over the centuries, with little luck. In modern times there have been stories of Stalfos appearing in larger numbers than was usual. Whispers of necromantic powers returning the Hyrule are not uncommon. Indeed, there are forces at work that wish to revive the long forgotten arts of cheating death. NECROMANCERS Without a master, most undead simply wander without any clear objective. Shambling Stalfos and ReDead zombies can be found aimless in the darkest corners of Hyrule, remnants of a long gone necromantic age. Should these horrors ever fall under the power of a necromancer or mage with enough skill, they could be used to wreck untold havoc on the world as a fearless horde of soldiers that feel no pain and no remorse. PLAYSTYLE The Stalfos have a very distinct gameplay structure that deviates from many other factions. The Stalfos are not creative by nature, and cannot construct new buildings or train new units. Rather they can only transform dead material into what they currently need. In terms of structures, the Stalfos must capture pre-existing ruins on a map and by ritual transform them into the buildings they need. Should there be too few ruins for their purposes, the Stalfos can expend many Rupees to unearth a new set of ruins at a target location. Once these ruins have been dug up to the surface of Hyrule they can convert them into the structures that they require. As for Stalfos units, they accomplish expanding their army by collecting the corpses of their victims and converting them into the forms they need for battle. This is represented by the "Bone" resource, which replaces food. Bones can be harvested from any dead organic creature, as well as graves found on some maps. If a Stalfos player has a unit that can directly raise the dead, they can instead instantly turn corpses into new units. For more details on the Stalfos Heroes and their unit roster, check out the spoiler below: HEROES

It looks like the community maps mod hasn't been updated since a23, so I've made a temporary fork of the project called community maps 2 It's pretty basic, but it gives access to the maps again. And I've run some migration scripts on the maps themselves to make them compatible with >=a24. Though I haven't checked them all for warnings or errors. If you notice any problems, just open a ticket on the community maps 2 repo and I'll try to fix things up; or you can make a PR if you feel like it. The pyromod file can be downloaded from the releases section

Hello. I would like to dispel a few doubts and misconceptions about the mRNA vaccine, since it is a new technology and people might be curious of how it works. First we need to discuss what is DNA and RNA. DNA is a molecule that resides in the cell nucleous and is responsible for storing our genetic information (our genome). It's quite a sturdy molecule and very stable. RNA is a molecule that can be found in the nucleous and in the cell body (cytoplasm). Is a small molecule and one of its main purposes is to convey information (or messages, if you will). It is not as stable as DNA. How do DNA and RNA work in the body? We know that DNA is stored in the nucleous, but the majority of the cell processes happen in the cytoplasm, which is separated from the nucleous (in humans) by the nuclear membrane. So if the cell wants to produce something (protein, antibody, enzyme, etc) using the information stored in the DNA, it need that information to get out of the nucleous. That is where RNA comes in. In a process called Transcription, a segment of our DNA is copied in the form of mRNA (the "m" stands for messenger), which then can leave the nucleous and reach the cell body. There, the information that it contains can be used to produce stuff for the cell. We can say then that mRNA is nothing more than the mailman of the cell, bringing information from the DNA to the cell body. The thing though is that this mailman is short lived and will soon be recycled by the cell. This way, the cell can regulate itself and more easily avoid overproducing stuff. So, back to the mRNA vaccine. Well, we know that the only thing that mRNA can do is convey a message. But what message does the mRNA vaccine convey? It conveys instructions to build a specific protein called SPIKE. The COVID-19 virus uses this specific protein to bypass cell defenses, entering and infecting the cell. Why would i want my cells to build a viral protein? The purpose of vaccines is to train your imune system against a specific invader. But to train they need a target. Vaccines provide the target. Some use inactivated or dead virus, while others use active, but weakened virus. Some even break up the virus in the lab and use only some of its parts. The mRNA vaccine is new because instead of injecting viral proteins in your bloodstream, it inject instructions that will allow a limited number of your cells to produce those proteins, thus providing your imune system with a target to train and practice with. Since SPIKE is THE protein that enables the virus to enter the cell and (so far) is found on all variants of the coronavirus, it was the most valuable target to practice with. Will my cell be altered in any way by the vaccine? In short, no. Because as we've seen before mRNA doesn't last very long in a cell and will eventually be recycled by it. It will stay active for a time, allowing the cell to produce and export SPIKE to train the imune system and then it will be destroyed. If if can just inject SPIKE in my bloodstream, why use a vaccine that makes me produce them instead? That is a great question and it really highlights why this new technology is so awesome. Proteins are hard to produce in a lab. They are formed from a myriad of amino acids and have complex shapes. mRNA, on the other hand, is just a string, like a bead necklace and it is it made from only 4 different molecules. mRNA is easier and cheaper to produce in a lab in comparison to proteins. Another reason is quantity and space. Each vaccine shot has limited space and the more targets we can fit into it, the more practice our imune system will have against it. Each SPIKE protein counts as a single target, but each mRNA can produce hundreds of targets (or more) during it's lifespan. So we can get more quantity for the same space using mRNA instead of proteins. If the mRNA vaccine is so good, why do some people have side effects? In the case of mRNA vaccines, the side effects are a result of your imune system fighting and practicing against the targets that we introduced. The imune system has a pattern of response against invasions. First step is stall the enemy while we gather intelligence, meaning you body will increase its temperature (fever), produce mucus (sneezing, coryza, cofing) and redirect your energy reserves to fighting the invader (tiredness). Although these are symptoms commonly associated with diseases, it's actually our body that is causing them. They might be a pain to us, but they are even more of a pain to the invaders and are quite effective in most cases. This strategy is meant to buy time in order for the imune system to capture and study some invaders in order to produce antibodies against them. So, by taking the vaccine, although you are not being invaded by any hostile forces, you are producing something that the body does not recognize and so it will mount a full attack against it. Since people are different, the intensity of their imune response is also different. This means that some can experience very mild effects will others might not. It's basically like an allergic reaction. If i can also have side effects from the vaccine, why not just get COVID instead? Well, the main difference between a vaccine and virus is that the virus will destroy your cells, while the vaccine won't. If your body can contain the virus in time, then you'll experience some to no symptoms and will be fine. If your body cannot, then the virus can get out of control and cause greater damage to your organs. COVID is specially nasty, since although it starts at the lungs it can migrate to other parts of the body (heart, brain, liver, etc). Any damage to those areas might cause significant health problems and even lead to death. When we look at the situation this way, the vaccine is preferable, even if it has a chance to cause some side effects. TL;DR; 1 - mRNA is not DNA 2 - mRNA can't change your genome 3 - mRNA is short lived 4 - The mRNA vaccine allows your body to produce the viral protein SPIKE (for a limited period of time). 5 - SPIKE alone is harmless. 6 - All COVID-19 virus, so far, have SPIKE and use to breach cell defenses and enter the cell. 7 - By taking the vaccine, you are providing SPIKE proteins for your imune system to study and learn how to fight it. 8 - Then, when a COVID-19 virus enters your body, your imune system will easily recognize the SPIKE protein is has and will stop the virus before it does significant damage to you.

Most competitive players are not playing the game often, so it's not being built for competitive players. The fact that we don't have such diverse civilizations is because there is no design plan and someone to command it. I've even started working on it, but it takes a lot of time, and unfortunately I don't have my free time to spend on it anymore, Besides that the part of 0.ad community is extremely ungrateful. You spend hundreds of hours working on various improvements, to find two or three problems/errors and post on the forum all the time when the new alpha is bad. I said several times that a24 was a work in progress and that a25 would be much better, but they continued to talk a lot of crap. Well the "end" result of the work is an alpha25 much better than alpha24 and 23 as I said. Lack of patience is a problem, especially for those who don't move a finger to help with anything. Basically the alpha 24 - 25 was mostly build by me and @Nescio (gameplay/balance), but we're not working on it concretely anymore, so if no one else is interested in this, players are destined to play with these civilizations / gameplay / balancing for many years, like that how was a23 sling + ram.

I was thinking the same for a while ! The game seems to be more and more tailored only for hardcore competitors who expect perfect balancing between all civs : something which is impossible without making them completely similar. This withdraws most of the game diversity except graphically and, to some extent, the interest to play different civs to get a different playing experience. The game becomes quickly annoying for casual playsers and generally not hardcore competitors players. I believe the game is not played only by hardcore competitors. Maybe the generalizing civs movement was intentend to get a sens of balancing before re-adding diversity to the game to take it out of its competitor niche market ?

I feel a bit sorry for this uneducated person:

Extended from this thread: Github Repo: https://github.com/JustusAvramenko/0ad_terrains_overhaul @maroder, myself, and others are looking to build upon the biome and map work we did for Alpha 25. We will post discussion and progress reports in this thread. We will also entertain suggestions, bug reports, and criticism here. First thing Maroder is working on is improving Gulf of Bothnia random map. First thing I am working on is improving the India biome. I'm making wider spaces to build and removing the obscene amount of grass props. ------------------------------------------------------------------- In addition to improving the existing new biomes from A25, I'd like to add a few more for A26: Hispania-North Africa Italia Persia ------------------------------------------------------------------- We would also like to work with the team to extend and expand the biome code to allow for more flexibility and interesting maps. Wishlist. Note: Not all random maps are required to use all options available in the biome files: Additional Gaia options fish1 fish2 treasure1 treasure2 treasure3 bushForest1 So, these are bushes, plants, and saplings that line the edges of forests. This is crucial to make forests look natural. bushForest2 dangerousHuntableAnimal Boars, etc. riverineShoreAnimal1 Crocodiles, Hippos, etc. riverineShoreAnimal2 dangerousAnimal1 Tigers, Lions, Wolves dangerousAnimal2 Additional Decoratives bird1 bird2 oceanAnimal1 sharks, etc. oceanAnimal2 dolphins or Portuguese man o' wars, etc. rockShore cloud1 dust1 Sand storms, etc. dust2 Resource Counts. Allow biomes more fine-tuned control over various resources. Patch: https://code.wildfiregames.com/D3995

When designing civs (or redesigning them), I think the focus should not just be on balance, but to make each civ "Favorite Worthy." What I mean is, each civ should have aspects that make it unique, fun, and cool enough to make stand out and make it worthy of vying for the community's "favorite" civ. In a "tier list" ideally it should be a struggle to decide which civ should be knocked down to a 'C'. They should all be clustered at B, A, and S. Some ideas: General Remove champion "unlock" techs and move them back to Fortress unless otherwise stated. Move Heroes to Civic Center unless otherwise stated. All Citizen-Soldiers types in every civ have Rank Promotion technologies up to Advanced. Exceptions 1 type of Citizen-Soldier per civ will have an additional promotion tech up to Elite. 1 type of Citizen-Soldier per civ will have no promotion techs. Unless otherwise stated, all civs retain their current bonuses and technologies. Athenians Retool the "Delian League" team bonus. All allies can train the Delian Marine from their Dock. -20% build time for all Ships and Boats. -20% research time for all Dock Technologies. "Painted Stoa" structure (build limit: 1), which grants the "Greek Architecture" aura (Buildings +20% health). Remove the "Greek Architecture" bonus from all other Greek civs. Heroes trained instantly at the Prytaneion (not Civic Center). Gymnaseion Replaces the Barracks Larger footprint and +20% greater health. Slightly more expensive. Trains "Hoplite" Citizen-Infantry and Champion Infantry "City Guard." Archery Range available to train Athenian Militia Slinger, Cretan Mercenary Archer, and Thracian Peltast. "Scythian Archer" Champion Infantry trained at the Fortress. Britons Chariots Available from Town Phase, after researching unlocking tech. When "killed", the Javelineer rider jumps off and continues to battle (until he too is killed) Slightly underpowered in Town Phase, but has a City Phase upgrade "Reinforced Undercarriage" which makes them extra stronk. Add Infantry Swordsman to the citizen soldier roster, available in Town Phase. Reimplement the Population Bonus special for their buildings, but at +1 population, instead of the old +2. Carthaginians Embassies "unlock" ethnic mercenaries at the Barracks, Stable, and Range. War Elephants have a "Tower" upgrade, which adds a Howdah prop to them. Cothon Shipyard shoots arrows. A fourth hero can be "Xanthippus of Sparta", who specifically boosts mercenaries. A 3rd champion, available at the Fortress: "Veteran African Infantry", a champion swordsman with a mix of Carthaginian and Roman equipment. "Sacred Band" champions still trained at the Temple. Gauls Give them a cheap Infantry Archer, "Gallic Hunter," available in Town Phase. Add Infantry Swordsman to the citizen soldier roster, available in Village Phase. Carnyx Trumpeter should have a "Horn Blow" special ability that temporarily improves attack of nearby Gallic troops. This is automatically done every 2 minutes in battle, but can be manually activated by the player every 1 minute. Iberians Keep the free starting walls, but remove the free gates (just have openings; the player can close them with fresh walls and gates if they wish). Allow the Monument to be built anywhere, even in enemy territory. "Burning Pitch" technology allows players to toggle javelin-throwing units between regular (anti-infantry) and burning (anti-structure) javelins. "Horse Country" tech at the Corral, for another -10% cavalry training time. Champion Infantry and Champion Cavalry can swap between Sword and Javelin. Kushites Give them a free Sanga Cattle at the start of the match. A new "Extensive Husbandry" tech at the Corral makes training animals faster. "Iron Smelting" tech makes Forges and Forge Technologies a lot cheaper and faster. "Iron Exports" makes bartering for Metal at the Market more profitable. Macedonians Barracks New "Royal Barracks" upgrade for individual Barracks in the City Phase. +50% Health to the upgraded Barracks. Can train Elite Phalangites and Champion Hypaspists. Stables New "Royal Stables" upgrade for individual Stables in City Phase. +50% Health to the upgraded Stable. Can train Elite Thessalian Cavalry and Champion Companion Cavalry. A 4th hero "General Craterus" boosts Phalangites specifically. "Naval Arms Race" technology unlocks the "Hexeres" heavy warship for the Macedonians. Mauryas Remove Population Cap civ bonus, but... Citizen-Infantry. Bonus: 0.5 population cost Bonus: -50% train time Bonus: -25% resource cost Penalty: -50% gathering rate Penalty: -50% health Penalty: -25% attack Worker Elephant can construct buildings again. Maiden Guards can swap from bow to sword. Mauryas receive a free Palace at the beginning of the match. The hero Chanakya can be trained in tandem with the other heroes (he doesn't count toward the "hero" training limit) 4th Maurya hero "Bindusara." Persians Keep Population Cap civ bonus. Organic units start out with -15% health and -10% train time. Receive a free "Yakchal" Ice House at the start of the match for a +5% health bonus to units. Build up to 4 more Ice Houses for additional +5% health boosts for each one built. They get more expensive for each one built. Ptolemies "Syncretism" special technology in Town Phase. Allows Priests the ability to build the "Isis Statue" and "Serapis Statue." Isis Statue Short-range Aura: Nearby Gatherers +20% gather rates Serapis Statue Long-range Aura: Nearby Units +10% health "Lighthouse of Alexandria" is a 2nd Wonder Player can still only choose to build 1 Wonder, but the Lighthouse can be built on the shore and gives a large vision range. "Temple of Edfu" would be the option to build on a non-water map. Romans An extra big House available in City Phase called the Insula ("Tenement Building") Population Bonus: 20 (plus house pop techs) Triarius trained at Elite rank (no promotion techs necessary). 2nd Team Bonus "Socii Allies" Allied Soldiers +10% attack within range of a Roman Civic Center or Army Camp. Seleucids Very much the same as they are now, except... Given back their Library. Spartans Team bonus now applies to all Melee Infantry (not just Spear Infantry). "Sysition" replaces the Barracks. "Hoplite" Citizen-Soldier, Champion Infantry "Spartiates," and Spartan Heroes all trained here. The "Helot Practice Range" Archery Range class building Trains Helot Skirmisher and Helot Slinger "Helot Emancipation" technology unlocks the ability for Helot units to upgrade individually to Light Hoplites. New "Helot" support units Cannot construct buildings, but... +25% resource gathering ability over Female Citizens. Can be captured by other players

Hey guys. My mod was never intended to be woke, progressive, or to "right historical wrongs," or to reduce female representation, remove/promote misogyny/misandry, or anything pro/con politically or socially. I just felt it made more sense to have male and female variants of civilian citizens, aka "villagers." That's pretty much the extent. I think it also just looks cooler to have male and female villagers working side-by-side.

I know that this is off-topic forum. However, this is way way way way way way off topic trolling.

I haven't seen it posted on the forums, and I thought the devs should know.

there are some big caveats here, though, which I would contend make all the difference. See celts building pop bonus, stables, ptol eco buildings now have a cost (although still technically unique it is less so), all civs have rams, all civs have siege factories, multiple civs lost universities, lighthouse changed and as a result is now unused, cav health tech was propagated to all civs which devalued Persian and sele civ, Maury ele is less helpful now, Athens lost p2 champs, Sparta lost champ types, Roman army camp while still unique is also less capable and therefore not used as much. There are more but that is what I can come up with without having to think. I know some of these might be coming back, but there is no doubt that a lot of the game is fundamentally different now. For some civs like mace their uniqueness has basically been almost totally eliminated. The diversity isn’t as bad as it was in a24, but I don’t think it is anywhere near where it was in a23 (as imperfect some things were in a23) I agree that the game should put back in many of the unique aspects that are most noticeably and used

@Stan`

A Quick Introduction Hello Everyone! Since this is my first post on the 0AD forums, i would like to start with a quick introduction. I've come to know about 0AD quite recently and been playing it since May 2021 (single-player). I have played quite a few RTSs already (namely Age of Empires II, Age of Mythology, Warcraft 3 and StarCraft), but this was the first game that i ever saw a Batch Training mechanic and i love it! Fun aside though, i also started doing some tests to try and use this mechanic to it's fullest potential. In this regard, 0AD sets itself apart from those other games i mentioned because it is an Open Source Project so I could go through the code more easily to unearth the formulas, modifiers, etc in order to make my analyses. So without further ado, let's do some math! The Mechanic Unveiled First things first: How is Batch Training implemented? As far as resource costs and population growth is concerned, there are no changes, but training time (for each individual unit) is greatly reduced using the following formula: BatchTime = BaseTime * (#Units ^ Mod) Where: BaseTime = The time it takes to train a single unit #Units = The size of the group Mod = Modifier, a value that is intrinsic to the Building Type and determines the reduction in Training Time. List of Modifiers: Houses: 1.0 (meaning, Batch training in houses does not reduce training times) Corral, Market, Siege Workshop, Elephant Stable, Special Buildings: 0.7 Barrack, Stable, Fortress, Civic Centre, Carthage Embassies: 0.8 Let's illustrate this with an example: Unit: Spartan Hoplite – From Civic Center (Mod: 0.8) BaseTime = 10 secs #Units 1 by 1 - Time (s) Batched Time (s) 2 20 17.41 3 30 24.08 4 40 30.31 5 50 36.24 So, as seen in the exemple above, Batch Training reduces the training time of units considerably and, on the surface, it appears to be always better to Batch train instead of training 1by1. However there is a tradeoff. You'll only have said units at the end of the entire Training period (which is longer than the time to train a single unit). What this means is that 1by1 will give you readily available units sooner, but in smaller quantities, while Batching will give you readily available units later, but in larger quantities. This is a point to consider, specially in the early game, where we want to gather resources as fast as possible to build up our economy and our army. If we call the amount of time a unit is out on the map ActiveTime (as in it can perform actions such as move, gather, fight, etc), we can say that the method that gives us more ActiveTime overall will be better. Analysis Let's use our Spartan Hoplite to understand this problem. Spartan Hoplite – From Civic Center (Mod: 0.8) BaseTime = 10 secs Let's say we train 2 units using both methods: From our table we gather that 1by1 will produce a unit after 10 secs and another after 10 more seconds, while batching will produce 2 units after 17.41 secs. This means that both methods don't generate any ActiveTime in the first 10 seconds (since no units are out yet) and will start generating the same amount after 20 secs (when the second unit of 1by1 gets done). So what we can compare is the amount of ActiveTime generated after 10 secs but before 20, for both methods. Do note that each unit out on the map generates 1 sec of ActiveTime for each in-game second. This means that 2 units will generate 2 secs for each in-game second and so on. With that in mind we can do the calculations and reach the following table: #Units = 2 Time Elapsed (s) 1 by 1 Batching #Units Produced ActiveTime(s) #Units Produced ActiveTime(s) 0 0 0 0 0 10 1 0 0 0 17.41 1 7.41 2 0 20 2 10 2 5.18 #Units = 3 Time Elapsed (s) 1 by 1 Batching #Units Produced ActiveTime(s) #Units Produced ActiveTime(s) 0 0 0 0 0 10 1 0 0 0 20 2 10 0 0 24.08 2 18.16 3 0 30 3 30 3 17.76 #Units = 4 Time Elapsed (s) 1 by 1 Batching #Units Produced Total ActiveTime (s) #Units Produced Total ActiveTime(s) 0 0 0 0 0 10 1 0 0 0 20 2 10 0 0 30 3 30 0 0 30.31 3 30.93 4 0 40 4 60 4 38.76 As we can see, although batching reached the total amount of units faster than 1by1, that amount of Active time generated in the same period heavily favors 1by1. Now let's see if this trend continues and calculate the percentages to see by how much 1 by 1 is beating Batching. # Units 1 by 1 Batching Percentage (%) Total ActiveTime (s) Total ActiveTime(s) 2 10 5.18 51.8 3 30 17.75 59.17 4 60 38.74 64.57 5 100 68.81 68.81 6 150 108.42 72.28 7 210 157.97 75.22 8 280 217.76 77.77 9 360 288.04 80.01 10 450 369.04 82.01 27 3510 3519.02 100.26 Interesting! As we increase the amount of units trained, Batching slowly catches up to 1 by1 and by the time we reach 27 units, Batching will match 1by1 in Total ActiveTime generated. We can also see that any number of units above 27, Batching will start becoming more and more efficient. Naturally, 27 units costs an unfeasible amount of resources and time (specially in the early game) so we can conclude that by our metric of ActiveTime 1by1 is by far more productive than any amount of batching we can get in the early game. Conscription In the City Phase (last phase) we get access to the Conscription technology (in the barracks and the Stable). This technology lowers the Batch Training modifiers by 10% (Mod = 0.8 to Mod: 0.7) and that is a huge change. Lets do the same calculation, but now with Mod = 0.7. # Units 1 by 1 Batching Percentage (%) Total ActiveTime (s) Total ActiveTime(s) 2 10 7.51 75.10 3 30 25.27 84.23 4 60 54.44 90.73 5 100 95.74 95.74 6 150 149.69 99.79 7 210 216.68 103.18 This means that in the late game (after researching Conscription), given enough resources, any Batch amount > 6 will be more efficient than training 1by1. That is also valid for all the buildings that naturally have Mod = 0.7. Discussion So, the main question that arises from this analysis is: Is the Batch mechanic useless in the early game? My answer is NO and here is my reasoning. THE GOOD: - Batching is great for early game rushes and timing attacks: since we'll be able to pump units much faster that by building 1by1 and we can't afford to build multiple barracks or stables in the early game. - Batching is great for dumping excess resources: Stockpiling resources isn't advisable, since resources don't produce anything while sitting in the bank. Unfortunately it happens sometimes, so if we find yourselves with excess Food, we can just build a Stable and Batch train some horses to explore the map and harass our opponent. - Batching gives options instead on limiting them: If Batching was universally better than 1by1 then there would be no point in having having a choice. By having it's drawbacks, Batching gives more variety to the game by enabling certain strategies. THE BAD: - Batching is less flexible than 1by1: By Batching, we sink a lot of resources and have to wait a considerable amount of time for them to bear fruits. This means that if we need to cancel some of our productions in other to gather resources to build an upgrade or advance phases, the amount of time lost training that group can be great. - Batching eats a lot of population: Population is also a resource. So if we want to Batch train a large group we need to have space available. Also, we'll need to quickly build houses to open more space to not get capped and keep producing out of our other buildings. THE UGLY: - Batching is eclipsed by 1by1 for economy: Since much of our goals in the early game is to boost our economy as fast as possible (and we do that by maximizing ActiveTime), batching does the exact opposite of what it's expected of it. And now in A25, the introduction of the Autoqueue mechanic basically kills batching even more for early game economy. Closing Remarks Well, that's basically all i had to say about the subject. I hope this post wasn't too boring and you were able to enjoy it. I would also like to read your opinions and comments on the matter. If you agreed or disagree with this analysis and why? Any concerns or constructive criticisms are always welcome. See you on the forums and have fun! ===================================//================================== TL;DR (just in case) Which is more efficient in the early game: training in batches or training units 1by1? Well, 1by1 will give you readily available units sooner, but in smaller quantities, while Batching will give you readily available units later, but in larger quantities. By comparing the Total ActiveTime (the amount of time a unit is on the map, ready to move, gather, fight, etc) in both approaches, we get: - From the Barracks, Stable or Civic Center: 1by1 is more efficient if the batch size is smaller than 27. Since batches of 27 are basically impossible in the early game, for economy purposes, 1by1 if far better than any amount of batching. -Batching is better than 1by1 in strategies involving rushes or timing attacks. ==================================================================== EDIT 1: So, considering what @Jofursloft and @Freagarach have said in the their posts, i redid the calculations for batching and 1by1 considering more productions cycles and the ProgressTimeout delay that autoqueue gives. To avoid making this post bigger than it already is, i placed the the calculations and the result tables in the attached pdf. In general, smaller batches (2 to 3 units) break even with 1by1 by the 3rd production cycle, while bigger batches (5 and upwards) break even by the second production cycle. Things are a bit less efficient if you use autoqueue, but not by much. So, as long as you can batch units constantly, batching will always be better than 1by1. Also, the bigger the batch size, the better. Batching Revisited.pdf

Another classic clash for Sunday afternoon entertainment!

How did you know I just made a vulture model ? :p

circling vultures above chickens

1 thing I have spotted: we need bigger chickens for A26. Or, we replace the starting hunt with another animal that is larger and easier to click on. For example, sheeps /cows.

This is overblown. One's suitability to join the army on campaign was often predicated on economic status and age. Middle class Greeks and Romans did serve in the infantry, but lower peasants and those too young and too old often did not. A certain number of upper class citizens had to provide cavalry for the army, but those were often the sons of the landowners and serving in the cavalry could be avoided by being willing to supply additional horses. Often a campaign did not necessitate a "full call-up" of available manpower either. Full call-ups usually only occured during times of severe national emergency or siege. Athens could only field 10,000 hoplites from a population of 30,000 citizens and 100,000 non-citizens for the "national emergency" Marathon campaign. And Gauls had a warrior class, separate from the peasantry.

much more relevant (in my mind at least): to this day women gatherers still have lower vision than males. this is quite absurd, and clearly has no historical justification, there's only a gameplay motive, but effect on gameplay is actually minimal, and some times even paradoxical, like women not seeing archers attacking them.

Tbh female players are more concerned about lobby harassment than 1 gender citizen...

Between a24 and a25, the biggest change has arguably been unit pushing. This new feature has succeeded in smoothing unit movement considerably, but has made much more than that: it has changed they way units move and look, and the way they approach and engage enemy targets. I always felt like in this regard, mine was a minority opinion, but after discussing with a friend who was much more enthusiast than me about unit pushing, I think we can possibly agree on some way to enhance it, so I will speak out about what I think it's wrong about it. Units interpenetrate basically every time you move them. When you have a whole bunch moving together, they form queues so tight that they look like solid worms of people. In some cases, it may be hard to tell how many soldiers there are, making it particularly difficult to predict how a battle is going to go. It is even more difficult to tell how many soldiers are getting killed, because they are so densely packed in the melee that people dying are invisible inside the mob. Rams can sometime interpenetrate so deeply that two of them may look like there is only one, while they are attacking a building. Choke points are no longer of any real strategic relevance, you have to fit melee units into them to make them effective, and that's usually impossible/unfeasible. And the slightest gap between two buildings allows a whole cavalry army to pour in between in a couple of seconds. Any passage, narrow or large, can fit an army as large as you want. I think it wasn't necessary to deviate so strongly from how unit movement looked before, the new pathfinder is more andanced and effective, but it went too far on this new road. It is ok if a big mass of units struggles to go trough a narrow passage, that's how things work in reality anyway. And besides that, I think the look of battles is worse now than before, less clear and more hazardous. In any case, unit interpenetration is bad and should be avoided if possible. Thank you for bearibg my rant, let me know what you think.

Buenos días /tardes/noches; -Texturas para unidades de infantería ligera lusitana en fase 3 , provisionales; (las texturas inferiores de pelaje son las capas, además de añadir textura para grebas y cinturón) Escaramuzador lusitano; Espadachín lusitano; Hondero lusitano; Lancero lusitano; -Cualquier sugerencia , crítica .... serán bien aceptadas. Disculpen las molestias*

Hi all, after playing for a while, I finally have found some good friends in games. We had a couple of meetups and they were fun. I’m happy that I can find them here. Just wanna thank you and wish everyone a good day! :D

I don’t intend to debate the merits of each change. But what I can say is that something like the globalization of siege factories made some civs less unique because things like Mace’s “quick siege push” strategy or Persia’s mass cav with health bonus is now no longer unique. While I agree a25 has more players playing with more strats this diversity seems to be a function of unit balancing and upgrade changes, which is distinct from civ diversity where I think we can still improve.

A24 was less diverse than A23, but the idea that A25 is less diverse than A23 is mostly wrong. I guess the idea comes from the fact that nonexistant bonuses were removed from the history page, https://code.wildfiregames.com/D2720. The only actual existant bonus which was removed is the Gaul and Briton population bonus, https://code.wildfiregames.com/D2950. It's also true that every civ getting a stable removed the uniqueness of the Persian stable, but I think that's an acceptable casualty for better gameplay. From A23 to A25 most civs have gained actually existing bonuses, only exception being the Britons who haven't yet gotten anything. The gameplay is far more diverse than it was in A23, which was just infantry spam with an occasionaly early rush. The Carthaginians might not have gained any direct bonuses, but they've also gained the most identity with the mercenary changes. I also don't get from where the notion that the competitive community is pushing for the game to lose civ diversity and how the competitive players are the reason that not enough civ differentiation is done. If there's no one there to make patches nothing will happen.

Hello everyone! I'm Nagasushi. Some days ago I tried to register a forum account, but unfortunately it didn't get approved, so I have to borrow this account from someone to make a post for my new mod Res Gestae. Please download from my Github link here or at the end of this post. https://github.com/Nagasushi2021/Res_Gestae Res Gestae is intended to be a 'small overhaul mod', which changes many aspects of the game without diverging too far from vanilla, or adding too many complicated mechanics that will be hard to be adapted for the future versions of 0ad. We endeavour to provided a balanced gameplay that will be attested by mathematical calculations and matches between AIs and humans. We will also aim to make sure that the AI included in this mod will employ diversified strategies and tactics at the difficulties that will suit everyone, from absolute beginners to the multiplayer pros. Furthermore, there is an emphasis on the tactics, strategies, and particularly on the viability of diversified gameplay styles. Also as the name suggests, we draw our inspiration from real world history, which means we will try to emulate the military tactics they used, their army composition, and more particular features of each civilisation. Outline of the initial version: Pathfinder: twisted pathfinder parameters in order to prevent unit overlapping and exceedingly smooth movement. Units are able to block enemies properly. Subject to future changes. Unit changes (only done for citizen soldiers, need more testing): unit balance, and various changes making tactics and micromanagement possible. AI: I have made a bot called Catilina based on Petra bot, and tested it with @Yekaterina. Currently the medium difficulty is roughly equal to a 1300-1400 level human player. Note that this bot is intended for testing rather than competing against human players at the moment. We recommend 'balanced' behaviour, and 200-300 pop, very low to medium resource, small to medium map size settings. It should work on any map not divided by water regions (e.g. mainland). If you want to see two Catilina bots fighting against each other, we recommend small Corinthian Isthmus map, since they prefer to head to the opponent's base rather than fighting against its army directly on other maps. Techs: Merged damage techs and added movement speed techs to encourage combined army. ========================================================================================================= 0.0.3 The first major update of Res Gestae: AI difficulties: There are nine AI difficulty levels now - I found the highest one most entertaining for myself. Note that the rating intervals are merely guidelines, which do not reflect your level in vanilla multiplayer. AI: Various improvements including use of towers, change of combat behaviours, adjustments for gameplay changes, basic support for tiny map and more. Diversification: Catilina has different behaviours in each match - it might rush or choose to attack at different time. Gameplay changes: Arsenal and rams are available for all factions in Phase 2, which encourages more diversified strategies other than booming and attacking when pop cap is reached. Consequently, phase 3 will give players much better options to boost economy and army strength (in this version some p3 techs already have reduced cost). Champions will be addressed together with civ differentiation in future updates. Techs: reduced cost for many p3 techs and phase3 itself. Units: slightly changed gathering rates. Rams have significantly more health and lower damage - siege will last longer and winning battles is much more important for both sides: attacking side should not overspam rams; defending side should not try to 'pick out' rams before defeating attacker's army. Buildings: economic buildings and palisades are much easier to destroy. Lower hack resistance for almost all buildings. Stones towers deal more damage and cost more resources - it should be a good option to garrison towers when you are under attack. Slightly better vision for all towers. Other changes: slightly changed formations. 'Random' draws each civ with equal probability now. ========================================================================================================== MOD IS NOW PLAYABLE. COMPATIBLE WITH ALPHA 25. https://github.com/Nagasushi2021/Res_Gestae Still a work in progress. Please report bugs and suggest balancing and gameplay ideas

No, it's secret

petra_extreme is a new mod that adds a higher level of difficulty to the AI Download

Second video: Macedonian side is using spear cavalries to flank Mauryan archers. In vanilla, it's better not to do this flanking manoeuvre. 1200603073_RgDemo4-1.m4v

Not true. It’s half the res with shorter walking distances. Only true to the extent metal is scarce, which isn’t particularly true anymore

Are sword cav op? Or are mercenary sword cav op? There's a huge difference between them. Mercenary sword cav beat spearmen confidently. Normal sword cav get destroyed by spearmen, even gaul sword cav get beaten by spearmen very well. There's a reason why you don't see people doing sword cav with the Athenians, Britons, Mauryas often.

Sometimes I feel like calling it free to play seems to imply there is something to pay anyway :P, maybe the lag is the price.

aI made a mod that implements my proposals on formations. I think the improvement is stark, here's a preview: Some detail: Assignment of units to formation places This is already very similar to the current algorithm, the only difference is point 3.2. I tried hard to introduce it, but, for simple that it sounds, I can't seem to make it work. Sorting the array doesn't seem to have any effect, I noticed it's always the same units that take the farther positions, those left out by the others. I'm attaching the js file with attemted edits. Also point 2 has seen an improvememt, similar to the one dealt in the next section. Rotation movement This had the greatest impact, in particular the second point. Makes formations a lot more usable I think. First point is dealt as in my last post of June 30. Column formation This was easiest. Not much to add about it. Further considerations and questions - I did quite some code refactoring, as much as I thought it would be acceptable. External use of some function may break, although it seems unlikely to me. - I'm not sure I respected coding conventions either. - Formations now don't get formed anymore in the mean direction of their members. - Browsing Formation.js history, I was startled noticing that actually my proposals are nothing new and already where in the engine some time ago (rP14292, rP14300). I'm not sure what to do with this information. - How is LoadFormation supposed to be used? - The only way to make formation turns more natural than this, is to change how entities turn around obstacles, so that they do not do it on position, but rather sliding around the corner as they turn. The improvement would be evident for formations, but would also be noticeable for rams and cavalry. I'm not sure where's the code for that. - I can keep making improvements if you like, my goal is to make formations good looking, and also reasonable even for competitive games, and I'd like my edits to go in the main game. Formation formation-mod-proposal.pyromod

I think the mace houses look sad: While the barracks look like one amazed dude and a stoned one.

Texturas para mujer lusitana; (Mujer lusitana civil Y NO GUERRERA); referencias; -La mujer civil , llevaría capa o un " chal " , diferentes peinados ,adornos en el cabello o en el cuello o brazos ,diferentes colores de cabello y la textura de túnica que hice sería una túnica de manga larga y falda que llega hasta por encima los tobillos .Las partes en blanco de la túnica cambiarían de color según el color de facción de los jugadores y jugadoras. Disculpen las molestias*

I've played 9 games of medium mainland or continent 4 vs 4 against Norse, Anglo Saxons, Carol. and Byzantines with ptolemies, mauryas,and Persians as allies to my Romans (I really like to win). There were zero crashes or error messages. The AIs were pretty matched to each other with no civs noticeably dominant. If anything weird happens in future games I will let you know.

I'm from Misery. Erm, Missouri sorry.

I've made bushes passable and destructible by buildings. They don't block pathfinding or construction. Used a mixin: <?xml version="1.0" encoding="utf-8"?> <Entity> <Obstruction> <BlockMovement>false</BlockMovement> <BlockPathfinding>false</BlockPathfinding> <BlockFoundation>false</BlockFoundation> <BlockConstruction>false</BlockConstruction> <DeleteUponConstruction>true</DeleteUponConstruction> </Obstruction> <StatusBars> <HeightOffset>8</HeightOffset> </StatusBars> </Entity> This prevents bushes in your base from blocking you from constructing buildings, which was a huge problem for India and other biomes that heavily use bushes.

Exactly:

What about shared troops? A teammate tells me via mumble that he garrisoned some units in one of my CCs close to his territory that is under heavy attack. While he is fighting also on the other side and thus already very busy, he would like to give me control over his units. I can already now ungarrison, but then I have to tell him they are out and he needs to take over. Therefore, I thought that maybe taking/giving control from/to allied teammates could be an option. There are surely lots of hurdles and special situations to consider, and maybe it's technically too complex, but I just wanted to bring this up - for a mod or in-game.

This mod adds the map "Mainland balanced" for a25. (https://code.wildfiregames.com/D4232) Thanks @badosu for fulfilling the community's interest in balanced maps by providing a nice bunch of balanced maps for a23 and a24 Currently, only the starting food surrounding players is modified. Also, straggler berries are not modified yet (which can lead to imbalances). And the biome only slightly affects the total amount of food, and it currently doesn't affect the berry/hunt ratio, this is something I will change later. I also removed the jungle biome, until it gets fixed, so you can pick random biome now. Alpine Mountains is also included (https://code.wildfiregames.com/D2830, ) Feel free to comment how you feel about current generation's gameplay, also you can suggest other maps that you would like to see balanced, which I might add if I'm not too lazy. Download here: feldmap.pyromod feldmap.zip Edit: for unknown reasons, I get an error uploading the zip file. Use pyromod instead

(https://code.wildfiregames.com/rP25869)