To accomplish this, I added a file called tributeManager.js. Tribute is paid and a notification appears in the chat box, but I'm also unsure if tribute is still paid when conditions change (vassal budget is lower than required and before the empire launches a war).

@Frederick_1 What Debian? Saying you followed the instructions is imprecise, as they are very extensive. But let's get to the point. Compiling from the 0AD sources is simple and straightforward. A preliminary note: The compilation files take up a lot of disk space – mine is about 10 GiB. If you don't have that much space, compile on an external drive. Even a USB flash drive will work, as long as it's formatted with a Linux file system, e.g., ext4. If you use Windows file systems (e.g., fat32, exfat), compilation will fail. Checking required dependencies. dpkg -l build-essential cargo cmake curl libboost-dev libboost-system-dev libboost-filesystem-dev libcurl4-gnutls-dev libenet-dev libfmt-dev libfreetype-dev m4 libgloox-dev libicu-dev libminiupnpc-dev libnvtt-dev libogg-dev libopenal-dev libpng-dev libsdl2-dev libsodium-dev libvorbis-dev libwxgtk3.2-dev libxml2-dev llvm minisign python3 rustc zlib1g-dev If something is missing, we install it. Next – with user rights: cargo install --locked cbindgen@0.29.0 echo 'export PATH="/home/user_name/.cargo/bin:$PATH"' >> ~/.bashrc source ~/.bashrc Command list without unnecessary comments. Debian 13.3 Trixie. All commands as a user. After compilation, we are only interested in the 'binaries' directory. mkdir -p 0.28.0_Final cont 0.28.0_Final wget https://releases.wildfiregames.com/0ad-0.28.0-unix-build.tar.xz wget https://releases.wildfiregames.com/0ad-0.28.0-unix-build.tar.xz.sha256sum wget https://releases.wildfiregames.com/0ad-0.28.0-unix-build.tar.xz.minisig wget https://releases.wildfiregames.com/0ad-0.28.0-unix-data.tar.xz wget https://releases.wildfiregames.com/0ad-0.28.0-unix-data.tar.xz.sha256sum wget https://releases.wildfiregames.com/0ad-0.28.0-unix-data.tar.xz.minisig ls-al minisign -Vm 0ad-0.28.0-unix-build.tar.xz -P RWTWLbO12+ig3lUExIor3xd6DdZaYFEozn8Bu8nIzY3ImuRYQszIQyyy minisign -Vm 0ad-0.28.0-unix-data.tar.xz -P RWTWLbO12+ig3lUExIor3xd6DdZaYFEozn8Bu8nIzY3ImuRYQszIQyyy sha256sum -c 0ad-0.28.0-unix-build.tar.xz.sha256sum sha256sum -c 0ad-0.28.0-unix-data.tar.xz.sha256sum tar xpf 0ad-0.28.0-unix-build.tar.xz tar xpf 0ad-0.28.0-unix-data.tar.xz cd 0ad-0.28.0 cd libraries/ nproc # We'll see the number: N, e.g.: N=8 ./build-source-libs.sh -jN # So -j8 cd ../build/workspaces/ ./update-workspaces.sh -jN cd gcc/ make -jN cd ../../../binaries/system/ ./test ./pyrogenesis cp ../../build/build_version/build_version.txt . # Don't forget the dot at the end DONE If the compilation completes without errors with the final message: "Linking test," this is good. If for some reason you need to repeat the compilation, before issuing 'make', run the command:  'make clean'. Archive the 'binaries' directory and its contents and transfer it to another PC with Debian 13.x Trixie installed. But first, delete all '*.a' files from the 'system/' subdirectory. Leave only the '*.so' files and the 'ActorEditor', 'pyrogenesis', and 'test' files. Alternatively, leave the 'readme.txt' and the previously copied 'built_version.txt'. Do not touch the 'data/' subdirectory. The 'binaries' directory and its contents take up 5.0 GB of disk space. If '0ad' has never been run on this other computer in an earlier version, first check for the following packages: dpkg -l libenet7 libfmt10 libgloox18 libminiupnpc18 END Best regards  

I have a list of custom bots for various purposes, but my newest bot has a slight change in how the ally operates, which probably counts as gameplay related, so I wanted to discuss it with everyone here. "I'm delighted to introduce the newest bot in my series of AI bots, the Protectorate bot. This bot represents a breakthrough in gameplay compared to the previous two, redefining alliance relationships. To play this bot, you need at least two players on the same team, both controlled by Protectorate. The player with the smaller ID will play the role of the "Empire," and the other players will be "vassals" (for example, if players 1, 2, and 3 are on the same team, player 1 will be the Empire, and players 2 and 3 will be the vassals). The Empire will prioritize military strength and trade, while the vassals will prioritize workers and pay 30% of their resources every 60 seconds to the Empire. This payment is waived if the vassal's resources are less than 20% of the Empire's resources and increases to 40% when the Empire launches an attack. The empire would also station troops in vassal states, with the number depending on the actual situation (this only happened when the empire's population exceeded 100)." https://wildfiregames.com/forum/topic/140686-other-ai-bots-besides-petra/#:~:text=I'm delighted to,population exceeded 100). I'd like to hear everyone's opinions.

Below are some statistics from a 2v2 match with 2 Protectorate bots vs. 2 Petra bots (Team 1 is Protectorate and Team 4 is Petra, unlimited population and average resources).

I'm delighted to introduce the newest bot in my series of AI bots, the Protectorate bot. This bot represents a breakthrough in gameplay compared to the previous two, redefining alliance relationships. To play this bot, you need at least two players on the same team, both controlled by Protectorate. The player with the smaller ID will play the role of the "Empire," and the other players will be "vassals" (for example, if players 1, 2, and 3 are on the same team, player 1 will be the Empire, and players 2 and 3 will be the vassals). The Empire will prioritize military strength and trade, while the vassals will prioritize workers and pay 30% of their resources every 60 seconds to the Empire. This payment is waived if the vassal's resources are less than 20% of the Empire's resources and increases to 40% when the Empire launches an attack. The empire would also station troops in vassal states, with the number depending on the actual situation (this only happened when the empire's population exceeded 100). bot_Protectorate_1.zip