Imarok

No, my comment was regarding the humans using a mallet for seeding instead of a bowl. xD

Couldn't you just equip them with some kind of bowl?

So that's still needed, right? And have you seen my edit? ;)

I think they rather mean something like @Imarok's clickable attack messages: #5132

That works, but it doesn't resolve the elephant issue. I guess they need a separate variant file. Edit: And I guess they aren't supposed to seed with a mallet in their hands, aren't they?

Index: binaries/data/mods/public/simulation/components/UnitAI.js =================================================================== --- binaries/data/mods/public/simulation/components/UnitAI.js (Revision 22862) +++ binaries/data/mods/public/simulation/components/UnitAI.js (Arbeitskopie) @@ -2719,7 +2719,9 @@ this.FaceTowardsTarget(this.order.data.target); - this.SelectAnimation("build"); + let cmpIdentity = Engine.QueryInterface(this.order.data.target, IID_Identity); + + this.SelectAnimation(cmpIdentity && cmpIdentity.HasClass("Field") ? "seed" : "build"); this.StartTimer(1000, 1000); return false; }, But this doesn't consider the elephant worker issue. And not sure if the name of the animation fits our schema

But the animation doesn't have it's own variant yet, right?

I know but is it already committedto svn?

Yay Looking forward to have that in the game

Yep, the repository itself can always be easily migrated. But we already offer a repository on github... As said we already host a mirror of our repository on GH. But I guess you mean we should also use the "sugar" GH offers besides only hosting a git repo: pull requests, issues, CI, etc. But there we come back to your first point: all that "sugar" can't be easily migrated if GH(or M$) changes policy because those "sugar" isn't part of git. https://trac.wildfiregames.com/wiki/BuildInstructions#Acquiringthecode

So you are talking about a specific platform now? You can use git without using github... (And afaik you can also use phabricator together with our github mirror)

The metadata.json contains a record of all scores (and kills etc.) for about every 30 seconds of the game. So no need to rerun the replay.

I think that is exactly what @vladislavbelov is planning. Maybe he can need some help?

About a year ago I wanted to change the code so that it uses a seeding animation for building fields just to discover that we don't have such animation xD

I don't think there is such a plan. The AI was made JavaScript for moddability  Afaik everything that is too performance heavy in js should be done in c++ if it doesn't hinder moddability too much.

Very nice. Is it already committed? In that case we should change the code so that it is used.

A seeding animation would be nice. Then the workers won't build a field by hammering it in the ground anymore.

I would be available.

Already looked if a crashlog is produced? Assuming Solus us some unix os: tried running 0ad in the command line and looking at that output? (Tried attaching gdb?)

The aim of those strings is not to be easily translatable but to be understandable by english speakers. For translation one always have to have a general knowledge of the game and consider the context of the string to choose the best matching possible translation.

Feel free to do so. How did you fix the gloox issue?

Visual "realism" is good but it's for the bin if you don't see ata glance to which player a unit belongs. 0ad is still a game and not a history simulation. (Of course we should aim for the best historical accuracy. But only as long as it doesn't hinder the gameplay too much) I know the view on this issue also heavily depends on whether you are more a competitive player or a casual. (Maybe we should just have an option to switch between two variatons: One with 100% accurate textures and one with accurate textures and distinguishable player color. Will be much effort and not sure how easy to implement ;))

Try disable GLSL and postprocessing in the options.

Ok, there already is already a ticket: 2824 Edit: 2645 also sounds quite similar.

@implodedok can we fix that?