Thanks for the reply Stan, Cool, yes. I agree that patches speak louder than forum discussions.  Unfortunately, I don't currently have the skills (nor the time) to produce one. Truthfully, this was just a thought I had and figured I'd put it out there. Thanks for helping to coordinate development on a pretty cool game. 

Same reason, the cost of integrating, testing, bringing up to standards has not been undertaken.

Hey, I'm Stan. I'm technically no longer the leader though. Regarding changing this gameplay mechanic aside from convincing some people you'll have to make a patch on Gitea. There are a lot of great ideas, but developper timer is scarce, and patches speak louder than words   Do note however that having a patch doesn't mean it'll get merged.

Hello everyone! We just branched for R28. The nightly-build tracks the state of R28 and can be used to test the new version. It is generated weekly, and you can get it using SVN. Detailed information can be found on the wiki Mock Release Bundles are also generated weekly, from the nightly build. They can be downloaded from our Jenkins build system. Future RCs will be taken directly from here. A higher overview of the release process can be found at [RELEASE PROCESS] Release 28 The contribution work-flow is not stalled during the process. We are still merging the work of devs and contributors into the repository, for inclusion in the future releases. The preparation of Release 28 is made in parallel, and not blocking. That said, most of our energy is dedicated to the release, and you will experience delays in us reviewing contributions. Please make sure no mods are enabled when testing the game. What should I test? While we encourage you to test everything, we expect most regressions to be related to those changes: In the match-setup a player can be removed and might interact badly with joining player or so. The size of Strongholds have been refined. The Germans have been introduced and might not be balanced well. The font rendering changed. Especially non-Latin fonts should be tested. Some parts of the game now use js-modules. We want to know whether it's still easy to mod those. There is now a x86-64 and an AppImage build. What should I report? Not everything. We know about two apparent issues related to sound: #8342 #8426 Apart from that we must fix regressions (stuff that used to work, but doesn't work any-more) and critical issues that would prevent the users from playing. We cannot reasonably fix all the existing bugs in the release. Critical issues include crashes and multi-player OOS. How to report them is detailed in the ReportingErrors wiki page. With the weekly generation of testable game versions, it is absolutely necessary to check you use the same nightly build (version is displayed in the main menu) without any mods when testing for OOS. Happy testing!

From what his previous posts said, it seems that porting the campaign isn't an easy task.  BTW, I still don't know why this one hasn't been integrated in the main game, since it would have been a big - even if high maintenance - asset.

Noup, I solved changing my laptop bc I wanted a Mac so long ago.