Armed response arrives and everybody ends up standing in the open, because there is nothing to stand behind. This adds the shield — carried, dropped, planted, and restricted to the officers who should have one.

Two shields, or as many as you like

Ballistic and riot shields ship configured. Both are models with behaviour attached rather than hard-coded special cases, so adding a third of your own is a config entry instead of a rewrite.

Getting one out

Equip from an inventory item or with a command, whichever suits your force — both are switchable. If neither fits how your department works, the default command and items can be turned off entirely and the shield equipped through exports from your own resource.

Carrying it properly

A weapon check keeps shields to the sidearms you allow, so nobody advances behind one carrying a rifle. Actions that should be impossible while a shield is up — climbing a ladder, plus any controls you nominate — are blocked while it is deployed. One key drops the shield; another plants it on the ground so a unit can take cover behind it.

Fitting it in

Models, animations and behaviour are all configuration, so the shield can be tuned to how your department trains rather than to how the script was written. It idles at 0.00ms and costs around 0.01ms while a shield is actually being carried.