This has been fixed in 1.12.0.9
Yes. Upon running my attached reproduction case in 1.12.0.9, I still get a frame drop from 60 -> 8 on getting the Molang component, with a further drop to 4 upon updating said component. (On updating/querying exactly 10 creepers in the world)
Here are some benchmarks of how much time does getComponent
and applyComponentChanges
take for the molang component provided by abc55#7088 on the Scripting Discord Server.
getComponent min: 20, max: 33, avg: 23.33, median: 23
setComponent0 min: 3, max: 7, avg: 4.171, median: 4
setComponent1 min: 3, max: 6, avg: 4.434, median: 4
setComponent10 min: 5, max: 11, avg: 7.25, median: 7
setComponent50 min: 17, max: 27, avg: 19.548, median: 20
setComponent100 min: 30, max: 50, avg: 34.986, median: 35
Where,getComponent
is system.getComponent(entity, "minecraft:molang")
setComponentN
is system.applyComponentChanges(entity, molangComponent)
where molangComponent
has N
variables
Well it seems the first number can go very low, closing.
Update: it is really messed up for many of the slots
Yeah I found out, just needed to turn the redstone dust 90 degress 😉
Confirmed 14w19a
I can see why this causes much lag, +vote
Confirmed, really miss this!
Confirmed
This will be needed for mapmakers!
Soon, please
Yes; please get this fixed. I asked him for help and then it turned out to be a bug! Please help!
TheDestruc7i0n
Here:
Still present in the latest, 1.13.0.9 beta.