Reignited: ReReignited Edition

For players:

Have you ever been out in the night when your entire stack of torches gets put out? How about spelunking down in a cave when you accidentally step too far into the water that has been streaming down next to you? Cooking a stack of torches to light them all again can be a hassle and is less immersive. You could be able to take advantage of the light and heat you find already around you.

Instead why not light your torches by touching them to the blazing campfire you already have? Or maybe poke them into the lava down at the bottom of the cave? Most firey things should do and any block that acts as a heat source in winter should be able to heat up your torches!

 

 

Used primarily to allow a player to light torches from a variety of sources including other torches. Lights the entire stack.

As of 1.17.0 you can light your torches off of:

• Lit: Forges, Bloomeries, Pit Kilns, Campfires, Ovens, Torch Holders, and of course Torches
• Still hot Ovens that are out of fuel
• Lava
• Loose fire like burning trees and hay bales
• Smouldering coal piles
• Plus any mod blocks that work as a heat source should automatically work as well.

 

Use Sneak+R Click like you would with a lit torch on any compatible block. Your torch should start smouldering with smoke particles if the block in question is valid.

For modders:

Adds a block behavior that allows an item to be held up to blocks that should be able to ignite it.

To add compatability, add the CanBeIgnited behavior to your item with properties defining the item it should turn into.

<pre class="language-markup">{ name: "CanBeIgnited", properties: {auto: true}} { name: "CanBeIgnited", properties: {domainToBecome: "theitemsdomain", itemToBecome: "the-items-codename"}} </pre>

&nbsp;

The auto property assumes you follow the vanilla convention of your lit and unlit items having the same name but swapping lit and extinct

When not using the auto property you can define any item as the lit version including changing the item to something completely different when ignited

domainToBecome should be the modid of wherever the new item is from and itemToBecome should be the full hypenated path

&nbsp;

Wildcarded paths are not yet supported when defining an explicit domain:path for an item, if you can use auto: true and leave a comment to show there's interest in a wildcard feature