All Activity

I bet the regret is mostly that you realized you cannot make the last point, and probably never will on any subjects, even something you know better about.

You didn't do anything wrong. Everyone shares your wishes, and your proposals are welcome. Just to be clear, nothing I said was directed at you. Sorry for bringing conflict into your thread. I get annoyed by the attitude of certain people who point fingers and look for someone to blame. That attitude contributes absolutely nothing. But I should have kept quiet.

@Stan` seems like some other mods have mismatch : "name": "xiiiad", "label": "XXI Century AD" https://mod.io/g/0ad/m/xiii-century-ad But isn't the file creation something we control and could make more flexible in the engine? Or we just want to enforce the rule anyway for other reasons?

The problem is that the results aren't very different. I suppose AI lacks training. And perhaps the ability to distinguish between fantasy and historically accurate designs.

mod.io link https://mod.io/g/0ad/m/moderngui looks like you're hitting the problem where it creates multiple folders because name don't match https://gitea.wildfiregames.com/0ad/0ad/wiki/Mod_Verification_Process

Thanks for the report @namename, I can reproduce. It seems it would happen for any mods that have uppercase name, as the folder seems to be a left-over from the temporary download files. It might be possible to fix this at it's root I'll investigate.

Linux Flatpak: ModernGUI folder capitalization causes multiplayer compatibility failure Environment Both had 0 A.D. 0.28.0 I had Linux, Flatpak installation. The other player had Windows version. I have also tried 0ad AppImage and Lutris installation, so the problem is not related to Flatpak. ModernGUI R28, alongside Community Mod and Community Maps 2 Problem After downloading and enabling ModernGUI through the in-game mod manager, two directories appeared in the mods folder: ModernGUI — contained the mod files (mod.json and mod.zip) moderngui — empty Both players had the same mods and versions, but the multiplayer lobby reported incompatible mods, despite the installed and required mod lists matching. The tooltip was saying we have identical mods, their versions, and their order. The mod.json contains: { "name": "ModernGUI", "version": "0.28.78", "ignoreInCompatibilityChecks": true, "dependencies": ["0ad=0.28.0"] } Workaround that fixed it Since the other player in their in-game mod manager had ModernGUI entry look like "moderngui"(lowercase) in their folder column, I copied the contents of ModernGUI into moderngui, selected the lowercase moderngui entry in the in-game mod manager, and the multiplayer compatibility check passed. We were then able to play together. Question Why does the game create both uppercase and lowercase directories for this mod? Is this a ModernGUI packaging/installation issue or a 0 A.D. Linux/Flatpak mod-discovery issue? Could the folder-name mismatch cause the game to load or compare the wrong mod entry, despite ignoreInCompatibilityChecks: true? I can provide further details if needed.

!! I'm so glad! You've been pushing for battalion system, I've been hoping you'll take a look at this! Yes, I'm not entirely sure of the direction I would take from here. The battalions are using, as you might have guessed, barely modified UnitAI and Formation code as normal battles/vanilla 0A.D. So currently, the way you could do it is simply to have units in stand-ground stance. While playing the campaign, I had opportunities where it made sense : for example ranged units on high ground defending the acropolis, phalanx formation to defend a choke-point.. Example reproduction of the scene : Here I switched units into stand-ground so the melee block the choke-point and ranged units stay behind. The battalion cohesion (blue bar above the formation) gives extra bonus : The phalanx gives ~+5 armor but -50% speed at full cohesion. The ranged units get +20% attack range due to staying at high cohesion, and even more from terrain. So now I'm wondering : Is it worth rewriting all UnitAI and Formation code, (more work; diverging too much from base 0A.D.; unknown difficulties)? OR Keep it, and try to embrace the gameplay impact. But of course, it's not going to play exactly like TotalWar games. I tend to want the second more (also because I'm lazy) but it's possible I'll come to realize it's going to have too much cons.

Does it look like this https://gitea.wildfiregames.com/0ad/0ad/issues/7572 ?

tried this... what else can i try

More ChatGPT

ChatGPT^. Grok is not good.

Tried it. Really like it. Good concepts there. I wish the battalions stayed in formation, but I appreciate the direction it's heading in. I also think the battle maps should use the Aegean terrain assets, but hey.

"Fortune favours the Bold"

I feel that deeply, I've also had passions wither and die because the enthusiasm for them just wasn't being realised or cared for and in the end i was just doing it for myself, It's a tough one but never give up! even if it is on a small scale there are still people who appreciate what you do.

Your concepts are better and riskier than the base game. By riskier, I mean bolder.

Try switching from OpenGL to Vulkan or vice versa.

It's no big deal, honestly. I wouldn't take it too much to heart. I was once very passionate about making 0 A.D. into XYZ, but over the years realized no one shares my vision. lol Now, I only develop 0 A.D. out of spite. j/k. But anyway, the engine itself is slowly evolving to allow for more and more interesting things, even if the base game doesn't showcase them. Mods can and will take up the mantle as long as the capability is there.

I never wanted to create any conflict. I want collaboration: I want the gameplay people to help me, and I want the experts to help me too. But I can't handle the conflict. I don't have the energy for it. I want this game to be the AAA of open source. But I want us to do it together.

my characters are somewhat cloaked and they look like laser beams are bolting out of them?? help

@guerringuerrin of course it's hurtful to have the (many times unnecessarily extensively researched) whole body of one's input completely denigrated just for saying what many others have already said (and with a couple to "Like" such attack). But what is even more hurtful is when that comes from someone that seemed amongst the most reasonable people in the forum. My tag was just a reference to the campaign author, I could have omitted the @. What seems to me like a lack of humility is the apparent blindness towards non-competitive players, it's unfortunate that you put that on me when I'm only reacting with annoyance to the attitude "shorten timings and git gud", one doesn't even need any time in a forum, but with RTS, to find that mentality alarming (as happened in that thread). And there is a spectrum of it, many think the game is already leaning towards that extreme, and that a more centred presentation would benefit the growth of the game, and the less it affects the lobby players the better, but if some get jumpy even with techs that are there just for SP (as I think I mentioned in the only discussion I remember we had), then it's hard to say they even care about their experience (same with a couple of nice but held back recent proposals, not made by me). I don't even blame the whole lobby, or would go as far as to say people are pointing fingers, because you would leave no room to even address the issue.

Ah.. Well I guess you are right on campaign map, right click should just garrison the army. Basically here the city is just like your classical 0A.D. building. So to garrison you need to hold Ctrl+RightClick, as you would do to garrison a CC or any building in a game. It's true that because the campaign was built from ground, It didn't came to my mind that maybe some things could simplified with the hotkeys.

I tried station my army but I couldn't. Right click in the city wouldnt work

Mercator 0.12.0 is out (see start of this thread). Since the last release 0.11.3 quite a bit has happened (in fact so much that it could almost have been called 1.0) It stays a 0.x beta because it has been used by few people and almost only on Windows, and 1.0 should wait until it has been really used on Linux and macOS too. A great many of the ideas, and much of the testing, came from @lilypoppy - thank you! The starting positions, the heat map and the accessibility check were his ideas, the Q / W / E keys his suggestion, and his report from Ubuntu is why Atlas is found on Linux now. Mercator sets up a map's settings and players, forms the terrain's large structures, places walls and entities as the game does, checks the whole map, and hands it to Atlas (and takes it back) for the fine work Atlas is good at. post-Atlas comes afterwards checks maps and converts them for other game releases. And here below is a lot of text illustrating new features, but you might be wanting to test yourself and look at the documentation instead: Download from the first post of https://wildfiregames.com/forum/topic/169940-new-atlas-helper-tool-mercator/ I hope you can have fun creating maps! Changes in mercator 0.120: The big things A Terrain tab - the terrain formed before Atlas gets the map, shown as relief with its own 3D view. Start from flat ground, the map's own terrain, a greyscale picture or real elevation data (GeoTIFF, SRTM, DTED, ESRI grids - or a place chosen on a world map: its elevation is fetched once and kept). Then form it: a lasso that changes, copies or exports a piece of the terrain, and a low-pass filter that rounds off the terraces a heightmap leaves. areas raised, lowered or set to a height, and lakes: poured with a click, shown, or sunk to the water height - which is how you get a lake in the mountains with the map's one water height; rivers, roads (road, track or path), ridges and coasts, drawn and kept as objects you can change; a coast closed into a ring is an island, and the outer sea goes outside it. A river has two banks are the south / east and the north / west one, and Natural bends gives it steeper banks outside a bend and flatter ones inside; textures by rules (height, slope, distance from the shore, with presets for temperate, Mediterranean, alpine, desert and tropical land), with softened edges (the blocks you see in Atlas are the game's 4 m texture tiles) - and textures of their own for roads and rivers; Apply bakes it into the map's terrain; every earlier terrain file is kept under a dated name, and everything stays an object, so it can be changed again. And since the manual could not explain every parameter in words, each tool has a drawing of what it does to the ground - a profile of the road (across and along it), river, ridge, coast, area, lake and outer sea, with the parameters on it - small beside the tool buttons, enlarged by a click, and all in the manual. Starting positions (lilypoppy's idea). Choose a player, a civic centre or nomads, the starting units (the civ's own to begin with) and what goes round the start - biome, distance, trees, mines, berries, chickens - and click on the map: it is laid out as the game's random maps do it, as ordinary planned entities you can edit afterwards. The land each start begins with is outlined on the 2D map and in 3D by the game's own territory rules - far over open ground, short across deep water or a cliff, a border where the next player's start is stronger. Drawing tools in the Entity Placer: free curve, line, rectangle, polygon, ellipse. A shape can be moved, turned, edited by its points (a rectangle or ellipse by handles) and filled - the inside at a density, or along the outline every x metres, with a mix of kinds by weight, keeping clear of roads, rivers, lakes, the sea and cliffs. Clear inside deletes what stands in a closed shape; Check vegetation lists the trees on a road, in water or on a cliff, so you can delete them. A lasso selects what stands inside a free line, Q / W / E are the arrow, Move and Turn, and the selection can be made - and acted on - in 3D too. The same tools draw the Terrain tab's curves. A heat map of where units can go and an accessibility check (lilypoppy's asks): the ground coloured by the game's own passability classes - where a building can stand, where units walk, fords, deep water, cliffs, land nobody can reach - and a check in the Summary for players who cannot reach one another, resources nobody can get to, passages too narrow for siege engines, and a player with little room to build. A colour key explains every map view. Clearing that is part of the Entity Placer: Clear round the selection takes the trees, bushes and rocks out of the way of the buildings, walls, fields and shapes you select - and along the Terrain tab's roads and rivers, lakes and the sea - with a ragged, soft edge instead of a ruled one. Map packages: File > Open... takes a zip, a .pyromod, a tar or a folder of maps, asks which map when there are several, and never changes the package. More Draw walls has the rectangle and polygon icons: a closed wall of the set and player you choose. The Summary compares what each player's island holds (Balancing by Island) and what each starts with to fight, and checks for trigger scripts nobody has. The minimap is the map's preview, drawn from the terrain by itself and written with every save (unless you chose a picture). AI behaviour (random, balanced, defensive, aggressive) in Edit player; Help > Forum page...; Ctrl+S saves into the game; a map with no players is said when you leave Map Management; Undo goes back 50 steps. The little help (?) over a map says only what applies to the mode or tool you are in; tooltips are wrapped; the 2D maps are lit from the north-west so slopes can be seen. Fixed A large map showed as only its lower left corner in Atlas. The game reads a map's size from the XML, not from the terrain file; applying the terrain now tells the XML its size and the water's height. (Sizes beyond the game's largest, 512 tiles, are said to be untried.) "This install has no Atlas" on Linux (lilypoppy, Ubuntu 24.04): the launcher is nowhere near Atlas's library. Mercator now looks where packages keep it and, where it cannot tell, starts Atlas. The Entity Placer stayed empty after a crashed Atlas - it shows the map again as soon as the game lets go of its files. Thousands of trees were slow: with 10,000 trees an edit took 7 s, now 0.7 s. The Terrain tab's 3D window drawing nothing, an Adjust window taller than a laptop screen, cut-off buttons, and a help text that was too dim