Search the Community

This is a guide to help new players to choose which civilisation to play with, before each match. Pro players can ignore this. 1. Some general comments Civilisations in A26 are quite well balanced, especially with community mod, so there is no absolute best civ. The best civ for you is the one that suits your strategy / playstyle. Try to explore different strategies with each civ so that you get a good overview of what's available to you in each situation. If you haven't beaten the AI yet, try to practice with one civ until you have mastered it, then switch to others. 2. What makes a good civ: Being flexible in strategies: wide variety of unit types available. Can succeed in different terrains, biomes as well as naval battles. Strong economy: additional farming upgrades, gathering bonuses, etc. 3. Considering specific cases: Houses: Some civs have houses which increase your population capacity by 5, while other have that by 10. 5-house civs are generally more flexible in early games and gives your a slight advantage in wood if you want to research techs very early on. However, in late game, 10-house civs require much less attention to housebuilders and housing would unlikely be a obstacle to your population development. In addition, the building of 10-houses are more efficient as units have to walk less. Ranged units: in 0ad, the longer the unit's range, the less damage it does and the slower it moves. So javelins do the most damage per second while archers do the least. However, in some obscure landscapes such as gorges or densely built cities, the extra range of archers allows them to snipe the enemy without moving into the treacherous areas. This can minimise your losses and give you an advantage over your enemy if they only have javlin units. In addition, archers' additional range makes them perfect hit and run units; they can deal extra damage to any retreating enemy. However, in a prolonged confrontation on flat, open ground, archer's low damage will result in certain loss against javlins or slingers. Archers - longest range (60m-66m), walks slowly - not great for early economy but great for mountainous maps and urban fights in city lanes. Slingers - have extra crush damage, effective against buildings as well as humans. (45m) Can be used as replacements for siege weapons. Crossbows - Shoots a very high damage projectile every 3 seconds (45m-60m) Javlineers - high damage but low range (35m) - allows for fast economical development and wins you any close-range firefight behind the melees. Melee units: each type has a different use and no civ offers all of them, so choose wisely depending on your need. Melees are most often used as meatshields by pro players, to protect their ranged units who output the most damage. These values can be looked up in the structure tree. Swordsman - deal the highest damage per second but cost metal. The main damage type is hack, making them perfect against enemy siege weapons. Spearman - great againts due to their 3x bonus. However, they are less effective than swordsman at infantry and siege, although still decent. Pikeman - slow-moving but tanky units with double the armour of spearman and swordsman. Perfect meatshields but do little damage. Halberdier - Chinese variation of pikeman, stated between a normal pikeman and a spearman. Clubman / Maceman - deal huge crush damage; they can destroy buildings and siege weapons very quickly but are ineffective against other units. Champions, siege and heroes: if you are looking for a particular hero's bonus or a particular type of champions, e.g. elephants, then obviously choose a civ which has them. 4. Some personal recommendations If you are very new and have no idea what you want or what's ahead of you, Romans and Spartans are 2 good starting points in this alpha. These 2 have quite a simple structure tree so it's easy to get used to; they both have strong melee units and javelineers, allowing you to win any close-range confrontations against an AI. In addition, both have some strong champions for late game. Romans have an extra powerful model of catapult and entrenched camps which will help you in siege attacks, while Spartans have supercharged infantry units, namely the Skiritai Commandos and their heroes Brasidas and Leonidas. Their lack of archers is compensated by having bolt shooters. Stay away from Han and Ptolemies. Han is bugged in original A26 and has a very unique but complicated structure tree; their lack of javelineers and slingers will make defending against early attacks a bit more difficult. However, they do offer some very overpowered techs, heroes and the additional 10% maximum population in late game. Ptolemies' buildings are constructed very slowly, on top of that, being a 5-house civ, it's very easy for your development to be slowed down by the lack of houses. Also, their heavy reliance on mining also makes the civ difficult to play with. However, their buildings to cost much less than other civilisations, so you can save up wood for earlier techs and early infantry. Gauls are Britons can also offer very strong armies and rapid rates of economic development. However, they are more effective at killing enemy units than destroying their buildings. If your enemy decides to surround themselves with walls, towers and fortresses with swordsman inside, then it would be a challenge for Britons and Gauls to siege them. They are 5-house civs, which may or may not appeal to you over the 10-house Romans and Spartans.

