Stan`

@Genava55 I'll go with Remogantion if it's the most correct.

Maybe you are right I just remember they were removed. https://code.wildfiregames.com/rP20657 https://code.wildfiregames.com/rP20351

@Genava55 Specific name for the theatron ?

That's the idea. But until all that is reviewed and figured out I don't expect much...

Do you have any crashlog.txt or crashlog.dmp in %localappdata%\0ad\logs ?

No such guys right now :/ Nobody in the team is actively working on balancing, but you guys know that right ?

I believe those have a very bad performance impact. Weren't all those spread operators removed ?

To be honest it's because I don't play the game enough to have a say in balancing.

I am so sorry

What are you trying to pull off with the IRS documents ?

Well you can find a few rocks in my eyecandy mod m8te https://github.com/0ADMods/eyecandy

Hello sorry for the inconvenience. You have two options a) Download this fixed bundle (Please let me know if you do so) https://www.mediafire.com/file/00lxxtdmsu64nrs/0ad-0.0.23b-alpha-osx64.dmg/file b) In the game options lobby tab disable TLS encryption.

@LordGood Indeed I forgot to fix the AO ^^ better now .

If nobody has objections of @Genava55 @LordGood @Alexandermb I'll commit it as an Atlas template.

Sure. The question being would it save time in the future to modders and game programmers that they are separated. I think it would be pretty straightforward to look into the schemas for XML schemas, but some people might disagree. But the thing is the only thing they could oppose is that they like to have mixed code types, which as you stated is an antipattern. In theory yes, however XSD would come with other requirements https://www.w3schools.com/xml/schema_example.asp Also, that would mean we'd have to add it to every template block like Identity which seems a bit unproductive.

I'm not sure that's even an argument. I'd rather be comparing two XML files than a JavaScript file and an XML file. Luckily enough our schemas are defined at the top of the file. Moving seems like a pretty good idea then. I'm actually not sure. However, if one defines a broken Schema in JavaScript files, (I guess CPP too but I haven't tried) you'll get an error when you start Atlas. I actually found a work around for that. Maybe it's dirty, but with some refinement it could work properly. ResourceSupply.prototype.Schema = Engine.ReadFile("simulation/components/schemas/ResourceSupply.xml").replace("Resources.BuildChoicesSchema(true, true)", Resources.BuildChoicesSchema(true, true)); Changing parameters here sounds a bit tricky, but I guess one could come up with a way to define a special string which would cover different options. JavascriptObject;JavascriptFunction;Param1;Param2; etc and make a parsing function for it in utils. https://stackoverflow.com/questions/4116608/pass-unknown-number-of-arguments-into-javascript-function

Maybe but templates are XML so examples should be XML.

Nobody is getting paid so it would not attract more developers whether you have 25k or 160k in the bank.

Have you looked at Enrique's tutorial ?

@Trinketos I think the main problem here is the way you put the leaf planes :/

Nice work Sundiata. Keep it up and you might be one of us one day

Fun fact papyrus was added to the official list on ore two years baxk. It needs. One single clump variation and one pack

As long as it's useful it's worth it

Glad you like it ! I recorded it maybe twenty times