All Activity

Having people who can compile is important for testing many things. I can help you with that if you want to do it some day

My favorite too Hopefully it can be a good starting point to make naval battles very different then land battles. For the onager : In this very PR, I added support to be able to "tweak" projectile effect delays. So that's something that can be tuned to some degree but very easily. For the elephant : I guess this is a animation issue or maybe I should try to make the same solution then for projectiles but for melee attacks.

Too bad it's not possible to make a mod, unfortunately I don't have it compiled. I like what I see in the videos. The ship's movement looks really natural. The timing in the other two videos might be not 100 percent on point (on the elephant attack too late, on the catapult impact too early?). I think it's nice and I wanna encourage anyone who is able to test it

I haven't even looked at the Romans in vanilla yet

Thanks @Asher! This is great to hear! (read ) Just tried to convert some older maps from the forum (the LegendofMali worked mostly!) but some are just too old and I need to investigate how to still use them.

Seems to work , @Grautvornix

Unfortunately it's mainly modifications to the game engine itself, meaning it's not possible to wrap into a mod. But I can help out by providing a couple of demo videos for you : (I had to compress the videos) Screencast+from+2026-09-21+22-14-52.webm Screencast+from+2026-09-21+22-13-08.webm Screencast+from+2026-09-21+22-11-19.webm For testing you will need to know how to compile the game. Which makes things difficult I'm aware.

I'm excited to hear this is going forward! Is there a way you could provide a mod for easy testing purposes if it's not too much work? That would be awesome.

Sure, but as with many things, that's just an abstraction. No battle represents an actual battle, but a whole conflict, at least in a game like this, and how things are represented is always a decision to be made. A possibility could be for corpses to be robbed to get Loot, and after that for them to disappear fast. This would naturally be more safely done after the end of battles. But I don't know if this has been discussed, nor it seems a priority to me, compared with so many other things. Maybe I'd go 75% for stone and metal, and 50% for wood (or 50% 25% if from a gameplay point of view those are too much): easier to remember, takes into account stone and metal are highly reusable, and the process has to be worth it (this considering they are unbuilt/unproduced as I mentioned, which is part of the balance when compared to just deleting them). Actually, this way to get stone and metal should be an important one (at least realistically), not even Catholic Popes would eventually resist melting Roman bronze statues to make cannons, for example.

@Thalatta You are right - will remove that constraint (also use captured buildings as a quarry). Will also change the refunding stone and metal (50% each) wood (30%). While modifying the mod, I changed the "delete" function of everything: a unit being deleted (killed by its "owner") looses health over time (10s) until it dies (same es when being attacked), as well as any structure/siege/ships being deleted. Here is the latest version 1.4.0 with that logic (I know there is still a way to go). recover-resources.zip README.md

Updated to 1.3.0 (see top of this thread) Extended editing capability Analyze tab lists also treasures and relics if any Re-arranged section on the analyze and edit tabs fo rimproved readability.

Sure, but I just find it funny and it never made sense that you can earn loot in a battle in which no one survives to bring home anything.

Yes, which is why I have told you to at least look at the mod wether it be download and the structure tree, or just on github its self.

Do you also have triarii units? I guess that could be useful not to just lose spearmen.

The game does have "ruins" in many scenarios, which provide stone. The problem would be to take care of a more seamless transition between all kinds of buildings and their corresponding ruins. Maybe later on all these concepts could be unified in a coherent framework, but right now unbuilding/unproducing seems the simplest way. The game already includes Loot from killed units. Realistically, to the victor should belong the spoils, but as you say, in a game like this it's hard to determine when a battle ends, thus individual opportunism is what's accounted for.

I would find it "logistically" more "realistic" and tactically more "interesting" if destroyed buildings, no matter if self-destructed or the enemy's, would turn into "mines" containing the resources which have to be explicitly gathered and brought to one's storehouses. Also a battlefield could turn into "mines" with the "loot", like scouring the field after the battle looking for usable stuff, although it's hard to determine when a battle "ends". Would change balancing heavily against rushers/attackers in far away foreign territory though. Instead of "mines", the resources could also turn into those bonus-/treasure-item-like things, although those don't have to be brought to one's storehouses.

You could check out what we did with <SpecificName>Hastātus</SpecificName> for rome. My understanding is early on they were similar to hoplites in kits and then they evolved into swordsmen. So in p1 Hastatus = spearman and then it is replaced in p2 by Hastatus = swordsman infantry_swordsman_b.xml infantry_spearman_b.xml

