Factorio Forums

PiggyWhiskey wrote:It's semi-cheating as you can see where biter bases are all time. Even without radar

YukiHyou wrote:Found another bug for you!

The invisible "remote viewing" things that are on the ore patches are targets for biters.
This means they end up attacking the beacon in the middle of the ore patch instead of the miners a lot of the time.
Additionally, even after deleting the ore patches from the sidebar, the remote viewer thing stays there - and is still a target.

Narc wrote:Edit: Yup, found it -- somewhere in the reshuffling of the code, I managed to break the case where you return from a remote viewer, leaving the viewer around with no way to destroy it. I'll fix that as soon as possible and make it a new release -- be aware, I will also be bumping the minimum Factorio version to 0.12.9, as it fixes a rather heinous (if rare) bug related to remote viewing

PiggyWhiskey wrote:The console was spammed with "Invalid color value (resmon.lua line 455)
It was for a Bob's Mods tin ore field that was being punished by miners and god module 5's. It happened just as the field finished.

YukiHyou wrote:The invisible "remote viewing" things that are on the ore patches are targets for biters.
This means they end up attacking the beacon in the middle of the ore patch instead of the miners a lot of the time.
Additionally, even after deleting the ore patches from the sidebar, the remote viewer thing stays there - and is still a target.

• Calculate mining rate a bit like the production screen: Right now if you happen to mine nothing between 2 update cycles it shows 0/m. In this case i think it would be better to take the tick from the last rate that was not 0 and calculate the rate based on the old delta/current tick - last mined tick.
• Add a way to add entities to an existing one. I had an outpost with 3 different patches of ore and didn't manage to get there quick enough to add them into a single site (Same for an oil outpost with oilspots a couple hundreds tiles apart. So a button for each site to reenable adding a new patch would be great

Choumiko wrote:I love how it's not freezing when adding an ore field, might have to use that in resource combinator too.

Choumiko wrote:Some suggestions i haven't found on your issues:

• Calculate mining rate a bit like the production screen: Right now if you happen to mine nothing between 2 update cycles it shows 0/m. In this case i think it would be better to take the tick from the last rate that was not 0 and calculate the rate based on the old delta/current tick - last mined tick.
• Add a way to add entities to an existing one. I had an outpost with 3 different patches of ore and didn't manage to get there quick enough to add them into a single site (Same for an oil outpost with oilspots a couple hundreds tiles apart. So a button for each site to reenable adding a new patch would be great

Narc wrote: (which would also give an opportunity to reduce its duration -- 10 seconds is a long time to wait, and the only way to bypass the wait is to have another kind of ore handy).

Boogieman14 wrote:

Narc wrote: (which would also give an opportunity to reduce its duration -- 10 seconds is a long time to wait, and the only way to bypass the wait is to have another kind of ore handy).

Some kind of documentation probably couldn't hurt either. Only from this statement did I gather that the delay is there to allow adding multiple separate patches, I figured it was the counting that caused a delay

Narc wrote:But be aware I do currently have a known bug where sometimes an ore gets missed; I haven't looked into it yet, though it's probably as simple as adding 0.5 to the coordinates so the hit test checks the center of the tile instead of its top-left corner.
I, too, have been considering a better mining rate calculation method, perhaps taking advantage of multiple samples reaching as much as a minute back and doing some (possibly weighted) averaging -- but I like the last non-zero tick idea, too.

local function find_resource_at(surface, position)
    local area = {{position.x - 0.51, position.y - 0.51}, {position.x + 0.51, position.y + 0.51}}
    local stuff = surface.find_entities_filtered{area=area, type='resource'}
    if #stuff < 1 then return nil end

    return stuff[1] -- there should never be another resource at the exact same coordinates
end

Choumiko wrote:

Code: Select all

local area = {{position.x - 0.51, position.y - 0.51}, {position.x + 0.51, position.y + 0.51}}

Choumiko wrote:I think in the end the rate/m should be more or less the same as the consumption of the corresponding ore, even if the miners get backed up from time to time. The zero tick variant makes it a bit better, but not perfect.

Boogieman14 wrote:So clearly I completely missed that

Choumiko wrote:I love how it's not freezing when adding an ore field, might have to use that in resource combinator too.

Narc wrote:With Factorio 0.12.11 breaking all the things, I went ahead and updated...snip

PiggyWhiskey wrote:

Narc wrote:With Factorio 0.12.11 breaking all the things, I went ahead and updated...snip

YES! Amazing work. Off all the mods, This one I miss the most.

I'll test it immediately.

ccik wrote:But, for some reason, after loading a saved game, YARM shows all previously mapped ressource fields as depleted. (0 Ore left, -0 ores/min, never depleting). The only fix for this is to delete the fields, and remap everyone of them.

Narc wrote:

ccik wrote:But, for some reason, after loading a saved game, YARM shows all previously mapped ressource fields as depleted. (0 Ore left, -0 ores/min, never depleting). The only fix for this is to delete the fields, and remap everyone of them.

Hi there, I'm guessing you're on Factorio 0.12.13. In which case, you've definitely found a bug, but not in YARM: [0.12.13] Lua data de-serialization doesn't work.

As Choumiko has stated over in the EvoGUI thread, if you can downgrade to 0.12.12, it would probably be best if you did.

Narc wrote:Very much agreed on the ability to put an ore site back into "add" mode (which would also give an opportunity to reduce its duration -- 10 seconds is a long time to wait, and the only way to bypass the wait is to have another kind of ore handy).