All Activity

@Asher Thanks for the testing! Oh! Which type of templates are these? Any specific or just some? Good point! Will change that!

This and @Eilat's Modern warfare mod make my think of my latest general suggestion: That is, for this Galaxy example, could one have many maps "running" in parallel, representing many planets? And another map could connect it all, which instead of water and ships would be space and spaceships, and when arriving to a planet, one arrives to one of the other maps. Seems to me that maybe with quite some tweaking it could be achievable?

Is it on github or something, @Lopess?

I'm not sure what you mean by "mini", it wouldn't be actually "smaller", but "lighter". It should be the same as current ramming ships, but faster (thus maybe deal more damage), while taking more time and resources to produce, and have less garrison slots (all aligned with what was an attested Athenian advantage). Surely these things can be changed to something that's champion level but not OP? There's that idea of no garrison slots at all and to categorise such machines as "champion", to give a clear indication that they are full-time combatants, not really transport. Indeed, radius increase and/or healing per second is a good choice, considering how influential that was. Yeah, "City Guard" sounds like a guy lighting up street lamps at night... Chosen Athenian seems the strongest contender, and closer to what's attested.

@Chasca it's real lmao I was there,can confirm

Corrections of what is wrongly done in vanilla should apply to vanilla. Changes of what is not quite accurate in vanilla would also ideally apply to it, after gameplay considerations. Additions of what vanilla doesn't have in the first place could of course be considered, or just left as mod material. I tend to mention interesting or important things I come across, independently of any gameplay considerations (that part I leave to others).

@Thalatta I assume you are talking about delenda right? since the vanilla doesn't have... like, half of these things in the first place. other than that,yes these are mostly name or design changes and personally, I don't mind it either way, especially the designs... it's good that you can point it out but I'm not sure someone is willing to create brand new designs for one of the oldest civs in the game... I do have something to say abt the few balance changes I could see: no, under no circumstances should a mini ram boat be made. we already know what is happening with the scout ship. this mini ram ship will be the new ultimate spam. just, no. that temple bonus you were talking about... yes, I'm always up for something to make each civ more unique! perhaps the temple could get a tech that increases their radius and/or increases their heal per second. ah and, Chosen Athenian sounds a soo much cooler than "city guard" lol i definitely want to see that change

