Just been wondering and need some clarifications on those TE Itemduct lag message that occasionally popped in the chat. It usually goes like this: # => BlockCoords {x,y,z] So what does the number # means and how high does it need to be to considered as bad because sometimes it showed a duct in my base but usually number 1 to 2. But there is also times when some ducts reaches number like 500+ and most of the time these coords pinpoint to a base that was already inactive for weeks or months, which means that its not even loaded but each time a high number or laggy duct appear, it usually ends up in some inactive island. Now does that mean this while this mod/program searches for a laggy duct, it ends up loading these inactive island?
The structure is most likely chunk loaded if u know these bases have been inactive for over 2 weeks please report it to staff via a ticket and they will try there best to remove it as fast as possible
So, the lack of reply from staff means I need to post proof or something? Well here goes.. As you can see from the TE Itemduct Lag message: So, I flew 50k blocks to this coords and this is the said base: So from this username you can use /stats player name to find out how active he is: Conclusion: So, in crash landing, chunk loader only supposed to work when you are online and this base is already inactive for more than a month. Suddenly being pick up by the TE Itemduct Lag plugin which in my theory, force loading this base, and now everyday we get this message saying that this inactive base has some laggy duct on it.
Ok, thanks for the clarifications. Also one more thing, are those number doesn't lag? Just wondering why those duct aren't removed yet. I guess its fine as it is if those number isn't anything big.
I was in the base few days ago and the servers was running at 20 TPS, so I didn't remove them. In the most cases it causes issues at 500+
