I know this is a potential touchy subject most software developers don't like to see - but there are non-developers (like myself) who are not good enough in coding / SW developing to get a more complicated mod done: Now, If I specify and design and test a mod and ask an AI to code it - what does that mean? I'd like to discuss a few questions. Finally, it might be usefull to provide  guidance to others what vibe coding implies in this specific case: The mod might be using some code of 0AD  thus automatically inheriting the GPL v2 license. Do I need to tell which parts this refers to? The mod created by the AI should be checked by a tool like scancode (https://scancode-toolkit.readthedocs.io/en/stable/index.html) to avoid using accidentally, and not knowingly, other IPR. (AIs are typically trained with anything they can get including all kind of code repositories on the internet with various license models.) @Asher kindly provided a useful link for consideration  (https://seisan.com/ai-generated-code-intellectual-property-ownership/) but frankly, this leaves quite a few questions open. If a tool like scancode finds some infringement, what can I do? rewrite the code manually? Only use the "generated" code it for myself but not publish it? If I contributed to writing the mod by creating the ideas, design, specs and test scenarios and finally testing it - just not writing the code - does that justify a partial authorship? What does that do with the "right to use"/"right to publish"? Questions I'd also like to have your opinion on are these: Would such vibe code be acceptable at all as game mod? Under which conditions? (e.g. state how the mod was implemented, state any known dependencies etc.) Would it help offering instead of the actual code only its design documentation and a few screenshots as an inspiration to actual developers should they want to implement such a function? Would it make sense to provide issue reports of game code identified by the AI when implementing the mod ? Sorry for the long text, but I'd really appreciate your input and opinion on these subjects!

Oh no! Here I am again with another crazy concept how we could implement bridges  (sorry I don't give up ) Bridges could actually be walls with the turrets being the bridges pillars (appropriate art still to be designed. Like building that surface during the build process, the bridge could survface from the water until it reaches a certain  height above seal level. They can onyl be built in shallow and possibly medium shallow water. Building is done using fisherboats (animation needs to be invented). Bridges cannot be undercrossed by ships. Briges can be destroyed by siege engines and by war ships Now the most difficult and special thing: Bridges can be crossed by individual units one at a time if we garrison them onto the bridgehead, then they would automatically move "sideways" along the wall  from position to postion (if I remember correctly, walls have garrison positions), from segment to segment, until they reach the other side where they are automatically ungarissoned. there could be simple wooden bridges (cheap) only for infantry and civilians, and more expensive/wider wooden bridges also for cavalry, and heavy expensive stone bridges (you would afford only in special conditions) able to transport also siege engines and elephants. I would like to do some testing using standard walls and sideways "movement". It will look clumsy initially but we might eventually find a way to generate the right animations.    Gameplay-wise, bridges can serve as bridges, but also as barriers to protect a river mount or the space between islands. theri high cost may prevent unconditional use though.   Again, I'd be curious to know your thoughts on this!

Is there an easy way to see if techs are working?

That would be awesome! My core interest in this it to get a tool running for myself, and if it works, I am happy to share it.  I do hope this issue can be solved. I have more tools in the pipe (a simple keyboard visualisation mod, finished, showing to dudes like myself where the game hotkeys are on my particular keyboard also as a reference in-game), and I also have created a python-based map validator/converter (based on Stan's scripts and other infos I was able to gather) that takes a newly created Atlas map, or an old map, highlights issues and allows fixing them, and finally converts it into R28 or R29 (under test). I would also like to look into trying to introduce a mod testing sideways movement of garrisoned troops along wall segments to the point of attack, as well as a selling-back mod for ships/buildings and siege engines once you destroy them yourself.  While I do acknowledge that real software development is a serious task and requires a lot of knowledge (I don't have) and certainly a lot of effort, vibe coding is fun as well (and it still needs a bit af creativity and energy in definition and testing). Hence I would really like to know if and how I can share such results safely (even without a license if needs be).   The least we could probably use this for is to test mechanisms and concepts - so that we can obtain a spec and an "inspirational" design for real devs if they wanted to implement it in reality.