Factorio Forums

Killkrog wrote:When it comes to factorioblueprints.com I have absolutely no control over the content there. The site is exclusively maintained by Dave.
When the blueprint books were a new thing, I even contacted both Dave and Choumiko and tried to convince them to unify the exported strings between our three mods, but they completely ignored me.

Kryzeth wrote:Hello, Mr. Person! First of all, thank you for the great mod, loving the blueprint flipping feature!

Anyways, I am the Kryzeth person from the mod portal who commented about using a mod that gave blueprints and bots from the start, without giving the research, so it seems you added a player command to forcibly enable blueprint manager.
Of course, it wasn't exaactly what I was aiming at; I had actually been asking for a config option of sorts within the mod itself that would allow blueprint manager at start, if a player wanted. It could default to off, so only the core mod-players would find it and change it, but it would be reeeally helpful to have!

It's not much of a problem, if it would be too difficult to do, but thanks either way!

madpav3l wrote:Could you add a button for this?

DaveMcW wrote:Sorry for ignoring you, but your proposed format was kinda big and I am all about making strings smaller.
I have nothing to do with factorioblueprints.com.

Kryzeth wrote:I had actually been asking for a config option of sorts within the mod itself

Killkrog wrote:

madpav3l wrote:Could you add a button for this?

Implemented for next update.

Killkrog wrote:introduce a nice way of handling user settings (World of Warcraft did a really good job with those)

DaveMcW wrote:your proposed format was kinda big and I am all about making strings smaller.

siggboy wrote:it just has to be a simple key-value store

siggboy wrote:for example, the blueprint manager could store the blueprint library in the config and then you could load it from another savegame

Peppe wrote:Arn't config changes lost when mods update?

Killkrog wrote: Config.lua files suck. They may be okay if you use a mod only in single player, but as soon as you join a server, every client would have to need the exact same config file. Since I want this mod to be 100% MP friendly, you will never see a config.lua. Also, as Peppe already said, every time I will post a update to the mod the config.lua will be overwritten.

Kryzeth wrote:

Peppe wrote:Arn't config changes lost when mods update?

You assume that I would ever update a mod without redoing the changes I made to said mod =P

Killkrog wrote: Config.lua files suck. They may be okay if you use a mod only in single player, but as soon as you join a server, every client would have to need the exact same config file. Since I want this mod to be 100% MP friendly, you will never see a config.lua. Also, as Peppe already said, every time I will post a update to the mod the config.lua will be overwritten.

Oh... well I'm sorry that you think that way. Personally, if I were playing Factorio multiplayer, I would simply send my entire mod folder (because I make many changes, modifying both configs and other internal parts) to the friends I was going to play with. It's not like I'd be playing with randoms or anything.

Mods don't auto-update; players still have to manually update them. And in theory, the config would only ever apply at first run (on new game) so even if it were overwritten by a later update, it shouldn't change that the blueprint interface was unlocked. I mean, I think. I don't know exactly how you have it set up internally, so maybe it might function differently than I think.

Oh, and I'm not the developer of the quick start mod I mentioned, I'm just using it. Either way, I wouldn't know how to call parts of a mod from within another mod...

local fix
--Double inventory
fix = data.raw["player"]["player"]
fix.inventory_size = fix.inventory_size*2

--Color Coding Fixes
fix = data.raw["item-subgroup"]["color-concrete"]
fix.group = "logistics"
fix.order = "y"

fix = data.raw["item-subgroup"]["color-lamps"]
fix.group = "logistics"
fix.order = "z"


local COLOR_TABLE = {}
COLOR_TABLE["red"    ]={r=1.0, g=0.1, b=0.1}
COLOR_TABLE["orange" ]={r=1.0, g=0.5, b=0.1}
COLOR_TABLE["yellow" ]={r=1.0, g=1.0, b=0.1}
COLOR_TABLE["green"  ]={r=0.1, g=1.0, b=0.1}
COLOR_TABLE["cyan"   ]={r=0.1, g=1.0, b=1.0}
COLOR_TABLE["blue"   ]={r=0.1, g=0.1, b=1.0}
COLOR_TABLE["purple" ]={r=0.5, g=0.1, b=1.0}
COLOR_TABLE["magenta"]={r=1.0, g=0.1, b=1.0}
COLOR_TABLE["white"  ]={r=1.0, g=1.0, b=1.0}
COLOR_TABLE["black"  ]={r=0.1, g=0.1, b=0.1}
COLOR_TABLE["fire-left"   ]={r=1.0, g=0.5, b=0.5}
COLOR_TABLE["fire-right"  ]={r=1.0, g=0.5, b=0.5}

for color,rgb in pairs(COLOR_TABLE) do
	fix = data.raw["tile"]["concrete-"..color]
	fix.minable["result"] = "concrete"
end
 
fix = data.raw["tile"]["hazard-concrete-left"]
fix.minable["result"] = "concrete"
fix = data.raw["tile"]["hazard-concrete-right"]
fix.minable["result"] = "concrete"

--homeworld fixes
fix = data.raw["recipe"]["concrete"]
fix.ingredients = {{"stone-brick", 5},{"iron-stick", 1},{type="fluid", name="water", amount=10}}

--Mine sand with any miner
fix = data.raw["resource"]["sand-source"]
fix.category = "basic-solid"

fix = data.raw["mining-drill"]["sand-collector"]
fix.resource_searching_radius = 2.49
fix.resource_categories = {"basic-solid"}

fix = data.raw["recipe"]["sand-collector"]
fix.enabled = false

fix = data.raw["item-subgroup"]["fluid"]
fix.group = "intermediate-products"
fix.order = "z"

script.on_event(defines.events.on_player_created, function(event)
game.players[event.player_index].color = {r = 0, g = 1, b = 0, a = 1};
end)

Kryzeth wrote:It's kind of annoying to have to come back to the Factorio forums every time I want to start a new game, just to copy/paste the command.

Killkrog wrote:That's the reason god gave us text files

Peppe wrote: It only takes once for you to update mods in game and miss a mod that you have modified the config for and now your save may or may not work the same as before.

Killkrog wrote: I guess you did something like this?

Code: Select all

if remote.interfaces["KBlueprints"] and remote.interfaces["KBlueprints"]["Always Show GUI"] then
	remote.call("KBlueprints", "Always Show GUI", player)
end

for name, version in pairs(game.active_mods) do
  if name == "KBlueprints" then kblue = true end
end

if kblue then
  remote.call("KBlueprints", "Always Show GUI", game.players[event.player_index])
end

Neemys wrote:Are you working on a fix right now?