Leaderboard

You'll be happy, it's yet implemented in the current dev version, so you can expect to see it in a21: http://trac.wildfiregames.com/changeset/18372 You can see all current changes at http://trac.wildfiregames.com/wiki/Alpha21

Okay, my new thoughts about the Scythians. I think that large buildings like Civic Center, Market, etc. can "upgrade" to a Large Cart. And then this Large Cart can upgrade back to any Large class building (Civic Center, Temple, Market). There can be a Small Cart that can change to any Small class building and back again. So what this does is illiminate the need to remember what cart is which and the need to make a unique cart model for each building. You just have 2 classes of cart, Large and Small, and each can upgrade to any building in their class. Thoughts?

Thracians would make a very cool mod civ though.

What is a prop-point? A prop-point is a specific point in a 3D space (basically a coordinate) with a specific name which is used to reference that specific spot within 0AD actors (structures' models, units, animals, even props) What are they used for? They're used to spawn an actor within another actor. Basically you load another model/unit/structure/prop of the game inside the model where the prop-point is. Examples: - In a structure, you can use a prop-point to have a fountain which is already in the game and place it within that structure. - In units, you can use prop-points to have different gear in different places like the head for helmets, in the hands for shields/weapons etc - In animals, you can use prop-points to spawn effects like dust in their feet when they're running or blood when they die. - In props, you can use it for randomization of the prop, like a helmet which can use different styles of feathers spawned at the prop-point location. Which are the benefits? There are many. Just saying that you can reference any existing prop/model in the game directly in a place within your model is quite powerful already. - Powerful recursive system - Easy set-up - Randomization capabilities - Memory saving (you don't need to store again the data of a model that is already in the game) How can I create them? In Blender3D: In blender these prop-points are made with "empties". An empty is just a point in space which stores the coordinates where it's located within the scene. No materials, no geometry, no lighting data. Just location and rotation. To create an empty in your model, just open the "add menu" with shift+space in the viewport and select "Empty" there will be a list with different empties types, but these are all the same, just different types of representations of it. Select your preferred type (the standard is "Plain Axes") and an empty will be created in the location of the 3D cursor. IMPORTANT NOTES: -It is obligatory that the name of these empties start with: "prop- " or "prop_ " -Examples: prop-fountain , prop-helmet, prop_flag-AND it is also obligatory that the empties are parented to the geometry of your model. To parent the empties to your model, (in object mode) select all your empties first, then your model and use the hotkey CTRL+P and they'll be parented to the geometry.-Finally, when exporting, select all your empties first, and you model last, and export as usual.How can I reference a prop-point inside an .xml actor? Props are defined in the .xml normally after the mesh has been defined. Here's an example of the persian stables, where the horses are propped by prop-points. Note that minheight and maxheight are OPTIONAL parameters used for anchoring the prop-point to the ground. Prop parameters: actor= the actor .xml that we want to spawn in that prop-point attachpoint= the name of the empty/prop-point that we created in the mesh WITHOUT the "prop-" or "prop_" prefix minheight/maxheight= These are optional parameters to determine the anchoring to the ground, the max and minimum height the prop will have when conforming to terrain. <?xml version="1.0" encoding="utf-8"?><actor version="1"> <castshadow/> <group> <variant frequency="100" name="Stables"> <mesh>structural/pers_stables.dae</mesh> <props> <prop actor="props/structures/decals/dirt_4x4.xml" attachpoint="root"/> <prop actor="props/structures/decals/celt_sb1_mud.xml" attachpoint="root"/> <prop actor="props/structures/persians/stable_horse_a.xml" attachpoint="horsea" minheight="-20" maxheight="1.7"/> <prop actor="props/structures/persians/stable_horse_b.xml" attachpoint="horseb" minheight="-20" maxheight="1.7"/> <prop actor="props/structures/persians/stable_horse_c.xml" attachpoint="horsec" minheight="-20" maxheight="1.7"/> </props> <textures> <texture file="structural/pers_struct.png" name="baseTex"/> [...]Prop-points in armatures When creating prop-points for meshes that are animated (in other words, when they have an armature/skeleton) the prop-points are created with bones. These bones doesn't need to have a vertexgroup in the mesh, but they're required to have a name with the prefix "prop-" or "prop_" just the same as when using empties.These bones also need to have a parent bone, which will inherit it's movement (location and rotation)Animating these bones would not have any effect when the animation is imported into the game.When defining prop-points on animated meshes, nothing changes. It is the same procedure as normal prop-points. Other useful tutorials in this forum: Import/export assets from Blender to 0AD and baking AOHow to export animations from Blender to 0ADLowpoly modelling tipsHow to create textures with Blender3DIt would be nice if Stan could post also some guidelines to create these prop-points called dummies in 3DSMAX in this thread too

I would recommend too the Petra Bot entry of the wiki: http://trac.wildfiregames.com/wiki/PetraBot

BTW -- here is why fog would need to be reduce or turned off for ISO view:

Hi, Aghilas! I've been involved with the Aristeia mod for some time now, mostly in the background, off and on, as document designer and civ researcher. I'm very happy to meet a fellow Bronze Age enthusiast! But let me just say this... I have strong feelings about the accurate depiction of the Hebrew peoples (and other ancient peoples in general, but _especially_ the descendants of Abraham). I have no doubt that you and others who use the Star of David as an ancient Israelite symbol are well-meaning; however, I am compelled to point out that this is probably not a correct symbol to use to represent people of Hebrew descent prior to a couple of centuries ago. See this article: http://www.menorah.org/starofdavid.html Based on my research, I have come to the following tentative conclusions regarding Hebrew civ emblems: For a Maccabean timeframe, the menorah would work fine. For a Divided Kingdom Judah timeframe, the Lion of Judah would apply. For Divided Kingdom Israel, you could use the Bronze Bull of Samaria. Or, you could use a representation of Baal (which would also work well with Phoenicia). For the Judges and/or United Monarchy, the pomegranate would be a good choice. For the Patriarch period, I haven't decided yet. (Torah? Circumcision knife? Shofar? Pomegranate again? Palm frond? More research required.) Funny story: I had already decided on the Carthaginians as the basic placeholder civ to use for anything Judah/Israel/Phoenicia-related for Aristeia, at least as far as architecture goes.

You were right, a rebuild of spidermonkey seems to have resolved the issue, thanks, much appreciated.

That's what I'm there for

If you look at the replay code in the source folder you will find how we parse it to replay games, we basically execute player commands one by one to replay the exact same thing, So I guess learning from that is doable, though it will require some data extracting cause it's quite raw. But that's an interesting project. Maybe you'll find more stuff here : https://github.com/agentx-cgn/Hannibal and https://github.com/lexoyo/split-bot/blob/master/src/BotAI.hx unfortunately both dead projects AFAIK, maybe @agentx is still around to help you.