ChronA

Create new variant XML files for each new animation in ...\art\variants\biped and ...\art\variants\quadraped for infantry and cavalry respectively. The actual animation sequences should be copied from existing sword swinging and sling throwing variants. That will save you from needing to make any new animations with Blender. You might need to create a few extra variants for each action to accommodate units with differ sized shields. Add the proper new <variant> tags for each new action to ALL the actor XML file... FOR EVERY SINGLE UNIT IN THE GAME!!! Add code to the Component files (...\simulation\components) for UnitAI.js, Attack.js, (plus all the other combat components that interact with them) to allow units to know when and how to use their new attacks, and what to do when hit by them. Add new attributes to the unit-template XML files to set the speed and damage for the new attacks according to the syntax you set up in the Component files. I'm probably forgetting something, but that's what I remember from last time I looked at doing something similar. Needless to say it is a tremendous amount of work, and unless you are actually a god-tier coder you should recruit help if you are dedicated to seeing this idea realized. Don't try to do it all on your own. It will take ages, and there is a good chance the next update could wreck all of your work before you even release it. Work smart by communicating with the main devs, sharing the burden with collaborators, using version control software for everything, and pacing yourself. This will protect your work and mental health in the long run. Other than Hyrule Conquest and maybe that one Pony mod, I don't think anyone else has ever attempted a renovation of this scale in the last 10 years. But it can be done if you are smart, persuasive, and committed to seeing your vision through. Good luck and best wishes!

Exactly, the West (past, present, academic, and lay) absolutely has its own closet overflowing with skeletons where misrepresenting historical evidence is concerned. But that can't mean everybody gets a free pass to keep doing the same. It means we all need to be more critical about how we source and interpret our history. I admit I used this opportunity to rib AIEND for their country's instrumentalist attitude to these matters, and that disrespect deserves some calling out. However, I can't apologize for trying to point out a cognitive bias in others when it contributes to erroneous reasoning. Where the situation reversed, I would appreciate someone else pointing out a potential cause of my mistakes even if it temporarily hurt my ego. I think that is the only realistic way to deal with these things, and anyone who can't take the heat of having their biases examined should be ready to occasionally take a break from the kitchen.

Chinese textbooks are the one infallible authority on any question of historical truth. /s Snark aside, there is a kernel of truth here that any absolute statement about the gear and tactics of an ancient military unit that operated over hundreds of years is likely to have counter examples. In early times these were people acting as military emissaries of a distinct ethnic group , and later an evolving military company shaped by the traditions of those forbearers as well as the organizational and operational requirements of their own circumstances. They were not inanimate weapons systems, like a particular model of rifle or tank. They could and would change their gear and tactics to keep up with changing times and situations. That said, in a game like this there needs to be some some sort of typical representation for a special unit like this that is functionally distinct from other units. We can quibble about their precise representation, but I think the choice to draw them as elite medium-to-light-ish melee infantry is representative of their most celebrated exploits. (As attested in the accounts above.)

Gameplay wise, what differentiates corrals from farms? I've never given them much thought personally, but presumably the player gets something like 2-10 times more resource generation per unit time, and a hugely reduced territory footprint, and in exchange for much more micromanagement. The first thing to ask is whether corral management represents a distinctly fun skill challenge. Is it engaging? Does it reward the player's attention in a different way from farming? Secondly does it create a distinct set of strategic considerations? Like could provide players with reduced territory footprint with a comeback mechanic? A way to get food from land that is unavailable for farming (because of terrain, or auras, or threat of attack)? Maybe it makes cavalry more cost effective by allowing them to participate in food generation? If the answer to both these questions is no, the feature should be cut. Otherwise any buffs should ideally be concentrated on intensifying these differentiators.

Is there a link on the wiki? I've looked a bit for that sort of info for 0 AD (because I would like to have larger projectile models so I can tell who is shooting who) and I've not found anything.

