From Quake Wiki


"A spideresque hybrid horror. Keep your eye on the firepod he hurls."

Health 400
Gib threshold -90
Attacks Homing firepod (~30 dmg)
Drop nothing
1st appearance e2m6
Game version Registered
Death message Player was exploded by a Vore
† The data files for monsters that appear only in the registered version of Quake reside in pak1.pak rather than pak0.pak.

The Vore (also known as a Shalrath) is one of the toughest regular enemies the player will encounter in Quake. It is a three-legged monster that moves very slowly, but throws spiked bombs that home in on the player's position, making them often one of the trickiest enemies to deal with, especially in combination with other enemies.

The homing firepods (more commonly known as Voreballs or Vorespikes) that are thrown by the vore can follow the player around quite sharp corners when close enough, and do not explode until they collide with something. This can make them very tricky for a player to shake, especially on Nightmare difficulty, where they are fired more frequently and move faster than on lower skill levels.


Because of the danger posed by Voreballs, fighting Vores in large open spaces, or where the player is exposed but cannot easily move around (such as on a ledge) is not usually done. Many players deal with Vores from a position that provides cover and enables them to shoot at the Vore, then duck into cover until the Voreball explodes before re-emerging to continue their attack and wear the Vore down.

When fighting Vores in an open space, Voreballs will tend to accumulate in a trail behind a constantly moving player. Voreballs that are following the player can be used against other enemies quite easily, and by simply moving behind another enemy so that it is blocking the path of the Voreball, the player can start monster infighting to save both ammunition and time.

Since Voreballs will home toward the player gradually, they will often fly around obstacles that are otherwise blocking their path to the player when following very close behind. The best way to safely dispose of closely trailing Voreballs is usually to move quickly around a series of sharp corners, or run in a circle around a pillar or other obstacle. However, if the Voreball gets too close, it can become impossible to avoid in a conventional manner.

Additionally, it's important to know that the vore takes the full splash damage from its own spike. Skilled players can exploit the level geometry to make the vore balls explode almost immediately upon launch, thus gradually wearing the vore down with next to none detriment to own health and ammo supply.

Relationship with other monsters[edit]

Because Vores fire projectiles, and especially because these projectiles can be directed somewhat by crafty players, Vores often get into fights with other monsters. If the vore attracts the attention of multiple monsters, its slow speed often leads to it being killed by even weaker enemies such as Scrags.

One particular thing to note about the Vore is that it is one of the few monsters capable of gibbing a Zombie. This is enabled by a special case in the Voreball code that causes them to inflict extra damage to Zombies - 110 points of damage versus the standard 40 points.


Because Voreballs follow the player, they can be quite easy to use as a propellant for doing tricks. Since it is possible to run in circles and accumulate trailing Voreballs, it is possible to do Voreball jumps using more than one Voreball at a time, allowing a skilled player to jump extremely high.

Entity type point
Entity class monster
Dimensions 64 x 64 x 72
Quake-C shalrath.qc
Precaches progs/shalrath.mdl


Entity information[edit]

monster_shalrath is the entity for placing Vores in a level.


Vores are best placed where there is not too much easy cover, so that the player has to move around, or even run away to avoid getting hit by the homing bombs the Vore fires. Giving the player too much cover can make Vores boring to fight, as the player can safely take potshots without ever really having to worry about Voreballs hitting them.

Vores actually work quite well in open areas with little cover, as it forces the player to run from the Voreballs, and can lead them to drawing the Voreballs into other enemies to create monster infighting situations.

Using Vores in areas with cover can work if there are multiple Vores, making it difficult for the player to hide completely out of sight from all the Vores at any one time. Adding other monsters at ground level to keep the player from standing in cover also works well.



targetname The targetname of the Vore. When triggered, the Vore will wake up if inactive.
target The targetname of the entity to be triggered when the Vore dies.
killtarget The targetname of the entity to be removed when the Vore dies.


The monster_vore entity supports the following spawnflags:

Flag Common Name Description
1 Ambush The Vore will not wake up from seeing other monsters wake up or hearing sounds.

It also supports the standard spawnflags for difficulty and deathmatch presence.

Flag Common Name Description
256 Not on Easy The Vore will not spawn on Easy difficulty.
512 Not on Normal The Vore will not spawn on Normal difficulty.
1024 Not on Hard The Vore will not spawn on Hard difficulty.
2048 Not in Deathmatch The Vore will not spawn in Deathmatch mode.


FGD Definition[edit]

This is the format used by TrenchBroom and Worldcraft. Note that the model(...) parameter is not supported by Worldcraft. This does not include the Monster base class definition, which is also required.

@PointClass base(Monster) size(-32 -32 -24, 32 32 48) model(":progs/shalrath.mdl")
    = monster_shalrath : "Vore" []

DEF Definition[edit]

This is the definition format used for most old Quake editors, including the original QuakeEd.

/*QUAKED monster_shalrath (1 0 0) (-32 -32 -24) (32 32 48) AMBUSH