Try this
data:extend({
{
type = "recipe",
name ="coal-craking",
category = "chemistry",
enabled = "false",
energy_required = 5,
ingredients = {
{type="item", name="coal", amount=12},
},
results = {
{type="fluid", name="crude-oil", amount=4},
},
subgroup = "fluid",
icon = "__base ...

your code is not wrapped properly, see below
{
type = "recipe",
name ="coal-craking",
category = "chemistry",
enabled = "false",
energy_required = 5,
ingredients =
{
{type="item", name="coal", amount=12},

},
results=
{
{type="fluid", name="crude-oil", amount=4}
},
subgroup = "fluid ...

try adding the following to all of your rails in prototypes

type = "assembling-machine",
crafting_categories = {"no-recipe-category"},
fixed_recipe = "no-recipe",
ingredient_count = 0,

and then adding the following to your recipes
{
type = "recipe",
name = "no-recipe",
enabled = true ...

Yeah, here's the appropriate onLoad stuff.
script.on_load(setup)

function setup()
global.onTickFunctions = global.onTickFunctions or {}
global.elevator_association = global.elevator_association or {}
global.item_elevator = global.item_elevator or {}
global.surface_drillers = global.surface ...

In multiplayer I have a wierd desync issue with one of our mods, I've tried to fix it to no avail and quite frankly have no idea what I'm doing anymore. I have the feeling that it has something to do with the transport belts not performing the same action on all clients at the same time. The desync ...

We are getting a desync error in multiplayer whenever items get stuck in the independent item elevators, as well as when they get stuck in the item elevators that come with the surface drill. Isolated the issue from earlier, I think it has something to do with the move_items function.

Line 52 of control.lua causes a crash when attempting to create world in singleplayer, here's the fix I found for it.

fixed a bug when placing multiple digging robot machines near each other, see my fork on github.

We can't get the digging robots to work in multiplayer because you are using the global player variable which only works in singleplayer. You will need to update to use the get_player method instead, which will need more parameters to be passed to most of your methods for player index, etc. See ...

We can't get the digging robots to work in multiplayer because you are using the global player variable which only works in singleplayer. You will need to update to use the get_player method instead, which will need more parameters to be passed to most of your methods for player index, etc. See here ...

Also encountered another bug, this time with the underground fluid tanks. Whenever piping more than 1 fluid into the tank by accident it crashes if the fluid in the tank gets below 1.
"Error while running the event handler: __Subsurface__/control.lua:426: attempt to compare boolean with number"

Ok so I changed line 364 from "if time_spent_dict == 0 then", to "if associative_table_count(time_spent_dict) == 0 then"


One of us got ----Error while running the event handler: __Subsurface__/lib.lua:86: bad argument #1 to 'pairs' (table expected, got number)----
did you remove the ...

Ok so I changed line 364 from "if time_spent_dict == 0 then", to "if associative_table_count(time_spent_dict) == 0 then"


One of us got ----Error while running the event handler: __Subsurface__/lib.lua:86: bad argument #1 to 'pairs' (table expected, got number)----
did you remove the ...

Ok so I changed line 364 from "if time_spent_dict == 0 then", to "if associative_table_count(time_spent_dict) == 0 then"


One of us got ----Error while running the event handler: __Subsurface__/lib.lua:86: bad argument #1 to 'pairs' (table expected, got number)----
did you remove the ...

Another bug occured after some testing with your dev version:
Error while running the event handler: __Subsurface__/control.lua:827: Invalid surface name: Surface names must not be blank and must be unique

This happened when we destroyed a drill and restarted the server because my friend was stuck ...

While in multiplayer errors out every time one of us tries to go underground after pausing when gui comes up, after crashing the server error reads:
"Error while running the event handler:
__Subsurface__/control.lua:290 Gui element with name teleportation_progress container already present in the ...