updateTick() for Blocks is Being Slow

[Cyberdragon 1]

I've been trying to figure this out for awhile now. I have a block with an updateTick() and setTickRandomly() on true. https://pastebin.com/u1zz4LZT However, the ticks are incredibly slow, sometimes minutes apart. I found reference to a similar issue in a really old thread elsewhere, but no answer. I have tried playing with tickRate() with no effect, and also randomTick(). I tried doing something with scheduleBlockUpdate() by forcing a tick with onBlockAdded() then again in the updateTick() (massively bad idea?), and it sort of worked but led to strange and unintended behavior. Note: It does not need to be the full tick speed, just fast enough to not be noticeable in-game.

 

Strangely, it works fine for anything extending blockBush. Does it have to be a plant to work correctly? (I would think not)

[Draco18s 1928]

Blocks do not update every tick. That's not how that function works. 

 

tickRate() does fuckall unless you call it yourself. 

[Laike_Endaril 7]

In general I'm not sure I'd suggest using those methods for something you want to happen "every tick".  There are several different forge handles that fire on tick events, but I think the one you'd be most interested in is TickEvent.WorldTickEvent (this is the tick that usually happens 20 times per second for each given dimension, and is shown if you run the in-game command "/forge tps")

 

The other tick events can also be found in the same class (TickEvent).

 

Any chance you could tell us what it is you're trying to do every tick?  Better make sure it's not too expensive or you'll break the game pretty fast.

 

Edit 1 ===============

If you decide to subscribe your block itself to the world tick event, make sure you have it check the event to see what world it is for, or else each block will be using the event once for each loaded dimension.

Edited November 17, 2018 by Laike_Endaril

[Cadiboo 145]

3 hours ago, Laike_Endaril said:

In general I'm not sure I'd suggest using those methods for something you want to happen "every tick".  There are several different forge handles that fire on tick events, but I think the one you'd be most interested in is TickEvent.WorldTickEvent (this is the tick that usually happens 20 times per second for each given dimension, and is shown if you run the in-game command "/forge tps")

 

The other tick events can also be found in the same class (TickEvent).

 

Any chance you could tell us what it is you're trying to do every tick?  Better make sure it's not too expensive or you'll break the game pretty fast.

 

Edit 1 ===============

If you decide to subscribe your block itself to the world tick event, make sure you have it check the event to see what world it is for, or else each block will be using the event once for each loaded dimension.

This is pretty much the entire purpose of tile entities

[Cyberdragon 1]

The problem is tileEntities would probably cause way too much lag for the purpose (which is why I'm avoiding them). It only needs to spawn and despawn that block above it based on conditions, nothing more or less. And there will be alot of these blocks, they are naturally generating.

 

It also does not need to update every tick, just a few times per second. But why can plants do that (breaking when not on a solid block is an updateTick), but my block can't?

Edited November 17, 2018 by Cyberdragon

[V0idWa1k3r 308]

19 minutes ago, Cyberdragon said:

breaking when not on a solid block is an updateTick

Plants check whether they can stay or not when their neighbour changes, not when the block receives the update tick. Actually a lot of blocks work like that - crops, torches, end rods, flowers, fire, snow layers, cactus, chorus plants, tallgrass, mushrooms, sugar cane, vines, ladders, pots... I could go on but you hopefully get my point. All these blocks don't update(most of them don't even allow the world to "tick" them) but rather detect neighbours changing and re-evaluate themselves. See any of those block's classes to see how they do that. I would recommend BlockLadder since it is probably the least complex of them all.

 

If that doesn't work for you then you might need to use forge's WorldTickEvent to manually run whatever logic you need. There is really no way to make the block "tick" every X ticks without either using a TE(which you want to avoid) or scheduling block updates(which is just as slow as TEs are pretty much but has additional issues that can easily crash your world, especially if there are a lot of them scheduled, I've personally experienced the "ticknexttick list out of sync" issue as an example)

[Cyberdragon 1]

As I said, I have tried scheduled ticks and it does sort of work but yeah, it glitches. I'll try an eventbus with tick events then and see what happens.

[diesieben07 6112]

Doing it with a tile entity will not cause any more performance issues than ticking it in some other way. In fact, I have found repeatedly scheduled block ticks to be way less performant than just using a tile entity.

[Cadiboo 145]

9 hours ago, Cyberdragon said:

As I said, I have tried scheduled ticks and it does sort of work but yeah, it glitches. I'll try an eventbus with tick events then and see what happens.

Please don't, either make a TileEntity or use net.minecraft.block.Block#onNeighborChange