Leaderboard

Hopefully in the next few alphas we can get some of that historical stuff into the game so you all can learn more.

There is a blog article about it here: https://www.comitatus.net/greekbellybow.html Although it is not really related to the Macedonians but to the Greeks in general, it is a real ancient weapon. Edit: There is a plausible evidence for its use in Macedonia in the 2nd century BC: https://www.academia.edu/31610915/Perimortem_Weapon_Trauma_to_the_Thoracic_Vertebrae_of_a_2nd_Century_BC_Adult_Male_Skeleton_from_Central_Macedonia_Northern_Greece_2004_Death_from_a_catapulted_bolt_head_Journal_of_Paleopathology

In option, you define what color you want to steal, then every game you aren't this color, yours will be swaped with the player who has the one you want (As well as you customizing this color in the first place ofc) Example: Set color 1 to your favorite red, then set "Replace Own Color" to 1.

I'd honestly rather it be something in the game world rather than an options menu item. But either way, that would be ideal. But to make either option attractive, we gotta rebalance capturing vs. attacking.

Ideally yes.

This eventually worked. The topic can be closed.

prt_dock.zip

For years after it's introduction, we got asked to make attack the default. So we did. There might be some info here https://code.wildfiregames.com/D4697 but else digging on the forums might help

Capture is no longer the default, you need to press the C hotkey to make units capture in this version.

The word "Germani" is first popularized by Caesar, he used it to group a large population under one label and he built a narrative with it. There is a debate among scholars to know if Caesar was really the original source, maybe Posidonius of Apameia was the actual original transmitter of the word. But there is no consensus. Furthermore, there is a plausible hypothesis where Posidonius transmitted the named "Germani" to specifically speak about a tribe, not a large group. Tacitus mentioned that the name was originally applied to the Tungri only, then it has been generalized to others. Maybe Tacitus was relying on Posidonius because Caesar doesn't mention the Tungri. Caesar mentions the Aduatuci, the Condrusi, the Eburones, the Caeraesi and the Paemani as being commonly named Germans. Which is interesting because the Tungri could be another name of the Aduatuci. Finally there is something interesting in relation to the Cimbri here: The Aduatuci are a remnant of the Cimbri and Teutones who tried to invade the Belgians and failed. This is explained by Caesar. So the descendants of the Cimbri and Teutones could have been called Germans a few decades after their wandering. Thus, the Romans did call a large population Germans. German is not a label the tribes used to call themselves, but so do is the name Gaul. The concern with the name Germans and its correspondence with present-day Germans dates back to the Second World War and the Nazis' use of the Germanic theme as an ideological justification. But at no point is anyone going to make the same criticism of the use of the name Greek for the ancient populations of Greece when the Greeks of today bear the same name. The same goes for the Egyptians, the Chinese, the Belgians etc. I don't see why today's Germans should have exclusive use of this name. What's more, the problem only exists with English, and the world does not revolve around Anglo-Saxon countries alone. ‘Deutsch’ in German. ‘Allemands’ in French. ‘Tedeschi’ in Italian. ‘Alemán’ in Spanish. For me, the only problem with the Cimbri is that they come into conflict with a future faction of the Germans and that they're a single, relatively unknown people. The concept seems interesting, although I haven't tried the faction out yet. If we rename the Cimbri as Germans, it is fine for me. Although it is a bit sad to reduce the Germans to a single tribe.

It is not the case for A27, but in the future it may happen that a new 0 A.D. version will change the metadata.json replay file structure, f.e. adding, removing or replacing data. Then, LocalRatings will need to update its logic too, to reflect the new metadata structure. In other words, future replays may not be compatible with today's replays - at least from data extraction perspective. There is also one more consideration: the "interpretation" of ratings may be different from version to version, due to balance adjustments and gameplay changes. For example, a parameter that was relevant in A26 may not be relevant in A27 anymore and viceversa. So the interpretation of ratings would change too. For these two reasons, I am in favour of distinguishing the two versions.

There is no ETA. For now your best bet is to keep trying. Hopefully you'll be faster than the dDOS IPs

Ouch… That explains it. I'll refrain from trying again in a while to give admins a chance to fix the issue then. Can I be notified here when it's safe to try again? Thanks!

Thanks Mentula. Excellent work. I used your code to replace legacy color replacements code from boongui. @Seleucids here is a version for you customcolors+.zip

An official appimage is planned, but in the meantime I personnally trust @andy5995 We also made the flatpak official just a few days ago. It's as native on Windows than it is on macOS, BSD, Haiku and Linux. It's just that the distribution of the most performant version is a bit slower on Linux it's out of our control. We could wait for the maintainers to release but then just like when the trailer leaked, we'd get confusion in the lobby if they take 3 months like A26.

Han farming techs have been adjusted https://gitea.wildfiregames.com/0ad/0ad/commit/5dcef8c17a11c52817bbfb44b569cc8d29adde4a If P0 is the productivity of the first worker, then Pn would be the productivity of the (n+1)th worker I think. AI still has ways to go

Thank you @hyperion, your solution worked. Below are the fully updated build instructions for anyone who is having similar issues: 1. Install the build dependencies as specified in the dependencies section https://trac.wildfiregames.com/wiki/BuildInstructions But on top of this, you will need to install cxxtest, python-virtualenv, python3.10, git-lfs 2. Download the source code from Gitea; the SVN source resulted in permission errors. Run all commands in your terminal: git lfs install git clone https://gitea.wildfiregames.com/0ad/0ad.git 3. Enter the downloaded folder and create a Python environment there. I named my virtual environment 0ad_build. cd 0ad python -m virtualenv 0ad_build --python=python3.10 source 0ad_build/bin/activate 4. Now you are in the activated Python 3.10 environment. Build the libraries under this environment: ./libraries/build-source-libs.sh --with-system-cxxtest You can add a -j$(nproc) flag to speed up things at the cost of your CPU consumption 5. Workspace update: ./build/workspaces/update-workspaces.sh --with-system-cxxtest 6. Making: cd /build/workspaces/gcc/ make 7. Running: cd ../../../ binaries/system/pyrogenesis We can put this into a full build script for your convenience, see attached .sh file. Don't forget to chmod +x 0adbuild.sh