Well the game already does it for "hoplites" they have a mixin that allows all hoplites to have phalanx formation. <Identity> <Classes datatype="tokens">Hoplite</Classes> <Tooltip>Hoplites can use phalanx formation</Tooltip> <History>Hoplites were the very symbol of Hellenic prestige and citizenship, armed with a spear and a large round bronze-coated shield known as an aspis. Armor was heavy, with bronze helmets and a cuirass of either bronze or linen, in addition to greaves. Hoplites fought in a tight formation called a phalanx, guarding each other with their shields while they attacked the enemy with their 2.5 meter spear or short iron sword.</History> </Identity> just add a visable class <Identity> <VisibleClasses datatype="tokens">Athenian</VisibleClasses> <Tooltip>A true citizen of Athens.</Tooltip> </Identity>

I think the point could be to keep selectable options limited and uniform among civs, while allowing for actual differentiation and evolution if wanted. I've come across this issue so many times, and one has to end anachronistically simplify things, which could indeed be solved if "a unit can represent more than just the soldiers equipped in the exact same way". For example, the Athenians had hippotoxotai (cavalry archers) substituted by prodromoi ("scouts") in the first half of the 4th c. BC. With the proposal, both could appear, depending on progress, but the icon, or just the "generic" name, could be the same, and quite common for most civs (Mounted Skirmisher could be an option), but the actual model would change (among civs and with progress), have different stats, and the "particular" unit name also be written somewhere, but the "generic" name would tell you basically its function. Other examples I came across just this last week is that Alexander's mounted skirmishers went from javelineers to archers, and his prodromoi apparently from javelineers to lancers. And I guess it would simplify dealing with things like the Roman Army. Regarding mixins, if you can irreversibly upgrade them such that they also change in the buildings that produce them, and show also their "particular" name somewhere, maybe it could work, but those working on it would have a better understanding on why it wouldn't.

Besides my previous comments on why I think most of these rules could simply be removed, following that same line, I didn't comment on "entities you captured or converted from another player (or from Gaia) are not refunded", I wonder why this is the case: tons of monumental architecture has been dismantled by conquering states, using then the stone to build in their own style (even the Ayyubids tried to dismantle the Pyramids of Giza, Menkaure's has been left with a big gash since). That's what's great with stone and metal, quite reusable… which makes me think if wood should have some penalty, but also wouldn't want to add rules, my philosophy being the exact opposite.

@Thalatta happy it was not in my code

Oh hell naw! Just by pressing Learn to Play one can read "Civilisation", no one cares about guidelines . Will consider it for my upcoming renaming PR.

Just something to consider: I don't think there are any examples of ancient sword guards looking like a nihonto's tsuba.

Couldn't you do that through a "mixin"?

Here is an intermediate step recover-resources.mod V1.32. - not taking into account @Thalatta's latest comments yet, unfortunately. Version 1.3.2 · for 0 A.D. release 28 and the release 29 development builds When you delete one of your own structures, ships or siege engines, you get back a share of its resource cost, provided the situation allows it. What comes back is the salvage rat (30 % by default) multiplied by the object's health condition, meaning its remaining health. Food is never given back. Rules and Constraints: Only your own deliberate deletion (Delete key / delete button) triggers a refund. Nothing is refunded when an enemy destroys the entity. The refund is based on the entity's current cost, including cost modifiers from technologies and civilisation bonuses. Food is excluded: it was eaten during construction, while timber, stone and metal can be carried away. Entities you captured or converted from another player (or from Gaia) are not refunded. Ships are only refunded when deleted within 30 m of one of your own finished docks. Otherwise the message says how many ships gave nothing back. Siege engines are only refunded while they stand inside your own territory, e.g. a catapult abandoned deep in enemy land gives nothing back. The refund shrinks with condition: a ram at 40 % health gives back 40 % of the usual amount. Buildings (nw including walls and towers) must pass three rules: not attacked or captured in the last 15 seconds, no enemy capture progress and not decaying outside your borders, and one of your worker units within 20 m to do the work. Fields are never refunded. Nothing you delete dies at once. Buildings are dismantled and units disbanded over 10 seconds, losing health as they go, and any resources only arrive at the end (units don't give back resources). Pressing delete again calls it off and the drained health is given back; an enemy hit interrupts it the same way. Units take just as long even though they hand nothing back. Anything under threat is the exception: it falls the moment you press delete, because under fire there is no time for an orderly teardown. That means anything hit in the last 5 seconds, or with an armed enemy within 40 m — enemies closing in count even before the first blow lands. Whether it still pays out is decided by the ordinary rules, so a building under attack dies at once and gives nothing. Unfinished foundations are skipped because the base game already refunds the unbuilt part of their cost. Deletions the game itself blocks (for example, a building that is mostly captured) get no refund. A short message shows how much was recovered. recover-resources.zip README.md