Hello there!
I have a block which when placed, transforms itself and stacks more of itself on top of it in order to create a natural spike formation. When the player places it, the spikes are generated as intended. However, upon using features, said block generates but the block doesn't create spikes. The spike creation is an event in the block controlled by minecraft:queued_ticking. Is it a built in feature that queued ticking blocks won't tick if created by a feature, and if so, is there a workaround?
#Blocks Generated by Features don't Tick
1 messages · Page 1 of 1 (latest)
Known issue, ticking and onPlaced do not get trigger via world gen
Ah, that is rather unfortunate. Is it counterable if the block were to be created by a structure-type feature?
Theoretically, having a commandblock thats on loop then setblock the block youre trying to generate should trigger the ticking again
So you're saying that would work with a Structure-Type or would it work with let's say, a Single Block feature?
I'm saying save a 1x1x1 structure that contains a command block thats on loop to setblock itself into your block. So yes, the structure feature instead of single feature
Alright, thanks so much!