Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Doom barrel bug strikes again.

Recommended Posts

Hello Doomworld. I was playing the No End In sight beta release on E1M8 and a Baron destroyed a barrel and hurt a Demon, resulting in the Demon attacking the Baron. Later on as shown in this screenshot below, I ended up with a Baron attacking another Baron due to another barrel bug. Is the barrel bug very common these days? I was using prboom 2.5.0 with the Doom complevel settings configured in the menus.



Share this post

Link to post

Up to the latest versions of Doom 1 and 2 (1.9), if a monster destroys a barrel and hurt another one, this hurt one will try to kill the one who destroyed the barrel even if they are of the same species. By barrel destroying, you can see some very unusual fights like Cacodemon vs Cacodemon, Revenant vs Revenant and even Mancubus vs Mancubus.

Share this post

Link to post

The condition for starting an infighting is also quite more restrictive than people believe: if a "healthy" barrel is destroyed in a single hit, then no "barrel destroyer" is registered, and no weird infighting starts. In order for it to happen, a barrel must first be damaged little enough as to NOT blow up, and then when it blows up, the "blame" goes to the one who damaged it last without blowing it up.

In other words, it's possible to blow up a barrel and have someone else "take the blame" ;-) This is a bug due to how the barrel handling code works: an attacker is registered only if the barrel survives a hit from that attacker, and the barrel passes on this "attacker information" to its victims, if not null.

This is also why "barrel chain infighting" usually doesn't work in vanilla Doom and other ports than don't modify this behavior: barrels in a chain all blow up in a single hit, and no "transmission of blame" is possible. Some ports alter this behavior so it's possible to "transmit blame" down such chains.

Share this post

Link to post
yellowmadness54 said:

I believe it also causes monsters to fight themselves.

In earlier versions, it did. That bug was fixed though.

Share this post

Link to post

And to add one more to the pile, here's an example used in a max run (first level shown).

Excuse the heinously bad quality of the WAD (which I comment on in more detail in the video description), but this goes to show it does come in handy sometimes!

Share this post

Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now