I think this misses the point of the complaint. The ability to rescale things DOES already exist in the 3D modeling software, and that is great for those who already know how to use these programs and want all that extra flexibility. But for anyone who doesn't know how to use Blender it is a huge impediment to their ability to mod the game. There are a bunch of potential applications where the ability to easily grow or shrink game models without changing any animations would be helpful: like larger projectiles so that its actually possible to see them in flight. Or ships and units that actually match the dimensions of their collision footprints. Or an AoE style tiny trees mod. These become huge projects if every model must be rescaled and exported from source, but would be almost trivial if there was just a number in an xml that could be adjusted in on the fly with a text editor.

You're headed the right direction. The biggest problem with the source image is that the facture pattern gives away the scale (very small). Sharp edges like that melt or even sublimate away really quickly. So stable, geological-scale ice that has been around for a while rarely presents such abrupt, jagged reflection edges. I think you might experiment with applying a bit of blur to give the surface a more smoothed-away look. I'd also suggest trying to add a few little traces of snow drifts. Like, when it is very cold for a long time, snow particles blown by the wind get snagged in little cracks in a standing ice sheet, and then more snow gets hung up on those particles forming little dune-like drifts that follow the course of the original crack. Don't overdo it, but a few spots here and there might help sell the scale of the ice sheet more. Those are my suggestions, but no guarantees they are any good. I'm not an artist of any sort. Just a yearly admirer of winter landscapes.

That is a fair counterpoint. There might be some room to debate whether those skirmishes (if they are decisive) are actually so small that LOLN breaks down, or if they are just protracted exchanges still involving hundreds of projectiles but now spread out over a few minutes instead of 30-60 seconds. But I admit I lack the experience base to evaluate that question. Also I do agree with the concern that slower projectiles could throw of the balance in a major way, as it opens up a new avenue for systematic counter-play that could change the balance of tactics in unpredictable ways. (Dancing!) Also, with fewer, chunkier projectiles there could be problems with overkill weirdness. Like if previously it takes 10 arrows to kill a unit and 50% of the last arrow is overkill, that means 5% of the unit's DPS is wasted. Where as if it only takes 2 arrows with 50% overkill on the last shot now you are losing 25% of your theoretical DPS. Because of issues like this I would actually agree that any changes to attack rates should be lumped in with a general rebalancing of ranged vs melee troops. No sense doing the same work twice. (It helps that a melee buff is sorely needed if 0 AD is to have any pretenses of being historical.)

Unlikely it would cause any noticeable difference with respect to <Accuracy>. The Law of Large Numbers applies because, even with a reduced rate-of-fire, you are still flinging hundreds of projectiles over the course of a typical battle (most of which hit something). That is more than a large enough sample size to push the tendency very close to the theoretical expectation. In intuitive terms, yes misses would be a bigger lost opportunity, but the projectiles that do hit balance it out by having a proportionately larger punch that almost exactly makes up for the damage that is lost. Plus, I don't think the threshold of "game breaking chaos" is nearly as sensitive as this objection makes it out to be. There are a bunch of really unpredictable factors in 0 AD's combat already: e.g. not being able to tell how many units are in an enemy formation due to the obscene model overlap, or the way that promotions can randomly change a few lucky units' stats on the fly. Despite this, I don't hear anyone complaining that the combat gameplay is unskillful.

Every aspect of combat in 0 AD (and most other games like it) is tremendously abstracted. If you hypothetically wanted to simulate the process of attacking buildings in more detail I'd vote to go all out: with actual fire propagation spreading to other nearby buildings, attackers adding more torches to make it burn faster but not actually doing damage, and defenders "repairing" the building by throwing water on.

This is the kind of thing I'd like to be able to help with, however I've currently got other obligations that require my full attention. It would be really irresponsible for me to get back into 0 AD right now. Instead, let me just try to assuage you to consider giving it a shot yourself. Modifying unit stats in 0 AD is trivially easy. The hardest part is probably just setting up a new mod, but even that is pretty straight forward.

