Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 2026-09-20 in Posts

  1. Our first Release 28 community mod is up on the 0ad mod downloader. you can also get it straight from the 0ad community mod gitea page (https://gitea.wildfiregames.com/0ad/0ad-community-mod) With this version, the goal was to tackle some relatively simple balance changes, some of which have been in high demand. Fanatics HP, hack damage, and hack armor reduced. Persian immortal HP reduced (both melee and ranged), ranged version damage and accuracy were reduced. Heroes may no longer be used to "bait" enemy units, as Heroes are removed from the preferred target class for all units. Champion cavalry and ranged champion cavalry HP reduced from 260->220 and from 220->200, but wood and metal prices were reduced. This, combined with speed reduction is intended to bring their population efficiency closer to infantry champions. Cavalry speed was reduced by 15%. Scout ship counter damage vs ships reduced from 3x to 2.5x, range reduced, and price increased from 50f 50w to 50f 100w. Foundation pierce armor increased from 10 to 20. (Foundations take 66% less damage from pierce attacks). Capture balance: Civic center capture points increased from 2500 to 3500. Fortress increased from 4000 to 8000. "Sentries" tower upgrade now also increases tower capture points by 50%. "Professional garrisons" fortress upgrade now also doubles fortress capture points. Scipio's Capture attack aura removed. See https://gitea.wildfiregames.com/0ad/0ad/pulls/8892 for more. Germans buffs: Champion axeman unit metal cost reduced from 100 to 80. Seeress damage aura range increased from 15 to 20. Seeress armor increased from 2->3 hack armor and 4->6 pierce armor they remain unaffected by blacksmith techs. Wagon encampment price reduced from 350w, 150s to 275w, 100s. Feel free to see the full changelog in game thanks to @guerringuerrin. As always, please give us some feedback about how these balance changes go.
    3 points
  2. Hi everyone, I've been looking into the possibility of creating Proto-Germanic voice lines for the Germans in 0 A.D. First, a note about AI: I used ChatGPT to help me find linguistic sources and prepare the first word suggestions below. This is preliminary research, not a finished translation. I'm not a historical linguist, and the proposed forms have not been independently reviewed by one. Some of them may well be wrong. No audio has been generated yet. My idea is not to reconstruct exactly what the Cimbri spoke around 100 BC. As far as I understand, the surviving evidence simply doesn't allow this. Instead, I would like to find a reasonable linguistic approximation that fits the historical setting of 0 A.D. and sounds good in the game. We only need about 18 short voice lines. Ideally, they should be one or two syllables long, but I don't think this needs to be a strict requirement. Before experimenting with recordings or text-to-speech, I would like to get the words and their pronunciation into a reasonably good state. 1. Which language should we use? Release 28 describes the Germans as a coalition of the Cimbri, Teutones, Ambrones and other Celto-Germanic groups. Official Release 28 announcement The linguistic situation seems rather uncertain. For example, Gilles Quentel discusses early contacts between Continental Celtic and Germanic. There are also different interpretations of the surviving names of the Cimbri and Teutones. Bichlmeier and Blažek discuss several possible etymologies of these tribal names in their 2020 publication. I think reconstructed Proto-Germanic could be a reasonable common language for the faction, as long as we make clear that this is an approximation, not a reconstruction of an attested Cimbrian dialect. There is also the question of the First Germanic Sound Shift and its chronology. For our purposes, I would initially use a consistent reconstructed Proto-Germanic pronunciation rather than trying to reconstruct a hypothetical earlier dialect specifically for 100 BC. Of course, I would be interested in other opinions on this. 2. First suggestions for the voice lines I used the English meanings from the Audio Voice List, with the Latin translations as an example: Audio Voice List – 0 A.D. Wiki The following is a working draft, NOT a finished or academically validated translation. All proposed Proto-Germanic words and forms are reconstructions, not directly attested historical expressions. Some of the specific forms still need linguistic verification. Most candidates were initially found through Wiktionary's Proto-Germanic reconstruction entries, which often refer to etymological dictionaries such as Kroonen or Orel. However, I have not independently checked every individual reconstruction against these books. I also used the freely available Proto-Germanic grammar by Winfred P. Lehmann and the IE-CoR linguistic database. Some forms are more tentative than others. I have marked the particularly uncertain ones instead of pretending that we already have a complete solution. Selection and greetings English Proposed form Notes Hello hailaz! Literally "healthy, whole". A possible greeting, but not an attested Cimbrian one. What is it? hwat? Simply "what?". Shortened for gameplay. My lord? frawjô? "Lord", without "my". The appropriate form of address should be checked. Movement and fighting English Proposed form Notes I will walk gō "I go / walk". I will fight fehtō "I fight". The meaning and exact form should be checked. I will attack! hwētō! "I attack". This candidate needs further linguistic checking. I will march! farō! "I go / travel". Not specifically military marching, but perhaps sufficient for a short acknowledgement. I will retreat! wīkwaną "To yield / retreat". This is still an infinitive. A shorter and grammatically appropriate spoken form is needed. Battle cry open Perhaps a non-verbal shout would work. Alternatively, a short expression based on a reconstructed verb for fighting could be considered. I would not want to invent something and present it as an authentic Germanic battle cry. Working and gathering English Proposed form Notes I will build timrō "I build". I will work land arjaną "To plough". The appropriate short spoken form still needs checking. I will gather samnō "I gather / collect". I will herd drībō "I drive". This could refer to driving livestock, but is not exactly the same as tending a herd. I will fish fiskō "I fish". I will repair bōtī "Improve / make good!" Not specifically repairing a building. The form and its use in this context need checking. I will hunt huntōn- Reconstructed verb stem only. The precise form and vowel length remain open. I will heal hailī "Heal!" An imperative rather than "I will heal". The exact form needs checking. Regarding hunting, the IE-CoR database gives huntōn- as its reference form, but its explanation also mentions hūnton-. The vowel length and the actual spoken form therefore need further checking. Other (I will put myself into) garrison — felhō Intended meaning: "I enter / go inside". This is one of the least secure suggestions and needs both lexical and grammatical checking. It is not an attested term for entering a garrison. A few remarks about the list The grammatical forms are not consistent yet. Some are first-person forms, others imperatives, infinitives or reconstructed stems. Personally, I don't think every response necessarily needs to be in the same grammatical form. The important thing is that it works as a short and natural-sounding acknowledgement in the game. However, we should make sure that the individual forms are actually plausible and not simply invented by an AI. Also, several suggestions deliberately use a broader meaning than the English original. For example, "I travel" instead of "I march" or "I drive" instead of "I herd". These would be gameplay decisions, not exact translations. I would be happy to replace any of these suggestions if there are better alternatives. 3. Sources Here are the main sources I found. Historical background Gilles Quentel (2012): Early Linguistic Contacts between Continental Celtic and Germanic: Lexical Aspects. Publication on ResearchGate Harald Bichlmeier and Václav Blažek (2020): "Cimbri" et "Teutoni". Journal article – Acta Linguistica Lithuanica Václav Blažek: On chronology of the First Germanic Sound Shift (Lex Rask – Grimm). Publication via DOI These publications discuss historical names, etymologies and linguistic developments. They do not provide translations of the 18 voice lines. Grammar and pronunciation Winfred P. Lehmann: A Grammar of Proto-Germanic. University of Texas at Austin. Complete online grammar The chapters on phonology and inflection are particularly relevant. R. D. Fulk (2018): A Comparative Grammar of the Early Germanic Languages. Publisher's page – Open Access e-book The complete e-book is freely available. I have not worked through the whole book, though. Vocabulary IE-CoR – Indo-European Cognate Relationships Linguistic database One useful example is the entry for "hunt": IE-CoR: hunt. It references Kroonen's Etymological Dictionary of Proto-Germanic and also illustrates why some details need further checking. I also used Wiktionary's Proto-Germanic reconstruction entries as starting points for individual words: Proto-Germanic reconstructed terms Some examples: fehtaną – to fight timrōną – to build fiskōną – to fish hwētaną – to attack These entries are helpful for finding possible forms and references, but they are not a substitute for checking the original academic literature. 4. What is still missing? Before recording anything, I think we would need: Someone with knowledge of historical Germanic linguistics to review the suggested words and their grammatical forms. A consistent pronunciation guide, preferably using IPA. Better solutions for the uncertain expressions, especially retreat, repair, healing and garrison. A decision on the battle cry. A way to produce natural-sounding recordings that can be freely distributed with 0 A.D. I know there has already been some discussion about AI-generated content in the project. I'm not attached to using AI for the final audio. Human recordings would be fine as well. For now, AI has mainly helped me find sources and put together this preliminary list. I would be interested to know whether AI-assisted linguistic research is acceptable for this kind of contribution, and what the requirements for the final recordings would be. 5. Questions Does this general approach make sense for the Germans in 0 A.D.? Would reconstructed Proto-Germanic be a suitable choice, or should we consider another linguistic approach? And is anyone here familiar with historical Germanic linguistics who could help check the proposed words and pronunciation? I would be happy to continue working on this if there is interest. Thanks!
    2 points
  3. Exciting news! I've finely brought this project to a testable and reviewable state. A big change since my last posts is that I've managed to make the performance impact minimal. The inertia system pay for itself and is kinda having 0 cost including the collision detection logic and other logic related to it. Having a lot of units that have the "charge" effect fighting is also demonstrated to be reasonable on performance with only a few percent increase in simulation cost for a given battle. This project have a lot of implications, and anyone willing to be testing the PR and giving feedback would help tremendously to make it move forward. If you are able to, please do. PR link
    2 points
  4. The Romans landed at Carthage.
    2 points
  5. The reason I follow every unique mod.
    2 points
  6. Trying Atlas I found a few things I wasn't able to manage properly (or wasn't careful or patient enough) such as properly connected wall segments and turrets. I finally started to write (with heavy support by Anthropic Claude) a little map analyzer/checker/converter tool, written in python, able to check the maps created with Atlas and offer options to correct issues analyze existing maps , also from older game versions, giving statistics, finding and offering to fix glitches (resource placed underneath a building or wall, trapped units, gaps in wall segments etc.) add a (poor) map preview if not existing or convert the Atlas screenshot into a preview file. converting and fixing older scenario and skirmish maps using the conversion scripts by @Stan` (e.g. renaming persian objects/units to achaemenids) I was only able to test on windows, it should theoretically work on Linux or MacOS as well (Python 3.14, pyQT6, numpy and pillow needed, see documentation). No real guarantee to always work (definitely NOT on random maps), but I was able to successfully convert a few great maps from past I found in the forum and play them. Note 1: Below screenshots illustrate the GUI and its capabilities. (They may not accurately reflect the current version in all details) Note 2: I only started experimenting with maps so I haven't seen all pitfalls by far. Should you have observed further typical mapping issues, I'd be interested to know and try integrating these into the analyzing and fixing section of the tool if possible. post-atlas-1.9.2.zip CHANGELOG.md README.md
    1 point
  7. @AsherThanks for your comprehensive review! Let me try and resolve things ... Was the mod that provided the missing resource for the map activated in your game (and saved) ? (if not, the tool does not see it.) This is a great idea - normally I would have thought that this is defined by the map creator in Atlas already, or on an existing map the map author has a specific scenario in mind (hence the name scenario map). Will integrate that - with that warning, though. In any case the original map is never modified by the tool unless you explicitly request that using the "edit map in place" button. Please clarify! That was a decision is because food resources are also part of what you will be building (fields, corrals). If you consider it useful we can certainly add natural food resources like fish, berries/fruit trees/edible animals etc. This could show a maps initial nutrition potential. Will change. Ok, got me - I used UK English and you are requesting US English. Will change. Had the same observation when I had installed the map already in the target folder in game. This is a logic bug. Will change. But wouldn't that potentially stop the process in the middle of something, i.e. in a non deterministic situation? This should then remove the product of conversion. Or do you want to stop the process when processing batches of maps after one map has finished befaore the next one is started? That's another bug to fix. The conversion from persian to achaemenid somehow was wrongly assumed to have happened pre-R0.28. Will change.
    1 point
  8. Another thing, I changed the current map, but on the convert page, the Test in Game button stayed the same, instead of changing back to Convert. Also, a stop button would be nice in the convert section
    1 point
  9. Also, it says in the Analyze section under Resources that food is not counted. I guess, why? Is there a certain reason why you didn't count it? Also, the tab Analyze is spelled wrong. It is currently spelled "Anaylse" (replace the "s" with a "z")
    1 point
  10. @Grautvornix, so I was getting some warnings and errors from a certain things on the map which weren't in the base game, then I loaded the game and the mods folder, but the warnings were still there. They didn't go away until I restarted the program. If you could make a button so you can refresh the errors. Also, if you could be able to edit certain things, like description, what civs the players are, if the players are bots or humans, ect. I think that would be helpful, so you don't have to have both this and scenario editor open at the same time, to make some of the smaller changes. Hopefully you don't think that I think this is horrible, it is just my feedback, to make it better; I think this tool will be a pretty usefully helpful
    1 point
  11. I might make another for this tournament @Atrik
    1 point
  12. Maybe @Alexandermb has some time, you might have to contact him via PM though so he gets an email or something.
    1 point
  13. Thanks! Very good - I'll take that on board. Oops! Good point as well. Needs to be changed. You are right, was just lazy and tried to keep it initially simple for me on a local repository. Will change that.
    1 point
  14. Good. Just give a name to the first percentage, it's salvageability, but maybe you can think of some other name. You could start with a 50% default for everything, to be fine-tuned later on if wanted (and food maybe could be ignored, because it's weird to salvage it). Incredibly complicated! And why? Why shouldn't walls and towers give a refund? Their stone was among the most salvageable resource. You said it yourself how things should be already, at least for buildings: And that's it! You later used the word "elegantly", then do it so: simple, no steps, no caps, no gaps, no radius, no more parameters, emulating existing processes, or their reverse. There you basically proposed to use unit(s) to unbuild structures, to be rewarded what I quoted from you at the beginning. Maybe I'm missing something, but I don't get why you would need ANY extra rule. What I quoted from you produces a simple rule: salvaging is unbuilding. For units, I can't help but keep saying that you don't need any extra rule! You use the same rule as with buildings: just unproduce them. Why complicate the ship rule with a radius, if you could just click a Salvage button on the ship, and then click a Dock, and all should be automatic from there? The ship would travel to the Dock, garrison, and get salvaged. All the radius thing is not simpler, not needed, not realistic, and not intuitive because the unproduce rule imitates that of buildings. Same with siege engines. Besides, you state you can dismantle (some of) them in one's territory, when one is not able to construct them there in the first place, incurring a logic gap. I agree doing so should be part of the game (with those big engines being extremely slow in return), but that's not yet there. When it is, yes, dismantle them wherever they can be constructed, to keep following the simple unbuilding/unproduce rule, but in the meantime it would be incoherent: the disassembly being realistic, while the assembly isn't. No. Scorched earth tactics should not be ultra-fast, that's exactly the point not to get the unsightly simultaneous collapse of everything (by the AI at least). What should be ultra-fast is deleting some building or unit that is bothering the player (I'm exaggerating with "ultra", it could take a very few seconds). The whole point is: you can use Self-Destruct, but you can't abuse it. The key is what I said: "only gets noticeable the more buildings at a time one wants to destroy". Thus, the best way to deal with all these and other issues at the same time seems to be modifying Self-Destruct the way I explained before (queue buildings, queue units in parallel if considered, and sequentially in each of both queues drain their HP at like 1000/s, etc), and all this has nothing to do with Salvage, there's no resource reward, because it's simpler and faster to execute.
    1 point
  15. Also, if anyone interested know how to animate, we are looking for charge animation (strike while moving) and staggering animation.
    1 point
  16. With a Pull Request you ask that your code be merged into the source code.
    1 point
  17. Hi! And sorry for the long reply. Yes, it's in sync with the projection matrix and culling mode.
    1 point
×
×
  • Create New...