The WAILA methods get called at every frame render. This is not constant! I have a quite powerful PC and play with 300+ FPS in my test world. This will mean that I see a stuffed item every 1/3 of a second! You will need to use a tick handler for this. You can hook into the one that is already present in 'event.TickEvent'!

Also, you might want to do something about performance. I drop 30 frames when looking at a stuffed Relocator. Reading NBT is CPU performance expensive! You might want to make a field with the stuffed items and (again) use the tick handler to set it to null every second, so it's refreshed every second.

Will work on this now. Is their a existing hook for the event.tickEvent? Would this not be the same case for extraction modules? I got the int tick idea from there.

At least I can easily test this, my computer can also easily run at 250+ FPS, if I don't open minecraft fullscreen.

All TE/entity etc. update methods are called 20 times per second. The thing is, the screen must be rendered more than 20 times per tick. And at every frame WAILA must be rendered, which means it needs to know what it must show every frame!

'event' is the package Refined Relocation pakage where you can find a working tickhandler. The tick method will be called every update tick.

Yes, but how would I go about setting variables to null in the RelocatorHud handler? I tried using a set/get method, but that doesn't really work since it can't get access to the same variables (I think?).