While I remain an advocate of big structural changes for 0 AD, at this juncture I think restraint would be wise for this mod. With the brand new alpha no one knows yet what the current crop of balance problems will be (even if we have some guesses). Rushing into a set of features that don't reflect the current balance zeitgeist, or worse create entirely new problems on top of the endogenous deficiencies, would risk discrediting the project. Plus there might be governance problems in these early days that would be easier to sort out before real balance politics begins. Better to wait a month or so to see how things shake out with alpha 26. Maybe start collecting proposals, drafting design documents, and organizing in the mean time.

I just meant that alre's comment that (to paraphrase) "back in alpha 24 it was important to stream reinforcements" would seem to imply that in alpha 25 (and maybe the in development alpha 26) it is no longer vital to stream reinforcements like it used to be. I haven't kept up with the evolving 0 AD meta during alpha 25 unfortunately--haven't had the time--so I too was kind of hoping they would elaborate. Do they mean that the technique was more popular back then, or that some of the more prominent players made very good use of the technique at the time, or that alre personally has just not played that way a lot or maybe played many matches in general since a24? Certainly nothing about the game appears to have changed that would alter the foundations of gameplay so profoundly! The idea that continuous reinforcement is suddenly no longer required to sustain a push or was a special property of a specific alpha is very odd, I agree.

That's not quite the same thing as friction of war; actually it's kind of the opposite. Although it is definitely a good thing to incentivize streaming reinforcements, and the covert implication that this might no longer be the case is worrisome. Friction is basically the idea that the deeper into enemy territory you get, the less effective your military assets become. When this is the case you don't actually want to follow up your attack with a stream of reinforcements to push deeper into enemy territory. You actually want to pull the attack group back and link up with the reinforcements in the previous no-man's-land so together they can consolidate the gains by either fortifying the newly claimed territory or attacking on a newly exposed flank. To really appreciate the distinction, look at the difference in tactics between Starcraft Brood War (a high friction game) and Starcraft 2 (a much lower friction game). SC2 features a lot more all-in deathball-style battles and decapitation base trades.

Source? Tree derived fruits and nuts like olives, figs, and acorns were staples of the diet in various times and places. Medieval Europeans and even the neolithic native-peoples of the Americas are well documented to have practiced managed forestry to cultivate and harvest lumber, firewood, and hunting lands. It would be pretty weird if none of these people ever realized that putting tree seed in ground makes new tree grow, and took "commercial" advantage of that fact.