This topic is started to discuss the civilization of the Norse and how it is going to be implemented in the game. Here will also be the final proposal. Description: The Norse of old were a north Germanic people who hailed from Scandinavia. During the early Middle Ages their regions expanded to Russia, England, Iceland and Greenland. They traveled to as far as Asia to the New World nearly 500 years before Columbus. Though feared for their fighting skills, they were also skilled traders and sailors. By the end of the Viking Age, which lasted from 793-1066 AD, their raids on the mainland faded, nonetheless they have left their mark on European culture and history. Gameplay: Norse don't have strong defences. Instead they (should) rely on keeping the initiative, expand fast and get hold of crucial resource spots (which is possible because they can build houses anywhere on the map). The house has a small ranged attack and can be built anywhere on the map, however they're a lot more expensive than normal houses. The citizen soldiers have a small speedbonus but are slow gatherers. Also the Norse lack cavalry. They have a couple of hybrid buildings (farmstead is merged with corral and Civic Center is merged with the fortress) and their navy is very versatile (see the line-up below for the bonuses they have) Unit Roster: Warrior (swordsman/axeman): http://wildfiregames.com/forum/index.php?showtopic=17918&page=4#entry280934 Spearman: http://wildfiregames.com/forum/index.php?showtopic=17918&p=281348 Hunter (Bowman): http://wildfiregames.com/forum/index.php?showtopic=17918&p=282347 Huskarl: http://wildfiregames.com/forum/index.php?showtopic=17918&p=282683 Berserker: http://wildfiregames.com/forum/index.php?showtopic=17918&p=282863 Navy: http://wildfiregames.com/forum/index.php?showtopic=18521&p=289163 Fishing ship. Knarr: Merchant, Mobile dropsite Karvi: combination but weaker warship / less trading income. Snekkja: Warship. Loot bonusing aura Drekar: Elite warship, Loot bonusing aura, Mobile dropsite, trains units Buildings: Longhouse (improved version of the house): http://wildfiregames.com/forum/index.php?showtopic=17918&p=283022 http://wildfiregames.com/forum/index.php?showtopic=17918&p=303012 Jarl's Hold (combination of CC and Fortress): http://wildfiregames.com/forum/index.php?showtopic=17918&p=288683 Farmstead (merged with corral): http://wildfiregames.com/forum/index.php?showtopic=17918&p=295275 Tavern (Barrack merged with Tavern, where you also can train Berserkers): http://wildfiregames.com/forum/index.php?showtopic=17918&p=291431 (left building in the concept) Dock: http://wildfiregames.com/forum/index.php?showtopic=17918&p=291806 Farmfield Palisades (Improved, stronger versions of the standard palisade) (since Vikings don't have stone walls) Outpost Wooden Tower Storehouse: http://wildfiregames.com/forum/index.php?showtopic=17918&p=309077 Market Temple: http://wildfiregames.com/forum/index.php?showtopic=17918&p=298492 Unique technologies: Clinker construction (Improves naval speed)

Download to test: https://github.com/JustusAvramenko/theban_greeks Ready for testing! Works with Alpha 24. Adds the Theban civilization to the game as a playable faction. They include 3 new heroes, 2 champions, custom actors, a fix for the plumed Boeotian helmet, 2 special technologies, a team bonus, and more! Will release on Mod.io in 2 weeks or sooner if all the bugs are ironed out!

I'm trying to set up a database for all civilisations (at least for mods as there chaos is great king). [This post will be updated.] Where to find: You see an old rusty gate with foreign inscripts. Pass through it. (the UI is not really functional yet, as no data exists) Terminology: - Leaf node: Mostly text. The final value. ----Civilisation----civilisation_file.xml:<root_element> <element attribute="leaf node"> leaf node.1 </element> ...<root_element>Functionality & Status:- Generate a civilisation or mod structure from an existing template, e.g. an existing civilisation or from a mod folder recursively (such that it has not to be created from scratch). - There is no fixed export filetype. Both JSON and XML can be output (to put into mods/<mod>/ folder). untested - The export target fileformat can be set on a per file basis. And changed even for already existing civilisation data. - Add new civilisation. - Rename civilisation, - Merge civilisations. - Add new File to civilization. - Rename file within all civilisations at the same time. - Move elements from one file to another. - Add new leaf element. (via xpath) - Insert/modify leaf node values. (good for researchers that don't have git or repository access) - Version control. not yet - Sorting (after Civ, File, XPath, or Leaf Value), - Grouping (after Civ, File, XPath, or Leaf Value), - Filtering (dynamic), - Option to apply changes to all occurrences in the whole database. <-- That's powerful, but also very dangerous if it goes wrong. - Option to modify equal values through out the currently filtered data rows.<-- That's quite useful as this way you can 1) filter the rows you wish to change. e.g. all occurrences of mesh_and_animation.v1.dae to mesh_and_animation.v2.dae within a certain civilisation.. - Updating the database civilisation structure by reading a template folder recursively when data already exists, creates new leaf elements automatically and shows in the civs that new elemets now have to/can be added/ are still empty and need to be filled. buggy Example: A new required element has been added, e.g. timetag/timerange. Now all civilisation data that not has this element yet, will have this added automatically (with dummy data, that can be changed thereafter). Targets: The target is researchers. Hopefully this later can be combined with a mercurial setup. I just have to add a button to allow researchers to commit their data.

