s0600204

@stanislas69 No, just use the .pyromod extension instead of .zip It could probably be made more explicit on the wiki. The "Modding Guide" page does currently state that "Typically mods are located in binaries/data/mods/" (which is correct - at least for mods distributed with the game), and then goes on to say "but you can also add them to the mods (data) directory" which is actually where we want third-party mods to be placed. This should probably be rewritten to make it clearer.

Frankly, I'm a little surprised he got that semi-working. But yes, that youtuber is demonstrating wrong. The place to install mods on OSX is "~/Library/Application Support/0ad/mods/{mod_name}/{mod_name.zip}". (I mean, if you're going to demonstrate something, it would be a good idea to make sure you're doing it correctly... You'd think the fact it doesn't show up in the mod selection screen would be indicative that he's done something wrong.) Anyway... Are you saying that your original "guy" has done something similar? (Also, where is he communicating with you?) (On Windows (Vista or newer), mods should be installed as: "C:\Users\{user}\Documents\My Games\0ad\mods\{mod_name}\{mod_name}.zip")

A mod written for A22 will certainly not work with A24. A mod written for A23 is very unlikely to work with A24. pyrogenesis probably should check that all enabled mods are (or at least claim to be) compatible every time it starts, but until someone writes code that does that...

Not really a bug, but expected behaviour. A mod created for A22 is not going to work with A23. Your user can either (any one of these should work): Run the program from the command line like so: "0ad -mod=mod", which will start 0ad in the mod-selector screen where they can disable the mod through the gui; or Find the file "user.cfg", and modify the line starting "mod.enabledmods" to remove the reference to delenda_est; or Remove the delenda_est folder manually from their system.

Links to a couple of tickets that have been opened on the topic of the stdlib error: https://trac.wildfiregames.com/ticket/5152 https://trac.wildfiregames.com/ticket/5157 (Just to keep things cross-referenced, and people apprised.)

Hello! If you want to run A22 on Ubuntu 18.04, you can acquire it from Ubuntu's own package repositories. The package you're trying to install is, as the name suggests, for use with Ubuntu 17.10.

Error occurs because "obsidiana" is not a valid Type for the Minimap component. Unfortunately, to add it requires a c++ change. (Clearly we missed something whilst de-hard-coding resource types...)

May I ping you? Looks like it'll still happen in A23. Looking at gamesetup.js, the code that assigns a random civ to a player starts by making a list of available "cultures" (filtering out unplayable civs so as not to add their "culture" to the list (unless they happen to share it with a playable civ)), then randomly chooses a civ from a randomly selected culture - but does not check if the civs it's selecting from are all playable. In other words, SelectableInGameSetup needs to be checked on line 2182. So... do you want to fix it, or shall I?

Committed in r21688 (trac / phab). Thanks to all for bringing this to our attention, and your assistance in helping test the fix.

@mapkoc, the patch on phabricator has been updated, could we ask you to try it again?

Problem appears to be caused by a recent commit to the github repository. Please see the (four) comments attached to the problematic commit. (The fishing boat simply hasn't been updated yet. I believe it's on @stanislas69's todo list.)

It bugs because you have units, structures, and techs that (according to the xml and json templates) require either the town or city phase techs, but the xiongnu civ has no way of researching these. This might be intentional, in which case one solution would be to remove any and all town and city phase requirements from the units, techs and structures of the civ. An alternate solution would be to override the generic phase techs with civ-specific ones that either cost nothing and auto-research themselves, or are renamed to be more suitable for a nomadic civ. (The phases might be named "Village" -> "Town" -> "City" in the core game, but that doesn't mean they have to be so in mods. You could have them as "Traveller Band" -> "Caravan Pack" -> "Convoy" (or whatever's suitable).)

Dunno about "Static Obstruction", but the template of the "Shoushe" siege weapon was broken as a side-effect of r20804 (trac / phab). (And selecting the fortress loads that template so the "Shoushe" can be displayed as a build/train option.) Try it now.