True, but a savvy balance designer could counteract this tendency by increasing friction of war (https://www.army.mil/article/185864/fog_friction_and_logistics). The best examples I've found of this being done successfully in the RTS space are in Starcraft Brood War and in Supreme Commander (and other TA-a-likes). In both of these games the normal re-max time is 2-3 times longer than the typical main base to main base rush distance. That would normally mean that whoever gains a decisive local advantage, namely by one-sidedly destroying the enemy's army, ought to snowball very quickly into a total victory. Just walk your surviving army and reinforcements over to the enemy base and win every subsequent engagement by virtue of Lanchester's square law. The reason this doesn't work in the above games (compared to some other games of note) is that fighting a series of (even individually advantageous) battles disconnect from resupply infrastructure exposes the player to an exponentially compounding risk of cascading homeostasis failures. The reasons for that are specific to each game, although there are some common factors: namely imperfect pathfinding and unit level target acquisition, strong counters, glass cannon units, strong static defense, and a heavy dependence on exhaustible meat shield units for composition effectiveness. For Brood War, add also the stringent limits on unit selection and control making perfect micro impossible, economic micromanagement demands, and the indispensability of vulnerable and exhaustible spell casters (i.e. High Templars, Arbiters, Defilers, and Science Vessels). For Sup Com there's the slow movement speed of units (and projectiles) compared to typical engagement distance making it hard to extract units from danger once they fall into it, and the asymmetric ability of the defender to salvage resources from battlefields. The end result in both games is that any blitzkrieg-style, decisive attack will almost always get bogged down and picked apart before it can cause game ending damage. Consequently the normal path to victory becomes a sustained campaign of incremental pushes, flanking maneuvers, and raids, rather than one big game ending battle. Could 0 AD do something like this. Maybe. Static defense could be buffed. Heroes and other support-or attack-role aura sources could be more effective. The role-differentiation and indispensability of melee infantry infantry as tanks, and cavalry as assassins could be boosted. Defensive building auras could play a bigger role. Time to kill could be lowered. Etc. The trick would be balancing it against the rest of the game design. Raids need something valuable (but not indespensible) to raid in order to prevent the game turning into a lane pushing tug of war. Game feel needs to be preserved. It could be a very big project.

This is very promising. While (understandably) this does not go as far as some proposals, it does open up a new, more streamlined pathway for balance provocateurs to submit modifications to the game and then test the effects of those modifications without jumping through loads of technical hoops. I tend to have more confidence in technological measures that change the facts on the ground pertaining to a problem, over "community initiatives" that call on individuals to adopt a new paradigm without addressing any of the incentives that produced the situation in the first place; and this solution does a bit of that. So... merci and bravo! Whether this will be enough to break some of the gridlock in 0AD's balance development I cannot venture to predict. Probably it will not fix all the problems in one go, but so long as the community maintains realistic expectations, the contributors remain committed to an incremental campaign of periodic improvements, and the main developers are open and supportive to increasing integration with the main mod and other balance-adjacent endeavors in the future, I cannot see this being entirely fruitless. As to the poll questions: would this be enough to get a vocal complainer like me to get off the benches and contribute some skin to the game? I think the answer is yes. This answers many of my objections about barriers to working on balance improvements. I've got some stuff going on right now that would make taking on another project hard, but once that is done I would be open to contribute, insofar as I am competent to. I agree with Lion that discussions must be had about the intended scope of this project. Is this to be focused on minor adjustments to specific balance issues, or will it be open to more radical reimagining of established unit roles and gameplay conventions? (Someone working on fine tuning archer balance is going to be pretty angry if someone else comes along and completely resets the balance relationship between melee and ranged a week later.) Best to have a plan, and maybe (gasp) a design document.

Or collision circles really need to be increased... and if that requires reducing unit counts so the engine will remain performant then so be it. What is the point of having 800 units on screen if you cannot clearly see a single one of them because they all congeal into a single undifferentiable blob of human neutronium?

For that they really need a unique role of their own to fill, separate from skirmishers and slingers. Right now all range infantry are just DPS sources. One of the three types is always going to be better at that than the others unless you make all their stats exactly identical. If they had different roles though, like if archers had bonus damage vs cavalry (there is some historical precedent for this) and skirmishers had extra hack armor on account of carrying a shield everywhere, and melee were actually viable DPS dealers and not just meat armor, you would no longer be comparing the two directly to each other because they no longer would be directly competing. Of course that would require actually designing the game around functioning counter cycles rather than pop-history.

You've got me there. I agree.

Correct. Likewise to remove resource gathering is <ResourceGatherer disable=""/>

I don't think archer are supposed to be able to fight or escape from a charging mob of javelineers, they are supposed to beat them by staying at standoff range with a meatshield or buildings protecting them from the enemy. If archers could also kite other ranged infantry that would once again turn them into a very hard counter to all infantry units, which does not seem in the spirit of 0 AD. Plus a speed change would boost their economic value and create chaos for civ balance (again).

- Persian women have a bow to defend themselves rather than the conventional dagger. Agree. I feel in general that civilians being melee instead of ranged in 0AD is a nonsensical Age-of-Empires-ism. Giving Persian women their civ's characteristic ranged weapon makes sense to me, and is unlikely to cause problems so long as their combat stats (i.e. the damage of their arrows and maybe their range) are not competitive-for-cost with proper CS archers. And they really should not be, because CS archers would be using proper war bows while civilians would only have hunting bows. - Archers are more accurate than other archers and advance in rank faster Slightly oppose. This is a good suggestion in concept, but as others have pointed out Archers are a recurrent problem unit for balance, and somewhere down the line someone will need to readjust them. Persians having a unique variant will make that person's life very slightly harder. That said, it might still be worth doing. This is one of the most "on-brand" buffs the Persians could get. - Decreases the attack of citizen spearmen considerably, but increases armor pierce. I think there is a much better way to do this: Step 1. Decrease the Persian CS spearman's cost to say 50 Food 30 Wood (because their wicker shields did not require high quality lumber) Step 2. Decrease their attack by 50% and reduce their hack armor from 5 to 3, but leave their HP and pierce armor unchanged Step 3. For eco balance, drop their resource gather rate by 20% to compensate for being able to have more of them. This would make the Persian spear line into a stronger pierce-tank role for cost as you suggested, but better fitting to the historical assessment that Persian infantry were inadequately armored compared to their Greek adversaries and compensated only by weight of numbers. It would also have some interesting late game implications. These spearmen would be slightly supply inefficient, so Persians would likely need to switch to champion Spearmen as they approached pop-cap. Persian CS infantry would also be much weaker to melee cavalry with this change. This might force them to compensate by focusing more on cavalry vs cavalry, which would be an interesting variation to the meta IMO. (It could also just make them completely non-viable vs cavalry, so be careful! That goes for your original variant too.) - All Persian cavalry are available in the CC, except champions. + All Persian CS cav are available in P1. I do not feel like I have a good grasp on the balance of factors for and against cavalry effectiveness in current 0AD, so I cannot predict how this would effect the meta. It seems like other people have concerns so I defer to them. Maybe just proceed with caution.

<Builder disable=""/> I think adding this to your Man At Arms unit's XML template file would do what you want.

Counter (counter) salt! Complaints that a project prioritizes graphics or performance or whatever other area of development over balance are not properly understood as criticisms of the people working on graphics or performance. They are criticisms of project managers for failing to onboard people to work on the problem area. The old fallacy that end users have no right to criticize creators... but let's ignore it and actually dig into that situation. About a year ago Stan chastised me for exactly this, and I thought "Hey they are right! Why complain when I could help fix things?" However as a I dug into what that would actually entail, I quickly realized that the time and effort that would be demanded of me to make a useful contribution were far beyond my current capacity. I'm not in any way a professional developer. (But even I know about GitHub at least.) Like Crynux said, you guys are using this arcane combination of outdated technologies to do your development; and it gatekeeps (irrespective of your intentions). It would have taken me days of very trying consultation with Stan to get up to speed. And then what after that? As has been noted time and again, the 0AD community is profoundly reactionary. What is some no-name noob actually going to accomplish? Spend hundreds or thousands of hours coding and advocating for changes that will be tried once and unceremoniously rejected? No. This is my contribution: to be a cranky wall of text that shines a spotlight on problems and options no one else is discussing, to lend support to minority perspectives and underserved users, and sometimes even to light fires when the forest is desperately in need of a proscribed burn. If I can nudge you or force you to make the hard choices, I will consider that a valuable contribution. So far I do not feel I have succeed, which is why I have no qualms about amping up the pressure of my rhetoric. Well, the truth is 0AD does compete with paid products in the hearts and minds of its community (yours included). We care about whether this project ultimately succeeds--whether it eventually attains a polished and feature complete form--because we are all dreaming of someday playing a good community-made ancient warfare RTS that actually respects history, instead of the dreck Microsoft spits out every year to earn a few more dollars. Is that so impossible? (And lest you forget, we are actually paying for the privilege... crowd funding it if you will, not in money but in time and attention. To many of us these are much dearer commodities than the mere $60 that AoE2:DE and all its DLC sell for on Steam.)