Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Aklyon]

Wasn't there one with all of them?

[BigD145]

Wasn't there one with all of them?

Yes, and Aavak was a hidden traitor working for the biters.

[Aklyon]

Sounds like aavak.

[flabort]

One reason I'm excited to see Sean doing some modding is because I've started some work on an ambitious project of my own.

So tell me, besides the fact that I haven't added image links or defined the items that these ores produce, is there anything blatantly wrong with this code?

Spoiler (click to show/hide)

Code: [Select]

data:extend(
{
{
type = "resource",
name = "adamite-ore",
icon = --NOTE: FIX THIS LINE BEFORE DOING ANYTHING ELSE!!!!!
flags = {"placeable-neutral"},
order = "a-b-f",
infinite = true,
minimum = 500,
normal = 5000,
minable =
{
hardness = 1.5,
mining_particle = --FIGURE THIS OUT TOO
mining_time = 2,
result = "adamite-ore"
},
collision_box = {{ -0.1, -0.1}, {0.1, 0.1}},
selection_box = {{ -0.5, -0.5}, {0.5, 0.5}},
autoplace =
{
control = "adamite-ore"
sharpness = 1
richness_multiplier = 10000,
richness_base = 500
size_control_multiplier = 0.06,
peaks =
{ --I HAVE NO CLUE WHAT'S GOING ON HERE
{
influence = 0.2,
starting_area_weight_optimal = 0,
starting_area_weight_range = 0,
starting_area_weight_max_range = 2,
},
{
influence = -0.3,
richness_influence = -0.2,
noise_layer = "stone",
noise_octaves_difference = -3,
noise_persistence = 0.2,
},
{
influence = -0.3,
richness_influence = -0.2,
noise_layer = "coal",
noise_octaves_difference = -3,
noise_persistence = 0.2,
},
{
influence = 0.5
richness_influence = -0.5
noise_layer = "iron-ore",
noise_octaves_difference = -2.3,
noise_persistence = 0.2,
}
}
}, --This ends Autoplace, right?
stage_counts = {0}
stages =
{
sheet =
{
filename = --AAAAAAAH
priority = "extra-high",
width = 38,
height = 38,
frame_count = 4,
variation_count = 1
}
},
map_color = {r=0.2, g=0.1, b=0.56}
},

{
type = "resource",
name = "crystal",
icon = --AAAAAAAADD THIS TOO!!!
flags = {"placeable-neutral"},
order = "a-b-g",
minable =
{
hardness = 0.7,
mining_particle = --FIGURE THIS OUT SOON BOI
mining_time = 2,
result =
{
{type = "item", name = "crystal-shard", amount = 1, probability = 0.7},
{type = "item", name = "crystal-shard", amount = 4, probability = 0.1},
{type = "item", name = "crystal-whole", amount = 1, probability = 0.2}
}
},
collision_box = {{ -0.1, -0.1}, {0.1, 0.1}},
selection_box = {{ -0.5, -0.5}, {0.5, 0.5}},
autoplace =
{
control = "crystal",
sharpness = 1,
max_probability = 0.02,
richness_multiplier = 18000,
richness_base = 6000,
size_control_multiplier = 0.08,
peaks =
{
{influence = 0.1},
{
influence = 0.2,
starting_area_weight_optimal = 1,
starting_area_weight_range = 1,
starting_area_weight_max_range = 3,
}
}
},
stage_counts = {0}
stages =
{
sheet =
{
filename = --AAAAAAAH
priority = "extra-high",
width = 38,
height = 38,
frame_count = 4,
variation_count = 1
}
}
map_color = {r=0.9, g=0.45, b=0.45},
}
})

[Sean Mirrsen]

I can see nothing blatantly wrong. However, Lua is not a language I am intimately familiar with, I'm just getting by with general programming knowledge. The lack of exceedingly opaque syntax helps, as does the lack of need to track semicolons.

I can't offer any specific advice on modding resources, though, I haven't done any research into that myself. I know the autoplace uses some kind of gaussian or perlin noise thing for choosing where and how to place resources, but how to manipulate it in a non-random way I have no idea.

[flabort]

Hmm. Well, I guess I'd have to test to find out if I was doing that right then.

