Hacked Splitters 2.0


You've used your ingenuity as an engineer to hack your original splitter design, creating new splitters that perfectly balance transport belt inputs. These hacked splitters require extra circuitry and are best used with single-item belts as they no longer perform the function of their baser models. They unlock when their respective counterparts become available.

Content
6 days ago
2.0
88
Logistics

g Bug

a month ago

When placing a Hacked Fast splitter from map view the splitter defaults back to old splitter behavior. Might be the case for the normal splitter as well

a month ago

i dont think im able to fix any bugs by myself sadly

a month ago

script.on_event (
{
defines.events.on_built_entity,
defines.events.on_robot_built_entity,
defines.events.script_raised_built,
defines.events.on_pre_ghost_upgraded
},
function (event)
local entity = event.entity
if is_splitter (entity) then
-- Now we'll do the same-ol' creation logic for all of our
-- splitters irrespective of type.
local splitter = add_splitter (entity)
end
end
)

all you need to do to fix it is add these two additional defines. I added them to the whole function above. its on line 136 ish and its where you currently have on built entity and on robot built entity

  defines.events.script_raised_built, 
  defines.events.on_pre_ghost_upgraded

New response