Leaderboard

I can do those this time XD

ValihrAnt vs PhilipTheSwaggerless ValihrantVsPhilipTheSwaggerless.zip

In any case, Philip The Swaggerless has a point that it's not realistic for a ram or elephant to knock down a large section of stone wall. Check out videos of vehicles ramming brick walls. It usually punches a small hole in the wall, the same size as the object attacking it. So, more realistic would be: shorten stone wall sections to the same length as palisade wall sections.

After seeing the Github mod page and @Lion.Kanzen's Yayoi video I'm beginning to see some inconsistencies with the specific names. Time for a rewrite! Classic Japanese Tsukai typically translates to "messenger", so it's preferred to use -möti ("-holder, -wielder") instead Axeman: Onoduki → Wonomöti Spearman: Pokötuki → Pokömöti Female citizen: Josei (Sino-Japanese, NGです) → Womina ("young woman", as opposed to Omina "old woman") or simply Me ("female") Slinger: Isinagë → Tabutenagë ("throwing stone-thrower") Archer: Ite → Yumitöri ("bow-taker", first attestation in 8th century Hizen Fudoki, Ite is 10th century) Korean horsearcher: → Umanöri Mësikakapë ("horse-riding mercenary", verb meshi-kakaeru first attested in 17th century but both components separately are in OJP literature) Champions Axeman: → (Wono nö) Tupamönö Swordsman: → (Turuki nö) Tupamönö There are actually a few more words that mean "sword", depending on the description: Turuki or Turugi is straight and usually double-edged, Tati long and curved, and there's Sapi Naval Fishing boat: → Turibune Merchant ship: → Akinapibune ("trading boat") or Wobune ("small boat") Light warship: → Opobune ("large boat"), Yakata ("roofed boat"), Wobune ("small boat", as above) or simply Pune (how to define smaller/larger boats?) Farmstead: Kömëgura ("rice granary") Field: decide between Ta ("rice paddy"), No, Nopara, or stick with current Nora (all three mean "field" in general and are attested in OJP literature) Since Ba ("place") is first attested in 13th century, older Nipa ("place, field, garden") could be plausible Barracks: Sikömiba → Sikömi nö Nipa ("training field/place") Archery Range: Sikömiba → Ikusa nö Nipa ("soldiers' field/place") Forge: Kanutiba → Kanutiya (compare modern Kajiya) Outpost: → Mipari (noun late-19th century, verb miharu 9th century) Market: → Iti (first attested in Kojiki) Shrine can use Yasirö while Temple should be changed to Miya. Wall: → Kaki Gate: → Kado Turret: → Kakizumi ("wall-corner") or just Sumi ("corner"), didn't want to repeat the defensive tower nameYagura Arsenal: →Takumiya ("artisan's shop") or Tukuriya ("construction shop") Battering ram: Tukikömimönö ("smashing-object"), Pasira ("pillar"), or, if no other placeholder, Pa-zyau-tui (Hajōtsui) Ainu Village: → Kotan Wonder: Issei Temple → Ituki nö Miya, the generic name parameter can be "Ise Shrine" or for posterity "Ise Grand Shrine"; what's with the "Issei" autocorrect?

alreVsWeirdJokes.zip

For me, I'd like to see fewer arrows in the game just in general, and make each arrow more impactful. This would not only reduce the cacophony of sound during battle, it would help reduce range queries immensely. DE already does this (people ask why DE runs better while looking better than the base game; this could be one reason).

Do you want to do it @Lopess or me? If we both do it, there will be a conflict when committed. lol

It does happen to me sometimes but i later noticed sometimes wifi reboots by itself - it happens quickly you may not notice, it disconnects and reconnects. I dont think its a problem with 0ad, possibly your isp or router, Restarting the router manually may fix it. It does not only work this way with WiFi. It also works with ethernet connections, pieces of software, etc. Funny how in technology a bunch of things are fixed this way. When it comes to WiFi connections, the network adapter might reload the wireless connections profile. What also might happen is that your computer might end up without any connection since the DHCP server allocated an IP address to the machine at some point back in time and now the addressing scheme might have changed. Device drivers might also suddenly no longer be compatible with your operating system or even not work properly due to conflicts with other parts of the system. Wireless connections are prone to the medium and this might turn out creating the most varied connection issues on the network card. Which are not as easily detected or troubleshooted as in wired connections.

It is on my to-do list to build the 0AD snap on arm64, but I don't have an ETA to share yet.

Raspbian Unstable has A26 so I assume you should be able to compile it yourself at least. For flatpacks you need to open an issue on their github I'll point @oSoMoN to this thread

HI! IIRC there was some work about adding aarch to A26, but don't know its status. Maybe @Stan` has more information.

MarcAurel vs borg metadata.json commands.txt

Following change may break some mods: For security reasons planing to restrict access for ReadFile, ReadFileLines, WriteJSONFile, ReadJSONFile, ListDirectoryFiles, FileExists to the following folders/files: "gui, simulation, maps, campaigns, saves/campaigns, config/matchsettings.json, config/matchsettings.mp.json" adding "moddata" if some mods need to access and ship custom files that don't fit into other locations mentioned above (https://code.wildfiregames.com/D4617)

Maybe ancient aliens visited the Macedonians to give them advanced technology before the other civilizations.

That was the purported reason--you could create a thicket of extremely strong towers. I never saw it done, though. Even if it did happen, a much better solution would've been to limit how closely they could be placed next to each other. Eliminating features is just a lazy way to 'fix' something that could otherwise be properly adjusted.

Palisades are built in smaller segments than stone walls. When a ram attacks a palisade, it attacks the edge of the palisade, the center of the palisade, and the other edge of the palisade. Each part of the palisade has 700 health, so an un-upgraded ram, dealing 150 crush damage, will need at least 5 hits to destroy each part of the palisade. Having destroyed a section, a tiny bottleneck of soldiers can then follow the ram through, but they are especially vulnerable to the defending army since they must squeeze through a small space. (Another trouble for the invader is that soldiers (especially ranged soldiers) get distracted fighting the palisade and do not immediately stop when enemy soldiers come into range) Stone walls are built in larger sections and of course have more health. But once the main section is destroyed there is a large gap for an army to pass through. I think palisades are too strong versus siege compared to stone walls and the main issue is that they have smaller sections that each need to be destroyed. I propose that the length of the middle section of palisade walls be extended to the same length as the stone walls.

There are lots of 50 unit army pushes now. It’s the most common form of inf rush. Hiding behind a CC is basically the only way to defend if you aren’t already prepared. This very frequently happens in 1v1s that last long enough for one player to reach 100 pop If you lose your only CC in 1v1 it’s almost certainly gg. The connection you are trying to draw between cheaper CCs and CCs’ defensive abilities is strained. To the extent your concern actually is valid it should be dealt with by increasing the difficulty of making a new CC (ie increasing cost or build time). You’re making a ton of assumptions based on things you think (but don’t know) will happen. If any of your assumptions are wrong it could eliminate the utility of an entire unit class (siege), frustrate the entire purpose of making CCs cheaper, and change the entire meta to something unknown and different.