The code doesn't know that until it tests for it. Which is what it's trying to do. Last time I saw the contents of your mod (the "v1.01 release", if my notes are accurate), you did have a copy of simulation/components/EntityLimits.js and it doesn't have the function in it. I can't remember right now why you have a copy of the file - and I don't know if you still do - but either update it or remove it. (It looks like the only differences between the version in your mod at v1.01 and the current SVN-version are the missing function, and some added lines in the Schema example.)

That would be something for @s0600204. (That language seen on that screenshot is german). *cough* D844

Got it. Try it now.

It should now. Not backport-able: you will need to update your mod to be A23-compatible to use it.

Therein lies the problem. (if you'd moved them to "structures/{civ}/*.xml" and "units/{civ}/*.xml" you wouldn't have the problem, and you'd have even fewer files in each folder.) The simplest "fix" would be to move 'em back (or into the "{structures|unit}/{civ}/*.xml" folder layout). A "code fix" wouldn't really be worth it, as A23 should be released within a month or so. Thus, any code "fix" for A22 would have to be replaced by another "fix" for A23; and would make it harder to upgrade your mod to be compatible with A23. Considering where the change would have to take place, a "code fix" would also be unpleasant.

1 - Fixed 2 - Unable to duplicate (or I'm misunderstanding you). 3 - Unable to duplicate. (In vanilla 0AD) Building a "Sentry Tower", upgrading it to "Defence Tower", then right-clicking the big entity icon: Template Viewer appears displaying stats of the "Defence Tower".

Thank you. I did say it was nowhere near complete, and clearly one of the things needed to do is check which files are actually needed and which aren't. (Did it for the gui. Mostly. Not so much for the simulation templates.) Doesn't have to be public. Github offers private repositories. (As previously mentioned in this thread.) GitLab does as well (and apparently offers them for free, unlike GitHub which requires a monthly subscription). Also, I'm not sure how GitHub handles repositories that are set to private but have "collaborators" (to use their nomenclature) who don't pay a monthly subscription. git apply {patchfile} (If you're using the command line. There should be an option in most gui abstractions of git that does the trick.) Of course, if you're going to put the project on github/lab it would be easier for me to fork and create a branch. That way you can see the changes split into discrete commits instead of all squashed into one as it is in that file.

https://trac.wildfiregames.com/wiki/Changelogs

Do you have a version for those of us who are not on Windows? (Or just a changeset perhaps.) Nowhere near complete, but as a start: hyrule_A23-squashed.patch (Could also provide it as a branch if there were some (semi-)public accessible repo...)

I can't find any variants or animations relating to crossbows in vanilla-0ad. @Alexandermb claims to have created and committed animations for infantry crossbowmen in this forum post, but there's no sign of that in the Terra Magna repository on GitHub (might not have pushed changes). There are animations for what (according to the file name) is infantry crossbow melee dating back to 2012 from @Kimball, but these (a) appear to be unused and (b) are not loadable in/by Atlas ("Didn't find any objects in the scene" / "Couldn't find object to convert" / "Could not load animation [...]" / "Failed loading, marked file as bad").

Yeah, that's a bug. Someone care to fill out an issue on trac? Please? It does not, no. Y'know, hypothetically, if the repository was on GitLab/GitHub/whatever (locked down so only a select few could see it if that's your thing) it would make things easier for those selected few to suggest fixes and improvements through pull requests. There's clearly a couple of people present who want to help with the scripting side of things. (Unless it already is, but you haven't told us...) Side-effect of the hero-choosing thing at game start. Usually, a technology that can't be researched at a building or unit, but is still a requirement for something else, is a cause for concern. This?: https://wildfiregames.com/forum/index.php?/topic/22904-how-does-the-armour-work

@stanislas69, art isn't really my forte but I've created a branch with what I hope are the required changes for Terra Magna on GitHub. Before it gets merged into master, could you check I haven't done anything stupid/missed anything, please? When you find the time. (The indenting in the actor files is all over the place. Tabs in roughly half, spaces in most of the others, with a mix of both in some files. Haven't done anything with it in the afore-mentioned branch so its clear what the pertinent changes are, but it would be nice to sort it out at some point.)