|For other uses, see Yuri.|
Psychic blast can cause own casualties
In Red Alert 2, Yuri Prime is a stolen-tech unit which can be unlocked when a Soviet-controlled spy (either by mind-controlling a spy or by obtaining access to the Allied techtree) infiltrates a Soviet Battle Lab. An Allied spy infiltrating Soviet Battle Lab and having an access to Soviet barracks (also built or captured) will have the same effect.
Yuri Prime himself is simply a much more powerful version of the Psi-Corps trooper.
Yuri Prime is a potentially powerful force on the battlefield, with the ability to mind-control most units from a very long distance. Yuri Prime's mind-control range outranges those of most defensive structures and siege units and can thereby cause considerable havoc in the enemy camp without endangering himself. He is however, like all mind-control units, vulnerable to aircrafts and naturally-immune units such as robots, miners, commandos and attack dogs. Unless he is attacked he also does not mind-control when possible and needs to be given a direct order to control enemy units in order to do so.
Yuri Prime is a commando unit, which usually means only one can exist on the battlefield at a time, although two may be produced with a Cloning Vat.
- Compared to the Psi-Corps trooper
- Mind-control range outranges those of most defensive structures and siege units, even more so than a normal Psi-Corps trooper.
- More expensive than Psi-Corps troopers
- Unable to cross water in spite of levitation abilities.
- Psychic blast can still cause own casualties.
- Only one may be trained from the Barracks, although two may be produced with a Cloning Vat.
- Difficult to acquire.
- Yuri Prime is surprisingly not walking, but levitating above the ground. However, he is unable to cross water.
- A trick once used in earlier versions of Red Alert 2 was to send the unit into a hospital and when he emerged, another unit would be created at the Cloning Vat. This enabled unlimited access to Yuri Prime, or any other infantry unit for that matter. This was fixed in version 1.006.