I've got a tiny bit more done, still no images (even placeholders). Not much change to the resource code blocks, just some commas added (Thanks Putnam!), but a code block for the items they give you and a couple recipes. I still don't have anything useful to do with the crystals, but hopefully they don't throw up errors by being in an inventory (besides the image-not-found errors).

Spoiler (click to show/hide)

Code: [Select]

data:extend(
{
{
type = "resource",
name = "adamite-ore",
icon = --NOTE: FIX THIS LINE BEFORE DOING ANYTHING ELSE!!!!!
flags = {"placeable-neutral"},
order = "a-b-f",
infinite = true,
minimum = 500,
normal = 5000,
minable =
{
hardness = 1.5,
mining_particle = --FIGURE THIS OUT TOO
mining_time = 2,
result = "adamite-ore"
},
collision_box = {{ -0.1, -0.1}, {0.1, 0.1}},
selection_box = {{ -0.5, -0.5}, {0.5, 0.5}},
autoplace =
{
control = "adamite-ore",
sharpness = 1,
richness_multiplier = 10000,
richness_base = 500,
size_control_multiplier = 0.06,
peaks =
{ --I HAVE NO CLUE WHAT'S GOING ON HERE
{
influence = 0.2,
starting_area_weight_optimal = 0,
starting_area_weight_range = 0,
starting_area_weight_max_range = 2,
},
{
influence = -0.3,
richness_influence = -0.2,
noise_layer = "stone",
noise_octaves_difference = -3,
noise_persistence = 0.2,
},
{
influence = -0.3,
richness_influence = -0.2,
noise_layer = "coal",
noise_octaves_difference = -3,
noise_persistence = 0.2,
},
{
influence = 0.5
richness_influence = -0.5
noise_layer = "iron-ore",
noise_octaves_difference = -2.3,
noise_persistence = 0.2,
}
}
}, --This ends Autoplace, right?
stage_counts = {0},
stages =
{
sheet =
{
filename = --AAAAAAAH
priority = "extra-high",
width = 38,
height = 38,
frame_count = 4,
variation_count = 1
}
},
map_color = {r=0.2, g=0.1, b=0.56}
},

{
type = "resource",
name = "crystal",
icon = --AAAAAAAADD THIS TOO!!!
flags = {"placeable-neutral"},
order = "a-b-g",
minable =
{
hardness = 0.7,
mining_particle = --FIGURE THIS OUT SOON BOI
mining_time = 2,
result =
{
{type = "item", name = "crystal-shard", amount = 1, probability = 0.7},
{type = "item", name = "crystal-shard", amount = 4, probability = 0.1},
{type = "item", name = "crystal-whole", amount = 1, probability = 0.2}
}
},
collision_box = {{ -0.1, -0.1}, {0.1, 0.1}},
selection_box = {{ -0.5, -0.5}, {0.5, 0.5}},
autoplace =
{
control = "crystal",
sharpness = 1,
max_probability = 0.02,
richness_multiplier = 18000,
richness_base = 6000,
size_control_multiplier = 0.08,
peaks =
{
{influence = 0.1},
{
influence = 0.2,
starting_area_weight_optimal = 1,
starting_area_weight_range = 1,
starting_area_weight_max_range = 3,
}
}
},
stage_counts = {0}
stages =
{
sheet =
{
filename = --AAAAAAAH
priority = "extra-high",
width = 38,
height = 38,
frame_count = 4,
variation_count = 1
}
}
map_color = {r=0.9, g=0.45, b=0.45},
}
})

Code: [Select]

data:extend({
{
type = "item",
name = "adamite-ore",
icon = --ADD ICON SOON
flags = { "goes-to-main-inventory" },
subgroup = "raw-resource",
order = "e[adamite-ore]",
stack_size = 50
},

{
type = "item"
name = "crystal-shard",
icon = --ADD ICON SOON
flags = { "goes-to-main-inventory" },
subgroup = "raw-material",
order = "e[crystal]-a[shard]",
stack_size = 100
},
{
type = "item"
name = "crystal-whole",
icon = --ADD ICON SOON
flags = { "goes-to-main-inventory" },
subgroup = "raw-material",
order = "e[crystal]-b[whole]",
stack_size = 50
}
})

