The game doesn't care if you burn the robot baby

[eriktorbjorn]

The game will point out if you drown the baby, even if the baby is inside a container:

>PUT BABY IN BASKET
The baby stops crying and, in the comfy warmth of the blanket, slips into a calm
sleep. A peaceful smile creeps over its face.

>PUT BASKET IN CANAL
"Glub." It's gone, you heartless baby murderer, you.

But it doesn't care if you burn the basket:

>PUT BABY IN BASKET
The baby stops crying and, in the comfy warmth of the blanket, slips into a calm
sleep. A peaceful smile creeps over its face.

>BURN BASKET WITH TORCH
In an instant, the wicker basket is consumed by fire.

Drowning is handled by CANAL-OBJECT-F:

              (T
               <REMOVE ,PRSO>
               <COND (<AND <PRSO? ,TORCH>
                   <FSET? ,TORCH ,ONBIT>>
                  <TELL "\"Phfffft!">)
                 (T
                      <TELL "\"Glub.">)>
               <TELL "\" ">
               <COND (<FSET? ,PRSO ,PLURALBIT>
                  <TELL "They're">)
                 (T
                  <TELL "It's">)>
               <TELL " gone">
               <COND (<OR <PRSO? ,BABY>
                  <ULTIMATELY-IN? ,BABY ,PRSO>>
                  <TELL ", you heartless baby murderer, you">)>
               <TELL ,PERIOD-CR>)>)

But there is no corresponding check in V-BURN. I'm not saying we should fix this, but it does seem like an oversight.

[eriktorbjorn]

It also doesn't care if you drop it in the catacombs, though it's unlikely that you'll ever carry the baby there:

>DROP BABY
With a splash, the robot infant is lost forever.

That message comes from SPECIAL-DROP.

[arcanetrivia]

It may be an oversight, although if the robot baby is metal or some other non-flammable material, perhaps it's logical that the baby doesn't burn and isn't thereby killed... but it still seems like it should complain if it's in the basket at the time!