Ceres

I wonder how a scroolbar works with 20 garrisoned units and you are hectically looking for units that are healthy enough to send them out. But yes, it might work. This is about infographics and visualisation of data after all, I guess. On the other hand, why bother to see that individual health bars and then manually pick some and send them out? Instead you could set a threshold (before or in-game) that when clicking "Ungarrison healthy units only" only units with health above that threshold are ungarrisoned. When clicking on "Ungarrison all selected units" send all of them out. Would this be an option? @LetswaveaBook Or is this far away from your thoughts?

Where in this small space do you want to show individual info? Yes, by right-clicking would work, but then you have to go through all of them. Or could we maybe have a narrow colour line on top of each group at the least, showing the group's overall health? Thus, we would at least see health per unit type: I wonder how health of the 11 units could be shown individually, besides by right-clicking or - a bit faster? - hovering over them and then popping out the individuals. Maybe like this, i.e. when you right-click or hover, they pop out (quick & dirty - I'm no artist ): But if you garrisoned 20 units, there would be no room for that many.

You mean that 0 A.D. 64bit on Linux is faster than 32bit on Windows 10 on the same hardware?

PS: How can I create the diff restricted to this patch, i.e. to the changes in '/binaries/data/mods/public/simulation/helpers/Commands.js'? I don't want to include the previous changes in '/binaries/data/mods/mod/gui/modmod/modmod.xml'. If I diff now, the patch includes both changes. Do I have to undo the other changes first, or is there another way?

Thanks for the nice trick with commenting that line - works like a charm, i.e. the text is translated. And thanks as well for the explanation about the debug messages. Oh my, I learned so much today.

@nwtour Would you mind that I provide your patch in https://code.wildfiregames.com? See below (not full context): /** * Sends a GUI notification about entities that can't be controlled. * @param {number} player - The player-ID of the player that needs to receive this message. */ function notifyOrderFailure(entity, player) { let cmpIdentity = Engine.QueryInterface(entity, IID_Identity); if (!cmpIdentity) return; let cmpGUIInterface = Engine.QueryInterface(SYSTEM_ENTITY, IID_GuiInterface); cmpGUIInterface.PushNotification({ "type": "text", "players": [player], - "message": sprintf(markForTranslation("%(unit)s can't be controlled."), { - "unit": cmpIdentity.GetGenericName() - }), + "message": markForTranslation("%(unit)s can't be controlled."), + "parameters": {"unit": cmpIdentity.GetGenericName()}, + "translateParameters": ["unit"], "translateMessage": true }); } Currently, I don't know, though, how to test it. I would need to have a unit that cannot be controlled - for whatever reason. Thanks for sharing further thoughts from your end.

Commands.js starts with this: // Setting this to true will display some warnings when commands // are likely to fail, which may be useful for debugging AIs var g_DebugCommands = false; Does this mean that the message I saw and which @nwtour kindly provided in the screenshot above, only appears if g_DebugCommands = true? It's set to false on my end, so I wonder why I saw this message at all.

Is it worth the effort?

Is this an easy task? (for me) Where can I find more info about it? Thank you!

I agree. Here a kind of "rubberband effect" would be positive - not they should follow the players but follow each other. What would this mean for maps that have animals scattered all over, though? Should they find each other? I refer to animals of the same type.

I'm curious: Will performance be better with 64bit on Windows? Only if using more RAM? How much at least?

By hippos!

Yes, I just hit "Continue", entered some info, and added O7 (CatchAll) as Reviewers. Thanks to @maroder and @Angenfor helping me with my first diff.

I agree that an average health status across all garrisoned units is less helpful when trying to quickly decide which ones to ungarrison. Maybe somw others would like to share their thoughts about this? @Stan`, any ideas?

@wowgetoffyourcellphone Very nice! Can sharks attack small fisher boats?

Can somebody please explain how turrets in wall segments or wall segments themselves behave attack-wise - manned or not? Not manned, they don't shoot anymore, right? What when they are manned? Which advantage have distance-fighting units (e.g. archers) when garrisoned on turrents of walls or on wall segments as compared to distance-fighting units standing on the ground? Is there currently a difference between turrets (by "turrets" I mean the higher parts between wall segments - you too?) and plain wall segmentswith regard to attacking possibilities (garrisoned/ungarrisoned)?

@wowgetoffyourcellphone Either I am too stupid or there is another reason why I don't see what you mean: The red "minus" and the corn(?) icons above the women's head are not explained in any tooltip - neither when I hover with the mouse over these signs over her head, nor when I check the CC. There are tooltips both for the women and for the CC, of course, but the meaning of the said icons remains unrevealed to me. If I am the only one, it must be me, and I would be happy to learn what I'm doing wrong. Thank you.

Hmm, but if you see the HP of individual units and want to decide unit by unit, it might take too much time. I was thinking about this game setting (top slider "Wounded unit health", here set to 33%): For our purpose (ungarrisoning units with let's say at least 90%?), this setting is not ideal, but one could adjust it to e.g. 90%. On the other hand, players might not like this high % for units with less health being treated as wounded, so maybe one could calc (100-x)%. In the above example, the setting is kept at 33% (i.e.units with less than 33% health are selected by the hotkey) but units with more than (100-33)%=64% are treated as "ok enough to be ungarrisoned". Admittedly, I'm not sure if these calcs make sense. Alternatively, there could be a second slider in the above shown game setting specifically for a threshold to ungarrison units (from whatever) if above that threshold health. I assume that overriding this in-game should be no problem, i.e. even if all garrisoned units have less health than the user set up, he can ungarrison them if needed. Maybe units should be ungarrisoned by the order of their health, top health first, almost dead last .

Done: https://code.wildfiregames.com/differential/diff/18563/

Erm, but wall segments have turrets between them. Or are we talking about something completely different?

And how would you control to ungarrison only one specific type of cav, e.g. cav with archers (but keep cav with e.g. swords and pikes in the CC? (or stable/barn - sorry, don't know the correct English word right now) Maybe the CC icon could get a toggle to ungarrison only healed units or not. (the amount of HP% for "healed" can already be set in the game settings) Would you prefer individual settings per each single CC etc.? I assume so, as in other areas you might not care so much if they have let's say at least 80% health only, e.g. just for hunting undangerous animals.

From all the discussion and recent changes, I still don't understand how turrets in wall segments or wall segments themselves behave - manned or not. Not manned, they don't shoot anymore, right? What is their behaviour when manned? Does it depend on the type of units they are manned with? Which units should one use to man turrets and wall segments? And by the way, same question for towers and outposts: Can only archers improve something or also pike men? Is an advantage linked to the use of units with the ability to distance attacks only? Are tooltips and the like also adjusted when the behaviour of e.g. walls in this case is changed? Thank you.

But once you set entity variety and started a game, the behaviour would not change, right? Maybe I'm missing the point, but why is rotation (or non-rotation) of the (square) obstruction and different snap of neighbouring buildings relevant if it is either set off or on?

@wowgetoffyourcellphone When I hover the mouse pointer (sword, not visible in the left screenshot) over that icon above the women, there is no tooltip. When I left-click it, it shows the usual info (right screenshot). Can you please let me know what I am doing wrong? Thanks!

Would you consider an option in the settings for this? Players could decide whether their visual recognition of the mines suffers or not. Could you disable mines rotation when the setting of entity variety is set to "0" and enable it otherwise?