[1.7.10] Radiant Heat From Lava

[Cyberdragon]

New guy here. I made my first mod, FlameIgnitions, it's still in very early development but it's posted to Github. Yes, I know there are issues with it, mainly that the wooden lighter doesn't use an event to light TNT (causing strangeness, I'll fix it later).

 

Since this is a hardcore mod, one of the things I want to add is lava burning things from a distance. I want to have it burn everything (animals, players, flammable blocks) within a certain sphere around it (about 4 blocks). But I don't know any way of doing this. Any ideas?

[Draco18s]

I would be interested in this as well.  What I'm doing at the moment (which doesn't set things on fire, but spawn a "smoke" liquid) is randomly look at blocks near a player and if its lava, do something.

[shieldbug1]

I don't know if this will work, but you can subscribe to the PlaceEvent. If it's a lava block, then save the BlockPos somewhere, and then later in a WorldTickEvent if the position is still valid, iterate in a sphere around the position and burn whatever up.

 

I'm not sure if the PlaceEvent works with generated lava however.

 

Maybe subscribe to one of the chunk population events?

[coolAlias]

WorldServer#pendingTickListEntriesThisTick is a collection of all pending blocks needing updating, calling Block#updateTick on each one as their time comes. Now, this may not help directly, since the collection is cleared each time and there is no hook at any time during the process, but there is WorldServer#getPendingBlockUpdates(Chunk, boolean) which could give you what you need. I've never tried messing with it myself, so I can't say for sure.

 

Alternatively, you could use ASM to patch Block#updateTick to fire an event, which you could then listen for and, if it's lava, check the surrounding area, preferably not too often.

[Draco18s]

Alternatively, you could use ASM to patch Block#updateTick to fire an event, which you could then listen for and, if it's lava, check the surrounding area, preferably not too often.

 

I was actually looking at ASM about two hours ago for another problem (making crops tick less often) and arrived at the conclusion that ASM is way too advanced for my britches.  I mean, I literally want to change "return 10" to "return 100" and I have no idea HTF to do that.

[shieldbug1]

To use ASM you must first

Then it's just a matter of figuring out what bytecode you want to change.

[Draco18s]

Or as I just said to a friend,

 

"I looked at ASM this evening and ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn."

http://s10.postimg.org/yawll0uad/back_eyed_loaf2.png[/img]

[Cyberdragon]

OH GOD! Bytecode now?

 

Also, from a performance in modpacks standpoint, some mods have large lava lakes and volcanoes, which could overload your computer. So I don't know how bad it would be to have it run every tick (since 20 ticks = 1 sec). Is there anyway I can count the ticks and have it run every, say, half second?

[Draco18s]

Every tick would be bad.  You'd want something more like every 1000 ticks.

Which will probably be "every tick, if random(1000) == 0, doSomething()."

 

As for mods that add large lava lakes, test your code out in the Nether.  I took my smoke generation code down there and found it was very poor, performance wise.  But I'll admit that was due to the fact that I was telling the game to spawn a ton of liquid blocks that then had to float up to the ceiling....

[shieldbug1]

if(world.getWorldTime() % 1000 == 0)
{
    //Runs every 50 seconds.
}

 

Now if Minecraft was multithreaded/thread-safe...

[Draco18s]

Might want to hash the blocks' position so they don't all run at the same time.

[Draco18s]

ASM

 

Programming Sucks at a high level of abstraction enough.  Having to think in single-byte instructions is maddening.

 

Two freaking days to write 11 lines of code that insert 2 lines (in regular Java) into BlockCrops.

 

#NeverAgain