Subscribe to download
[LATEST] CBA (Castle Blood Automatic) v13.1

The classic Castle Blood Automatic game (well, at least to me) with some updates and new features. I don't take credit for creating the original scenario, but I do hope you enjoy it! This was a popular scenario gamemode for me.

This IS the official latest patched version by Aeneas and me. Don't accept imitations!

IMPORTANT NEWS: Patch 4.0 made changes to how the workshop works in this game and I haven't gotten around to fixing it. If you go on multiplayer the scenario should be floating around.

The object of CBA is to destroy the enemy castles and protect your own. If
you lose all of your castles, you die. Itʼs a game with simple rules but
a lot of strategy.
Setup:
The game is typically played with 2 even teams, 3v3 or 4v4 usually. All players get a random civ.
Speed is on fast, visibility explored, resources standard, and population limit 200-500.
You start with 4 castles, a blacksmith and university in the back, a king in the back for selecting
the spawn distance, a ram and a tower for checking your number of razes and kills, and
some walls, gates, and towers. You cannot delete any of the gates or towers except for the
gate next to the castles / villager spawn.
Gameplay Rules:
1. Your civ’s unique units spawn repeatedly in front of your 4 castles with a population cap. If a
castle is destroyed, units will not spawn from it. Mass them up to attack!
2. Killing enemy units eventually lets you move up the ages. Everyone starts in feudal age
(except Vikings, which start in castle (remember the university upgrades!)). The number
of kills required to advance depends on the civ.
3. Getting a certain number of razes (not on walls) lets you get 2 villagers, which spawn next to
one of your castles. Different civs need a different number of razes. Once you get that
number, each additional raze gives you 2 villagers. You can use them to build stuff with
“infinite” resources. You cannot build too many walls or else they will be removed.
4. You are not allowed to delete buildings that are in danger of being razed (except castles).
Doing so is cheating.
5. You are not allowed to “full wall”: making a wall with no opening and no gate. That is
cheating!
Tips (or just figure this out yourself):
1. Block! “Blocking” is a technique commonly used in bloods where you place units on stand
ground to block off an area. Put your units on stand ground on the sides of your castles in
the little gaps when an enemy attack is threatening. If done right, the enemy will not be
able to surround your castles and attack them nearly as easily. You can also block gates
by putting units under them, which will make it hard for the enemy to attack the gates
(but this runs the risk of your units dying and leaving the gates open). Block yourself
when you need it, and block allies when they need it.
2. Teamwork is extremely important in this. Communicate a lot with your teammates.
3. “Set up” razes. If you are good at razing, damage a few enemy buildings without destroying
them so that allies who need razes more than you do or have archer civs can take the
razes and get villagers. Civs that are bad at razing take less razes to get villagers. You
could set up a raze for a British ally to give him villagers very early!
4. Know your role. Ranged civs are good for defense, so if you get one, you should help defend
your allies with less defensive civs. They are also good for support in attacks but not for
razing. If you get a razing civ (infantry unique units for example), it is your job to attack
most of the time.
5. Manage your forces, and maintain numbers in certain areas. If an ally is under attack by two
or more enemies, you may need to send help, but keeping pressure on an enemy is
sometimes also important. If an enemy is trying to build up with villagers, keep pressure
on him to prevent it, and try to assassinate his villagers. Make sure you have units in your
base in case of an attack.
6. Coordinate attacks. It is a good strategy to try and get everyone on your team to send massed
up forces to one enemy who is not in a good defensive position (such as one who has all
of his units out in combat).
7. Know when to let go of a teammate. Sometimes, it is best for everyone on your team to
attack the enemies as they are all focused on killing one of your teammates. Even if he is
unable to defend himself, sending help is sometimes not worth it. Sometimes, it is
impossible to save him because too many enemies are blocking him off.
8. Defend your teammate if he has the Huns, Goths, Persians, or maybe Teutons! Those civs are
bad at self-defense and great at attacking.
9. Use the right formations. Ranged units should be in line/block and on stand ground to
minimize surface area when fighting non-ranged enemies, otherwise in aggressive stance
and scattered or split formation if against ranged enemies. Non-ranged units should be in
scatter formation and aggressive stance when attacking anyone, but line formation is
sometimes better when trying to attack castles since they move a little faster, and nonranged
enemies cannot harm them as easily.
10. Know the game! Know what is good against what. Don’t do stupid things like using
skirmishers against mamelukes. Don’t feed kills to the enemies. Try and feed off of units
you can easily kill.
11. Be careful when you’re building. Don’t let your villagers die, and don’t let your enemies get
free razes. Make sure the area is safe.
12. Wait for the castle age or later to make units from stables, archery ranges, barracks, and (of
course) siege workshops. Remember that for each unit you make, a unique unit cannot
spawn from your castle because of the population cap. You can advance then mass up a
lot of buildings to pump out huge armies.
13. Wall up when you get villagers. Put walls in front of your gates with one spot open to make it
hard for enemies to attack the gates. Put a wall with a gate/opening in front of your
castles for added defense. Wall up your allies if they need it (especially if they are Goths).
You are not allowed to “full wall”: making a wall with no opening and no gate. That is
cheating!
14. Don’t bash your teammates unless they’re just not listening or something and seriously
deserve to be booted. CBA is a team game, and good players can often appear to be bad
at the game because they got unlucky or because their teammates failed to help properly.
If you think that a player isn’t very good at the game, whether or not you are correct, it’s
pointless to argue about it and destructive to teamwork ingame. Also, new players can
learn the game quickly as long as they communicate ingame, so don’t exclude them
unless they just don’t listen. Be nice.
(Written by Morshu9001)