Cannot reproduce. /c global.npc_worker = game.surfaces[1].create_entity{name="character", position={0,0}, force="player"} global.npc_worker.selected = game.surfaces[1].create_entity{name="iron-ore", position={0.5, 0.5}, amount=10000} global.npc_worker.mining_state = {mi...

Reproduction with moving train going for stop, only 5 inserters work

https://www.factorio.com/blog/post/fff-317 Issue is that you are using "path_resolution_modifier = -8". This means that abstract nodes cover 1 chunk each (32x32), but base node covers 64 chunks (256x256). At some point goal position is badly aligned because of resolution, chunk that contai...

I added missing entry in map-settings.example.json for [0.17.73] I am not sure if this value can be considered "default"

Duplicate of 76870 (that i fixed earlier today and forgot to respond)

yes. that intended. had to adjust the collision boxes to get it to work the way i wanted If that is intended, then OP's case was not a bug from start: oil-derrick-mk1 is defined to have entity size of 3x3 (because of collision box). Btw why not move this collision box definition directly to oil-der...

i see it bypasses check for pipe placement, i will investigate... hint: collision box is changed inside pypetroleumhandling inside data.lua when doing this: --((nat-from-oil))-- require("prototypes.functions.Natural-gas-from-oil-well") -- edit: Interesting - pypetroleumhandling_1.4.6/proto...

belt speeds are defined on prototypes during data stage and so cannot be changed later. Some mods would solve this issue in data stage by doing n deep copies of transport belt (lets keep n<10) with different speeds and then in game you could using lua, fast replace selected belts to different ones. ...

Any idea when are gonna be released latest pathfinder FFF changes? hint: Last week we mentioned the change to make biters not collide with each other, but that wasn’t the only biter-related update we released this past week. Somewhat coincidentally, this week’s updates have included something I’d b...

th0 wrote: ↑

Fri Oct 18, 2019 12:30 pm

Oyxd wrote further down that it is fixed, do you still need anything?

For now, no, thanks I found reproduction myself

th0 wrote: ↑

Fri Oct 18, 2019 12:30 pm

May I ask what was causing this?

unit group was deleted when we didn't expect that

Thanks for report, however it is duplicate of 76909.

Save from 6 minutes before will be useless since reproduction is quite fragile and many actions may prevent it from crashing.

Thanks for the report, do you have reliable way to reproduce this? Or could you share you save file?

Not a bug (in Factorio itself) PS: I used my own mod Schall Endgame Evolution ;) control.lua:256: -- Frames : Evolution Factor Components t = frame.add { type = "table", name="table_evo_pol", column_count = 3 } ------ pollution table.insert(captions, t.add { type = "label&qu...

0.17.70 changelog:

FactorioBot wrote: ↑

Tue Oct 15, 2019 8:19 pm

Bugfixes

• Fixed that personal roboports would function with literally no power.

should be easy: inserter read hand (pulse) -> memory cell -> inserter enable condition (uranium < 40) memory cell: arithmetic combinator "each*1 -> each" with output connected to input 0eNqVk92OnDAMhd/FlxVU/CzdFu2bVCsUgrdYHRLkmFGno7x7HVjNjFra6dwgmcTHx/6cM/SHBWcmJ9Cegax3AdqvZwj0zZlD+ienGaEF...

This is kind of engine limitation, when removing car from first surface, lua handle gets disconnected from car.

To workaround this, before teleport you may read car's unit_number and then after teleport find this entity on target surface.

For now this is minor issue

FactorioBot wrote: ↑

Tue Oct 15, 2019 8:19 pm

Scripting

• Added support to teleport car entity types between surfaces.

For now i will throw this request to Won't Implement because ability to teleport cars should solve your underlying issue.

i think zoom follows exponential curve with coef 1.05 between zoom levels but i may be wrong

If you enable replay wouldn't that record everything needed to go back to the last tick where client and server agreed and then single step each tick to find where they diverged? Almost yes(not undo, only replay from start to given tick), replay is just set of input_actions for each tick and so it ...

No. State contained in desync is some ticks later than desync occured because client seeing crc difference must send request "hey, something wrong, save me map for desync report" and this can arrive to server after some ticks later. Game being deterministic means that `f(state, input_actio...