Well, the main aim of this topic is not to make a discussion of why techs trees could be filled. The aim is making a collective resource for devs or modders, if they want to augment the number of units of units for civs, reducing the uniqueness of the rosters, but making them easier to balance (I'm for a asymmetrical balance, and the difference could be done in other ways, but as I said, focus the thread into filling the rosters). I'm not saying that we should add or not this units. At first I would use fast and superficial sources. Later If I have time or somebody does it, I would post better sources. My proposition is to make the design historical based, but not 100% accurate. For every proposal, a short argument or source. Not unique units, mainly common units and mercenaries (try to stick to historical mercenaries used for the correspondent civ) based on existing roles. The format is: role (based on existing ones): Concrete name Justification: and explanation if needed for supporting sources Source: Athens: (Fast) swordman: Ekdromoi Justification: It was a champion unit for the Greek civ before the splitting (now replaced by the Athen Marine). Could be the same that Spartan commando (c-s) or Gaul Fanatic (champion) Spartan: Slinger Justification: Spartan used slingers in their armies, for sure as mercenaries, and I don't know if they were also native soldiers. I don't know if were the helots who were used as slingers, like in Total War. Archer Justification: The same. Could be also Cretan mercenaries. Source for both them: https://uk.answers.yahoo.com/question/index?qid=20130703083325AACyja2 Pikeman: Periokoi pikeman Justification: by the III century b.c, pikemen were used by spartans. Now there's a scenario-editor only unit, and has been debated to give allow to train them by a reforms tech Sword cavalry: Hippeis cavalry Justification: Convention: most of the cavalry of the game, if I'm not mistaken, used javelins as a main weapon to fight infantry (unless chasing routing units or light infantry) and sword as side weapon, but devs give sword cavalry for most civs. Source for Cretan archers and pikemen: https://books.google.es/books?id=RLr8CwAAQBAJ&pg=PA29&lpg=PA29&dq=tarantine+cavalry+sparta&source=bl&ots=A-XsoU1zQ3&sig=I_smyZXsIO_j_SkVhaPBSDsATUM&hl=es&sa=X&ved=0ahUKEwjI0NDXlpTXAhXSFsAKHfcSCHUQ6AEIaTAL#v=onepage&q=tarantine cavalry sparta&f=false Gauls: Swordman: Justification: as it says in the original design doc, sword were used by celts, but mainly nobles. It could be used a narrow viewer to make them available as c/s Archer: Hunter Justification: Vercingetorix reunited hunters with bows to fight romans. Could be implemented as mercenaries, like Delenda Est. Britons: Swordmen: Justification: the same as gauls. Mauryans: Infantry skirmisher Justification: mauryan infantry was almost all made by light infantry, and used javelins Source: https://weaponsandwarfare.com/2015/11/10/the-mauryan-empire-military/. This source also says that mauryans used catapults, ballistas and rams! Slingers: Source: https://books.google.es/books?id=jpXijlqeRpIC&pg=PA30&lpg=PA30&dq=mauryans+slingers&source=bl&ots=RAdEwmEWZ6&sig=WyBgQ390GEkRCEiD3cw9auarmR0&hl=es&sa=X&ved=0ahUKEwiVoOaEm5TXAhWBoRQKHYjJBx0Q6AEIVDAK#v=onepage&q=mauryans slingers&f=false Persians: Slingers: Justification: Polybius said it, (II a.c) Source: https://books.google.es/books?id=C4A7DgAAQBAJ&pg=PT314&lpg=PT314&dq=Achaemenids+slingers&source=bl&ots=L5lL7a0O9U&sig=WdDtshe_OXpO5sfZxotqNcOZy1M&hl=es&sa=X&ved=0ahUKEwjuk9f_m5TXAhVEOxQKHbCBAS8Q6AEISDAI#v=onepage&q=Achaemenids slingers&f=false Iberians: I think that are pretty complete (in historical terms). But: Sword cavalry: Justification: Convention: most of the cavalry of the game, if I'm not mistaken, used javelins as a main weapon to fight infantry (unless chasing routing units or light infantry) and sword as side weapon, but devs give sword cavalry for most civs. Macedonians: Spearman: Source: https://en.wikipedia.org/wiki/Ancient_Macedonian_army wikipedia Republican Romans: Pretty sure that the roster its historically correct. Normal spearman could be used, not only triarius if wanted. But probably there's a lot of room for auxiliary units. Spearman: Rorarii Justification: https://en.wikipedia.org/wiki/Rorarii Sword cavalry: Justification: Convention: most of the cavalry of the game, if I'm not mistaken, used javelins as a main weapon to fight infantry (unless chasing routing units or light infantry) and sword as side weapon, but devs give sword cavalry for most civs. Carthaginians: Infantry skirmisher: Libyan skirmisher (citizien-soldier) Cavalry spear: Lybian or Carthaginian spear cavalry Source for both: https://en.wikipedia.org/wiki/Military_of_Carthage#Formation_and_structure Sword cavalry: Lybian or Carthaginian sword cavalry Justification: Convention: most of the cavalry of the game, if I'm not mistaken, used javelins as a main weapon to fight infantry (unless chasing routing units or light infantry) and sword as side weapon, but devs give sword cavalry for most civs. Lazy to do romans auxiliares and successors. If somebody have more sources and units, I will add them!

The first step in creating a new civilization is to create a unit, building and technology roaster. This roaster is also called civilization tree. The following link points to an example roaster for the Spartans: https://trac.wildfiregames.com/wiki/Civ%3A_Spartans The remaining question however is: how to balance the resource costs, life points, attack and defense points of units and buildings? Is this just made by try and error or is there any method to calculate all those factors?