jericho1060 / du-storage-monitoring Goto Github PK

I have a large factory with 100+ containers and hubs.
I kept getting CPU overloads on the init tick before it could build the table of containers.

I did some testing with coroutines, but nothing worked. I got some help from the people in the DU Discord's #lua channel, but nothing they suggested helped.

My hypothesis is that table.insert() is causing the CPU overload when the table has gotten too big somehow. Without knowing how this function works, I can't figure out what the cause is.

I could not find any workarounds that solved the problem.

i couldnt find another way to get ahold of you. Anyway we can get a version of this that will just pick up a container thats holding multiple ores and show the levels? Like we would name the container with only (s1) or (s2) and would show the resources inside? Would be willing to pay for it. i know others have this function but yours is the best looking and easiest to work with.

Or would be better actually if on your mining units monitor we could choose a second screen to output the container contents that the units get dumped into.

Hello, First of all, thank you very much for the script, it looks very good!, but I also didn't understand much how to make it work, first of all I don't speak English natively, so I am using the google translator to help me.

I wanted to know what the name of the containers is like, I currently have several containers, some with a single product and others with several, how is the itemid?

Excuse me if I didn't explain myself well.

First off, I like your script. It's small and easy to setup.

I would like to see groups. Maybe:

This would let us Group Pures, Ore and Products separately or even By Tier.

This could reduce number of screens you use.

You could do a but would let you do Subtitles (if enabled)

Just A feature request. Thanks for your time.

Version: 4.8.0

With the sorting option "none", the sorting of ingredients by name within tiers is not correct in my English environment.

On my programming board, I changed the following and it seemed to work:

            -- sorting by name
            for k,v in pairs(tiers) do
                table.sort(tiers[k], function(a,b) return a.ingredient.name:lower() < b.ingredient.name:lower() end)
            end

to:

            -- sorting by name
            for k,v in pairs(tiers) do
                table.sort(tiers[k], function(a,b) return a.ingredient.locDisplayNameWithSize:lower() < b.ingredient.locDisplayNameWithSize:lower() end)
            end