Code: [Select]

data:extend({
{
type = "recipe",
name = "adamite-smelt",
category = "smelting",
energy_required = 3.5,
ingredients = {{ "adamite-ore", 1}},
result =
{
{type = "item", name = "iron-ore", amount = 1, probability = 0.3},
{type = "item", name = "copper-ore", amount = 1, probability = 0.3},
{type = "item", name = "stone", amount = 1, probability = 0.2},
{type = "item", name = "crystal-shard", amount = 1, probability = 0.2}
}
},

{
type = "recipe",
name = "crystal-whole",
ingredients = {{"crystal-shard", 8}},
result = "crystal-whole"
},

{
type = "recipe",
name = "crystal-shard",
ingredients = {{"crystal-whole", 1}},
result = "crystal-shard",
result_count = 6
}
})

[n9103]

There's a great deal of already existing modding code that are available for reference on the official forums: https://forums.factorio.com/viewforum.php?f=10
The Factorio wiki also has documentation on moddable aspects: https://wiki.factorio.com/index.php?title=Modding (particularly useful will be the Official API documentation)

[flabort]

Ooh. Thanks for the first link. I was already using the second, which is why I have any information on the Peaks section at all, as compared to nothing which is what I would have had.
Definitely will be looking over the sections in your first link, though. Thanks

[Finndibaenn]

since 0.12 there is also http://lua-api.factorio.com/ which is updated on every release. It doesn't replace the wiki, but is complimentary

[flabort]

Found that too, from the wiki.
Fingers crossed, I've got some placeholder graphics and filled in the graphics parts of the codeblocks and am trying to find my savefiles to back up just in case.
It's time to find out if I've horribly ruined everything with the "result = {MULTIPLE RESULTS}" things or if this actually works!

[Sean Mirrsen]

Ooh, hang on, i remember this one. If you're having results with probabilities (and multiple results are fine, see oil processing), in order for probabilities to matter you can't set "amount". You need "amount_min" and "amount_max", flat amount overrides everything.

[Sean Mirrsen]

Further experimentation with modding:

[BigD145]

You dirty cheater. Not dirty enough because you're using less power.

[Sean Mirrsen]

Hehe.

I'm currently trying to think of good ways to let the player see if the assembly line input is clogged with items that don't match the recipe inputs, so they can unclog it by running up and collecting them. I'll pretty definitely going to have to make a custom sprite and animation set for these.

Right now the plan is to have these "assembly line" buildings work as ultra-fast, inline assemblers. Still thinking about how to prevent them from being loaded via inserters from the outside, and whether it's a limitation worth pursuing. They'll be available for research around the same time as Assembly Machine 3's, starting with the basic version that only processes one-ingredient recipes. Then a faster version able to use two-ingredient recipes, and an even faster one using three-ingredient recipes, capping at that because I can only fit three inputs on the side of a 3x3 building. Each input will need to take one specific item (kinda like the chemical plant), but they will take those items basically as fast as the conveyor belts can carry them.

So it's all sort of notionally balanced. The point being optimization and speedup of some trivial construction processes (gears, cable, circuits, inserters, belts, etc) late in the game when you might really not want to deal with the limited throughput of assembling machines for those high-demand items.

[Sean Mirrsen]

Automatic smart inserter filter at the input to show what input is expected:


Custom graphics and works in all directions now:


They now also can not be loaded by inserters. Well, they can if you really really want to, but it's a very limited possibility. The way it works is that I found that inserters will not want to work at all, if their target destination is another inserter that has no free inventory. So what I did is extended the collision box of the hidden loading inserter to 3x1 covering the input side, and there are now two output inserters (filling both sides of a conveyor belt if there is enough production speed) that both have 1x2 collision boxes covering the space along the sides. A fast inserter would have only one spot where it could put things into the building, and that spot would be blocking the output line, defeating most of the purpose. You could still have a total of four long-handed inserters loading or unloading things from the two unoccupied tiles in the building's collision box that are required for the inserters actually operating in the building, but there is rarely a big benefit from doing that.

Still a lot of fancy scripting to do... and then there's the multi-input versions.... T-T