I edited Part I to deal better with sources (first hidden bit now), and renamed the Delian League civ bonus Naucrary instead of Trierarchy, which could be another tech now. In this part I'm refining a few things regarding infantry and cavalry from Part I, but I'll deal mostly with siege engines. Most things are just name changes or design corrections, although for siege techs, compatibility with other civs would need to be checked (for those cases, in the meantime this is just meant as a record of sourced proposals). Part III will be about naval combat. PART II Things that should be: -Lithobólos (Siege Catapult) should be Lithobolos (Stone Thrower): accents should be removed, as per 0 A.D. nomenclature guidelines (most of the time I'll ignore this, but it should be followed). The present name, besides not being the correct translation, is misleading for the period, given that both bolt shooters and stone throwers were katapeltikon (throw against, basically), or catapults. Actually, in this period, "catapult" is even more often used for bolt shooters, being the first to be invented, and "ballista" used for stone throwers. The name inversion more familiar to everyone started after the 2nd c. A.D. -The Lithobolos torsion-springs shouldn't look like spirals: this makes no physical sense. Although there are a few ancient representations that also portray them incorrectly, there are plenty of representations around showing their correct appearance. -The Arsenal should be called Workshop: arsenals were where various equipment was stored, while "workshop" is used in the literature for what this building is supposed to be. Things that could be: -Athenians could charge when closing in on an attack: that is, be faster, louder and more disorderly than Spartans (stance depending), considering how heavy infantry charged at Marathon, and how psiloi "charged" at Sphacteria. I think it's funny that the caricaturesque static posture of the Spartans in the movie 300 and "shock combat" of the Athenians in the sequel could appear in the game in a less exaggerated way, while having some reported merit to it. -Epilektos (City Guard) could be Athēnaios Epilektos (Chosen Athenian, or less literally and keeping the present idea, Athenian Guard): just renaming them to make them more characteristically Athenian (there are units named similarly after all). It's not just about the name: Athens' Hellenistic infantry relied heavily on mercenaries, except for some elite volunteer hoplites, which seems to differentiate them a bit from epilektoi from other city-states. I thought about Epilektos Ethelontis (Chosen Volunteer), but I didn't want to give the impression that that made up term is an attested one (sometimes one has no choice). -Hippeús (Greek Cavalryman) could be Athēnaios Hippeus (Athenian Cavalryman), and be a lancer: gameplay seems to have resulted in too many things being exactly the other way around as they should be. Athenians avoided getting way too close with cavalry (they would have swords anyway, but usually as secondary or tertiary weapons, after javelins and lance), those tactics came later with the Macedonians (possibly after the Thebans), who in turn have no cavalry swordsmen in the game! -Pródromos (Cavalry Javelineer) could be Athēnaios Prodromos (Athenian Scout): I ended deciding for this name instead of Hippakontistēs (Cavalry Javelineer) since that's not actually attested (but for tournament situations, and after all, most cavalry were expected to use javelins). Although to be prodromos is more of a role that goes beyond just literally scouting, this is also how the corps is referred to (like saying that the Boy Scouts are scouts and more), and they are not mentioned that often for others except Macedonians (being later referred as lancers, as I've quoted before). -Tachunautousa Triērēs (Swift Sailing Trireme) could be an early remarkable ramming ship: it could be less literally and more helpfully translated as "Swift Ramming Trireme". The tachunautousai were the top trireme rating, strongly associated with Athens, for which ramming was their preferred tactic, although also rendered somewhat ineffective by the Hellenistic period, as will be explained in Part III. Their garrison should be reduced, or even completely removed while increasing their population cost to account for optimal performance at all times, which is one of the reasons I proposed somewhere else to extend champions to ships and siege engines. -The Oxybelēs is being represented by an early tension design: the oxybelēs would soon use a torsion mechanism mid-4th century B.C., looking like the present Lithobolos, which would completely supersede the tension design by the end of the 3rd century B.C., according to Mardsen. A further advancement would be the Polybolos, which had a magazine to increase shooting rate (could be just a tech). -The Lithobolos is being represented by a dubious design: this is still quite the controversy, but extremely illuminating, and could be used to differentiate units better. Regarding Roman terms, "the Greek bolt-shooting euthytone thus became the catapulta, and the stone-throwing palintone, the Ballista", from Kinard. Campbell and others state similar things, but what palintone exactly means is still debated: initially in his book he takes the conservative position that it had just to do with the orientation of the springs (hard to see in a game), and was a bigger version, necessary to more slowly transfer energy to somewhat equivalently worthy heavier stones. But a few years later (2011), Campbell takes the "French" position (https://www.researchgate.net/publication/307732119_The_inswinging_theory, by Iriarte), stating that "this solution, at once etymologically elegant and strikingly logical, has come to be known as 'the inswinging theory,' in which the catapult arms point forward when at rest, and are drawn inward during the spanning process", even claiming, when later discussing the onager, that "as in the case of the Hellenistic stone-projector, a brilliantly perceptive French design was sidelined by inferior German and English versions". Figures 3 and 4 in https://sciences.gloubik.info/spip.php?article1600 show both configurations clearly. In addition, palintones would eventually shoot heavy bolts (by changing their sliders), being a more powerful, although complicated, configuration. -Advanced Siege could be Lepides Sidērai (Iron Plates): the present name doesn't say anything, and it was really tricky to connect how the Lithobolos and Ram crush damage could even increase with the same tech, but regarding stone-throwers I read "Heron advises iron-plating any points of stress on the machine", from Campbell, and remembered that his other book stated "it is assumed that the vulnerable tip would have been reinforced with iron plating" regarding later rams. I've found critical point iron-plating references on many manuals while searching for something else. -Siegecraft could be Organopoioi (Mechanicians): also doesn't say absolutely anything. For a construction time bonus, "the art of those who construct the siege machines necessary for war (organopoioi), they too are termed mechanicians", from Sherwood. -Armour Plating could be Ōmon Derma (Raw Hide): to differentiate it better from the Iron Plates proposal, and many recommend for protection and fire-proofing for the big engines over iron-cladding because of weight. -Military Engineers could be Aphaireta Merē (Detachable Parts): to facilitate dismantling and transportation, as recommended in many Artillery Manuals (Belopoiika), this being another of my candidate names for this tech. I also wanted to leave more open the possible addition of Mēchanikoi (Engineers) units to build certain big siege engines in the field, as many have proposed in the past. -Bolt Accuracy could be Odontōtai Choinikides (Toothed Washers): again, the present name handwaves how exactly that would even be achieved. Washers are the discs through where the cords are threaded, their stability being important for consistent aim. To lock them, "teeth" were used after some point, and this was further developed with pin-holes (Trypētai Choinikides (Perforated Washers) could be an additional tech for more siege-oriented civs). I made up these names because these details appear only in archaeology, I think. -Naval Oxybeles could be Marine Catapult, but better if just removed: since not only the oxybeles was used, and to use the same terminology used by Morrison, and not just the same name as in Age of Mythology. Actually I disagree with having this tech at all, one should just have catapults mounted on heavier warships (explained in the coming Part III). Things that could also be considered: -Conscription at the Stable could also be Sitos (Fodder Allowance) or Katastasis (Establishment Grant): better alternatives to what was proposed in Part I, since the Hippeia (Cavalry Class) appeared in the early 6th c. B.C. (before the start of the game), while these are part of 5th c. B.C. Athenian cavalry reforms. -Eleusinia Mystēria (Eleusinian Mysteries), could be a civ bonus: this was an important panhellenic religious cult, and under Athenian control. Temples could give a food trickle, have improved healing aura, or produce units faster, for example, whatever makes sense. -An alternative approach to techs: in https://wildfiregames.com/forum/topic/34903-civ-spartans/page/3/#comment-760784 there was some discussion regarding techs unlocking units, and I ran into this "necessity" when trying to make sense of catapult evolution and how the game presently works, given that engines would look quite different after certain developments. An alternative approach would be to have some techs changing units (besides the usual techs improving them and the less common unlocking them). For siege engines, one would start with the Gastraphetēs, and then the Tension Oxybelēs (as they are right now). After researching a Torsion Springs tech, the Tension Oxybelēs would change to the Torsion Oxybelēs (which should look like a small Lithobolos), and the Lithobolos would be unlocked (which should use the French palintone design previously discussed). Later on the Polybolos (with magazine) could appear (either as an Oxybelēs change or unit unlock), and a final Heavy Catapult could later be unlocked (larger but slower) that could change between large stones and arrows. I know it seems too much, but I'm mentioning it for the sake of catapult clarity and completeness (and for whoever wants to implement things like these in their mod). Other information that might be useful: (All quotes from Sekunda). -Torch-Races for infantry speed bonuses: "we have evidence for three ephebic torch-races before the reform of the ephēbeia in 335, connected with the festivals of Prometheus, Hephaistos and Pan". -I think somewhere I mentioned Athenians would use "A" or "ATH" as shield devices, there's also evidence for an eye, a gorgon, a star and a laurel wreath. -Ephippios (Saddlecloth), Af'Hippou Akuntizonti (Mounted Javelin-Throwing) and Aphippolampada (Mounted Torch-Race) techs to improve cavalry: by 500 B.C. Athens didn't have yet a navy, nor proper cavalry, these were developments from the 5th c. BC. I like the idea of having lots of techs, for the player to think what to choose given different situations, otherwise everything devolves into mindless build/research order memorisation, or worse, just clicking what's affordable. Both should be penalised for a more strategic gameplay. These early techs should make Athens cavalry fast and accurate among Greeks early on, the problem is that the game is quite fast and by the mid game the Thebans, and later the Macedonians, should have better cavalry. In any case, this might be useful at some point for some. -"In Athens, a slave society, it was normal for an individual citizen of sufficient wealth to serve as a hoplite and to have his own personal slave. In time of war, the slave would carry the hoplite’s bedding and rations for him. Usually referred to as skeuophoroi, or 'baggage carriers' in our texts, the slaves would participate in the battle only if an unusual opportunity arose. Their essential role was recognized by the Athenian state". -It's good to bear in mind that, after a few decades where heavy armour seemed to be less common, "in the 360s, Athenian funerary reliefs start to show hoplites wearing muscle-cuirasses and 'Phrygian' helmets", "muscle-cuirass is universal, but there is a large diversity in the arrangement of the groin-flaps and the shape of the shoulder-guards", "some type of enabling legislation must have existed to force the adoption of the muscle-cuirass on the Athenian citizenry who served in the infantry". -"I imagine that the Athenian cavalry had adopted the Boeotian helmet by 362, and this was the reason why the Theban horse who opposed them at the battle of Mantineia painted their helmets white to identify themselves". @Arup, as the self proclaimed biggest worshipper of Athena, let us know what do you think is more worth considering regarding gameplay (although most of my proposals are just renames or design corrections, I think). I guess some points would change how the Athenians actually play, but I think they should be a fairly fast civ for Greek standards, with their decent early cavalry skirmishers, other missile support and swift ramming ships, while also having a solid infantry that, according to the stories, would make a sprint for it if needed. Right now I find it confusingly sword heavy, since neither the Marines nor Sword Cavalry correspond to anything realistic for them, while an eventual lack of swords would balance better with their Long Walls (and swords are really needed, maybe the Athenian Guard could switch between spear and sword, or better, the Iphicratean Hoplite proposed in Part I could switch between long-spear/proto-pike and sword).

Seems sensible. I don't have too much time now and won't have so soon. But I had a idea of using the game setup chat to share results. This way one can get faster to a bigger data base. During the transmission one would spam the chat window one time with a big wall of text. So there may be some guard rails necessary against abuse, but then again any user can spam the chat. So as I imagine it the broadcast would look something like this: ffm: [LoacalRatings V0.28] Sharing my game results for team games: Date Time (UTC+0) | Winnerteam | Loserteam 26.09.2026 20:00 | ffm(maur), a(iber), b(gaul), c(gaul) | d(gaul), e(gaul), f(gaul), g(gaul) This data could then be separately saved and in doubt deleted if you believe someone gave false data or someone had weird settings. Just as a sketch. A downside could be that users snitch on other users how often they play, I don't know if that makes some uncomfortable. This data is already shared via the replays but to a smaller extend. I guess best would be not to share your gamer nick with your boss. Edit: Actually this way whole replays could be transmitted. Don't know if one should. Maybe a new mod, share replays would be better. Host a game in the lobby for that purpose in the lobby, let some join that you want to share with and synchronize your data bases.

this looks so heavily edited I'm laughing

It also didn't seem to keep the replacement templates I put in

So, I was getting this. It isn't letting me pick a replacement template for certain ones. Also, could you have it when you double click on a warning or error in the findings tab, that it opens the fix selected menu, instead of going to the analyze tab

It reminds me the Death Hand of the Harkonnen...

Hey @ffm2 - Awesome work! I made a mod of your mod. I thought the communication in your version was a little too verbose -- too much detail, and I wanted to quickly answer the question for the host: "WHOM SHOULD I SWAP" to achieve balance. I'm attaching the two files which I modified: gui/gamesetup/Pages/GameSetupPage/Panels/Buttons/BalanceTeamsButton.js gui/common/network~LocalRatings.js Mostly, I wanted to add the /suggest command, but I ended adding or modifying four: /evaluate /suggest /suggestteams /about In detail: /evaluate Shows player rankings, including observers, and evaluates the current two-team setup. It does not propose new teams. Example /suggest For 3v3 and 4v4 games, evaluates eligible one-player swaps between the stronger and weaker teams and displays up to two swaps that most improve the predicted balance. Example Output /suggestteams Shows the current team setup and, in a 4v4 game, several fixed rank-based full-team configurations. It does not show rankings. /about Prints attribution and the command summary. What do you guys think? ps - In this version, I also manually nerf my own LR rating, because it is a little ridiculous. I might be accused of using this to try to get better teammates, but I'm really just trying to make it as accurate as possible. pps - I'm ignoring edge cases. The mod only suggests for 3v3 or 4v4 game. I think that covers 99% of use cases. BalanceTeamsButton.js network~LocalRatings.js

It turns out it has such a long history

Special attacks with bombers and nuclear missiles: (slowness is from the capture on the notebook, FPS in the top corner of the video). Gravação de tela de 2026-09-26 01-42-06.webm

@AsherIf you select only one map at a time then only that map is converted. When this is however a map pack, the entire pack is converted map by map but into the same folder, same as its source. Sorry, could not help it - just made another release 1.8.0 that provides better entity conversion support including automatic suggestion of most likely replacement and a few other improvements (e.g. @vladislavbelov's tree randomization script). One new architectural thing is that I extracted a common code package that will be also used by other ATLAS-related tools that I am preparing. Please find the latest release 1.8.0 in the top message of this thread (with updated screenshots)

nah, I could learn a lot from your work here :D Really cool! Didn't know all this was possible.

Turns out it was true they actually existed... I love this work, @Eilat. It looks really good!! The dust blowing around when the helicopter takes off is a great detail. Looking forward to seeing the next updates!

The first helicopter has entered full operational status. It features a full range of unique flight capabilities, such as lateral tilting and short range backward movement, and gains altitude during long distance flight. It is also capable of firing rockets and anti tank missiles, and deploying heat decoys. Recording 2026-09-26 005347.mp4

Thanks! That is very helpful. I probably won't do it today, but probably tomorrow One thing, can you make it so you can convert one map, and not all of the skirmishes or scenarios (this may be a feature already, sorry if it is and I just don't know about it). If you could make it where you select the individual maps on the setup page maybe?

Here are a couple of older maps I was able to collect form the forum. Some (that I played in the past already) are pretty awesome like Fall of Constantinople, Alesia, or TheLegendofMali. The others will most probably also be interesting. I'd suggest you look into one map and verify if it can be converted and is still palyable, if you like. That would be very helpful!!! Thank you so much! alesia.zip Athens.zip Alpine Settlement 0,1.zip Epiphany_v5.pmp Epiphany_v5.xml Fall Of Constantinople.pmp Fall Of Constantinople.xml Halicarnassus.pmp Halicarnassus.xml TheLegendofMaliSecondVersion.pmp TheLegendofMaliSecondVersion.xml

@Stan here you go: docker run -it --rm --name veredus -p 20595:20595/udp -v veredus:/data ghcr.io/victorcrimea/veredus:latest-sidecar Then connect with stock client via direct ip. Try to run a match with AI. Disconnect and reconnect to check the rejoin with ai.

Do you have any suggestions? I am not so familiar with the pmp versioning, so if you know of any, and could point me to them, that would be great! Or I could just look through the forum a little . Do you know what year pmp 5 was?

I’ve looked at your profile, and I realize that I, an amateur, have been giving instructions to an expert.