Official Factorio Wiki - User contributions [en]

User talk:Bilka

2024-11-10T10:38:57Z

Thoxo: /* Infobox Issue */

'''Welcome to ''Factorio''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:Mishka|Mishka]] ([[User talk:Mishka|talk]]) 13:07, 17 November 2016 (UTC)

== Templates that might need CSS cleanup ==
* [[Template:Outdated image]]
** Consider adding css for ''.boilerplate'' classes. This will put all the css of [[Template:Game image]], [[Template:Move]], [[Template:Screenshot]], etc. in one place and reduce loading times --[[User:Longtomjr|Longtomjr]] ([[User talk:Longtomjr|talk]])
<s>
* [[Template:Game image]]
</s>
--[[User:Longtomjr|Longtomjr]] ([[User talk:Longtomjr|talk]]) 11:37, 29 April 2017 (UTC)
=== Cleanup done ===
* [[Template:Key]]
* [[Template:Move]]
* [[Template:Disambiguation]]
* [[Template:Cleanup]]
* [[Template:Delete]]
--[[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) 11:52, 29 April 2017 (UTC)

: CSS has been merged into .factorio-boilerplate for all templates that use [[Template:Boilerplate]]. [[Template:Outdated image]], [[Template:Game image]], and [[Template:Screenshot]] still use .boilerplate. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 12:48, 9 February 2018 (UTC)

== Navigation box links ==

Hi Bilka! I found the misfunction on [[Factorio:Navigation|Navigation]] page. There are links to Navboxes in lower row of each Navbox but in all languages it links to English template. I'm going to change links. Please see the [[User:Snowball_II/Sandbox/ru|example]]. Is it OK to create pages [[Template:ProductionNav/ru]], [[Template:CombatNav/ru]] and so on? --[[User:Snowball II|Snowball II]] ([[User talk:Snowball II|talk]]) 22:50, 11 May 2017 (UTC)
 One more question. Is it OK to create pages with Russian names. For example [[Железная плита]] with redirection to [[Iron_plate/ru]]? --[[User:Snowball II|Snowball II]] ([[User talk:Snowball II|talk]]) 13:05, 12 May 2017 (UTC)

: Hi again. I have not received any response so i create pages [[Factorio:Navigation/Logistics]], [[Factorio:Navigation/Logistics/ru]] and change link on [[Template:ProductionNav]]. Don't you mind? --[[User:Snowball II|Snowball II]] ([[User talk:Snowball II|talk]]) 19:59, 15 May 2017 (UTC)

:: Hey there snowball. Not sure why Bilka didn't respond to you, but we are internally debating how to fix navigation boxes. Please leave it alone until we can form a consensus. As for creating russian redirection names, that's completely fine. --[[User:Gangsir|Gangsir]] ([[User talk:Gangsir|talk]]) - Admin 21:21, 15 May 2017 (UTC)

== German translation worldgenerator ==

Hi Bilka! I just tried to translate the page [[World_generator]] and for me it feels like the page is verry unorganized since it's not written with a intelligent order. So I stopped translating and tried to rearrange the site. My goal was, writing about the Generator in general, then talking about possible configurations, after that talking about the presets. This because it makes no sence for me to talk about presets if you don't understand what they actually change within the config. So I tried to build up the page like you see the menu ingame. I would like to hear your feedback on my attempt. [[user:Hoeloe/de|Weltengenerator Vorschlag]]

Another problem are those sheets with the preesets. I don't know right now if it makes sence to translate them and how. What do you think, can you help me?

Btw: Thanks for CoReading my stuff and checking for typos, I'm trying my best :)

Greetngs from switzerland [[User:Hoeloe|Hoeloe]] ([[User talk:Hoeloe|talk]]) 11:39, 1 September 2017 (UTC)

:Your organization definitely seems better to me. I think the biggest problem of the article is that it talks about the gui, its options and their effects, and about how the world generation works. Your organization somewhat seperates those topics, which makes the article more readable.

:Some possible improvements: Perhaps you could also list the presets and their descriptions in the first small section on them, and then put something like "Für genauere Information was die Voreinstellungen verändern, siehe [[#Voreinstellungen|]]". A link from the "basically it works with perlin noise" to the section that explains more about it would also be good. I think it might be a good idea to rework the preset resource table so that it only lists the ''changes'' from the default, instead of every single option, no matter if one of the presets changes it. Since the official game has translaions on everything used in the world generation gui, translating the rest of the tables shouldn't be too hard. It would be nice if you could do that reorganization also on the English page, "aber es ist kein muss".

:I appreciate how well you translate pages. I personally struggle with translating pages like Crafting or the World generator page because I am so used to the English words for things that I can't find appropriate German translations (even though German is my first language...). So thank you for your work on them! -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 12:12, 1 September 2017 (UTC)

::Thanks for your feedback. I will try to totally rewrite the presets part, but first I need to think about how to. I often use links, sometimes it feels too much for me, but the Perlin Noise one makes sence. There is one big point about the english page I struggle. The [[User:Hoeloe/de#Erweiterte_Konfiguration|Erweiterte Konfiguration]] is actually not covered right now. I don't know, maybe I will try to rewrite the english one, but I definitely need someone to check it since english is not my native language as well.

::I just translate the stuff 1:1, rearrange the sentence so it's readable in german and sometimes I switch some terms for better wording. But I know, sometimes you realy need to think about it since english can be written verry easy, flat and repeating while german can be very complex. I thank you for appreciating my work and also that you check it and help me. Ah and when you read my stuff particularly check for missing β's since this letter does not exist in the Swiss-Deutsche Rechtschreibung :) -- [[User:Hoeloe|Hoeloe]] ([[User talk:Hoeloe|talk]]) 13:30, 1 September 2017 (UTC)

:::Yeah, the advanced options just weren't added to that page yet because it hasn't really seen much of an update to 0.15. I can definitely check the changed page (or your WIP of a rework) for language or ask Gangsir to have a look at it. But what I can read from you right now, your English isn't too bad either :) As a heads up: You should translate page titles, like the title on the crafting page or on the campaign page, using the translation/de template instead of displaytitle. Oh and when you use the languages template, please don't put a blank line between it and the following text. Doing that creates some ugly whitespace at the start of the page. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 15:16, 1 September 2017 (UTC)

::::Okay, *hust* wieso sagt mir das keiner? Dann möge jemand die Anleitung aus dem Language Template entfernen! :P -- [[User:Hoeloe|Hoeloe]] ([[User talk:Hoeloe|talk]]) 12:43, 2 September 2017 (UTC)

:::::I don't see any instructions on that template page that mention using displaytitle. Only in the template itself, stating that it does that. Should I reword that comment? -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 12:56, 2 September 2017 (UTC)

::::::I just found this sentence in the language template and also in other translated /de articles. That was why I used it, I didn't know the translation template does this job. I need to say I'm not very used to wikis in terms of templates ''programming'' and stuff. Also there is no guide which explains all this.

::::::What do you think about my attempt of the english [[User:Hoeloe/sandbox|Wordlgenerator]]-page? I messed arround with the page again. The ''How it works'' part is now in ''Generation'', Made no sence to me to seperate this. I also changed that ''Generation'' is the first section (we can still swap this afterwards). The ''Presets'' part now does directly attend the individual presets. [[User:Hoeloe|Hoeloe]] ([[User talk:Hoeloe|talk]]) 08:04, 4 September 2017 (UTC)

:::::::Such a (style) guide is currently WIP. Just another thing that is missing documentation :/

:::::::Looks good so far. However, I think putting the technical generation info first isn't a good move. I imagine that the article is frequented by beginners who just want to know what changing the settings does, not how excatl the world is generated, or when chunks are generated. I think it would be a better idea to take the first few paragraphs of that section (up to the algorithm subsection) and leave them at the beginning of the article, perhaps without a header, more as a general thing. The rest of the generation section should be moved below the presets. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 12:44, 4 September 2017 (UTC)

== About <nowiki>{{translation/ms}}</nowiki> ==

Will do... and now I know how that template works. [[User:SNN95|SNN95]] ([[User talk:SNN95|talk]]) 11:14, 1 October 2017 (UTC)

== Shipwreck ==

I understand the merging, but did you really need to wipe everything? I worked a very long time on that stuff. I don't see the harm in the shipwreck getting mentioned. It is part of the game - something the player can interact with. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:28, 26 January 2018 (UTC)

:Well, the page had to go and I thought I had copied the relevant info. The problem is simply that we cant document the campaign only items at the same place as the freeplay items, that would only confuse the player; but making the shipwreck a subpage of the campaign page doesnt sound useful either, so the info should just be on the campaign (sub-)page. Feel free to add more info back to the campaign page. Since I dont think you can view the deleted page, I copied the latest state of the Shipwreck page to hastebin: [https://hastebin.com/semafisila]. Let me know if you think some of the images should be restored too, or just include them in the campagin page text about the shipwreck as redlinks and I'll restore the relevant ones. I hope this solution is okay for you. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 09:00, 26 January 2018 (UTC)

== Template:Inventory/pl‎‎ ==

Hi Bilka,
I apologize for the confusion with the site Inventory/pl‎‎, I read the rules, but I did not apply :(

I wanted to make the name appear in my language after hovering over the icon, so I just start translate in links on this page, from <pre><div class="factorio-icon">[[File:Transport belt.png|32px|link=Transport belt{{If language suffix}}]]</div></pre> to <pre><div class="factorio-icon">[[File:Transport belt.png|32px|link=Transport belt{{If language suffix}}|Taśmociąg]]</div></pre>

After you deleted the page, I started to wonder if it would be better to add to all links in Template:Inventory <pre>{{Translation|...}}</pre> for example: <pre><div class="factorio-icon">[[File:Transport belt.png|32px|link=Transport belt{{If language suffix}}|{{Translation|Transport belt}}]]</div></pre>

Do I think right? {{Unsigned|JakubSTR|11:15, 9 February 2018‎}}

: That indeed was a good idea, so I added it. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 12:41, 9 February 2018 (UTC)

== Intermediary Products ==

Am I allowed to make a page on intermediary products? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:06, 9 February 2018 (UTC)

: What would be on it? We already have [[:Category:Intermediate products]] which lists all of the items in the intermediate tab in the inventory, what extra information would you add to a page about them? Also please consider moving this discussion to the wiki-work channel in the [https://discord.gg/factorio factorio subreddit discord], communication is much faster there :) -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 15:16, 9 February 2018 (UTC)

I was also thinking about adding such page or modifying [[:Category:Intermediate products]], as there are now two meanings to the phrase "intermediate products": this can either be the products on the "intermediate products" tab or the items that can be created using productivity modules. I've tried to clarify this on the [[Module]] page, but perhaps a separate one would help with that too. [[User:Uukgoblin|Uukgoblin]] ([[User talk:Uukgoblin|talk]]) 13:54, 1 May 2018 (UTC)

:Intermediate products are intermediate products and that's it. The error message you get from productivity modules is simply misleading, and will hopefully be changed. However, I've been thinking about making a category for "recipes that accept productivity modules" for a while. If you have an idea for a shorter, non-misleading name that is not "intermediate produtcs", let me know and I'll set up the category. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 14:04, 1 May 2018 (UTC)
:: OK, that makes sense. Yeah, a good name for such category is not easy to come up with :-) Maybe the devs will sort it out for us when they fix the error message ;-) [[User:Uukgoblin|Uukgoblin]] ([[User talk:Uukgoblin|talk]]) 14:18, 1 May 2018 (UTC)

== Is there any ways to mark the translation obsolete? ==

Hi Bilka! I'm glad that [[special:diff/156286|you gave me a welcome message]].

I found some of translations obsolete and useless.
For example, the Japanese version of [[Electric system/ja|Electric system]] didn't mentioned [[Steam turbine]] or [[Nuclear power (research)]].
Maybe it's too much and too obvious for example, but there should be more obsolete texts it's not so clear to be obsolete.

The wiki forced editors to follow the English version, so I think it's convenient if there is a template, a category or something to state that the translation is obsolete. (It's also good if some bots automagically detect the obsolete pages and notify readers/writers of that)
--[[User:Fried biter|Fried biter]] ([[User talk:Fried biter|talk]]) 07:34, 8 March 2018 (UTC)

:If we had such a template, we would just end up with many pages being marked, which is not an improvement, it's just clutter. If you see that a page is outdated, update it. If you dont have the time/energy/whatever to update it, put it on a to-do-list in your userspace. This has the same result as marking with a template, but wont clutter a lot of pages. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 20:14, 8 March 2018 (UTC)

:: First, I don't think it's not an improvement that mark obsolete pages obsolete, since it could be simply a lie. It helps not only writers but also readers. So I don't think it's enough to put in my mind or my userspace.
:: But your concern is reasonable. Well, If we put and remove the template by hand, it should be just clutter. But I don't think leaving it to bots are quite hard. Basically, it watches [[Special:RecentChanges]]. If an English page is edited, then follow the inter-lang links and paste the template(or anything). If a non-English page which contains the template is edited, simply remove the template. If this is too much or too less, we can add some conditions like:
::* tolerant to small changes (ex: edit only 2bytes changed, which is likely to fix typo)
::* tolerant unless it's too obsolete (ex: only if the sum of changes in the original is more than a threshold / only if the translation is n-months older than original)
::* force non-English editors to tell translation edits from the other minor ones apart (ex: translate edit should contain '[Tt]ranslat' in Summary)
::* etc...
:: If your concern is that template/category/something itself is a clutter to readers, maybe it's not so much. [https://en.wikipedia.org/wiki/Category:Articles_needing_additional_references Make it hidden category as wikipedia do]. If your concern is about server performances, it's over. I have no way to deal it with :P --[[User:Fried biter|Fried biter]] ([[User talk:Fried biter|talk]]) 04:59, 9 March 2018 (UTC)

::: My concern is that it wont be useful because so many pages will be marked. Furthermore, a script that automatically marks pages will be very error-prone since it's a bot, and not a human. But I should be able to throw together a script that makes a list of most likely outdated pages. That will take a few days, then we can review the list to see if it would actually be useful to mark all of those pages, and take appropiate action. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 15:37, 9 March 2018 (UTC)

:::: I understood your concern. And I believe it can be solved by an appropriate conditioning. Anyway, I'm glad to hear that you are willing to try it to gather information to review. Thank you for your support with a bot. I hope it will work out fine. (p.s. I don't know [https://www.mediawiki.org/wiki/Help:Bots what language you are using to run bot on the wiki], but I can r/w some python or java so maybe I can help you with reviewing script)--[[User:Fried biter|Fried biter]] ([[User talk:Fried biter|talk]]) 10:32, 10 March 2018 (UTC)

::::: I wrote the script, you can find it here: [https://github.com/Bilka2/Wiki-scripts/blob/master/Find-outdated-lang-pages.js] The result of it is about what I was expecting: [[User:Bilka/Outdated pages]]. Most pages are outdated, so the list is rather useless. I excluded my own and my bot's edit from the language page dates because I only made structure maintaining edits on language pages without actually changing the content. I hope this shows why I dont think it's a good idea to mark the pages with templates. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 18:27, 29 March 2018 (UTC)

:(<- outdent) Thank you for writing a script! And as mentioned above, some filtering by certain conditions might be useful to reduce the number of "outdated" pages. [https://github.com/Bilka2/Wiki-scripts/blob/master/Find-outdated-lang-pages.js#L191 The script simply compare their timestamps], and this results in too many candidates and make the list useless. So why not try to introduce some limitations such as <code>en.timestamp > langTimestamp + PATIENCE_CONST</code>, or setting <code>rvlimit</code> parameter gives us previous revisions so that we can ignore minor edits. I don't know how it costs server resources, but if not too much, I think it still can be useful. (P.S. Can I run/test the script without special privileges? [[Special:ApiSandbox]] is not so flexible...) --[[User:Fried biter|Fried biter]] ([[User talk:Fried biter|talk]]) 06:28, 30 March 2018 (UTC)

:: Both your proposed conditions will falsify the result. Even 1 edit on a page can make any translation outdated, no matter how old it is, see for example [[Special:Diff/155934]]. So for example excluding pages that are "only" a week/month outdated will lead to wrong results. We have no rules or guides for what to mark as a minor edit since it is impossible to enforce, so sorting by that would also lead to wrong results. You should be able to test the script by just copying pasting it into the browser console and running <code>main(languages);</code> after lowering the 100 in line 112 and 113 to 50 to account for your lower api limits. The create page call on line 64 also wont work, you'll have to find another way to print the output somewhere. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 09:29, 31 March 2018 (UTC)

== Translate template to different word-order languages ==

Hi Bilka! I find it hard to translate [[:Template:about]] to Japanese.

In the [[Factorio:Translation_guide]], it says translation of templates should be done with just replace the argument of the template.
And the first sentence of [[:Template:about]] is <code><nowiki>{{Translation|This article is about}} {{{1}}}.</nowiki></code>.
But in Japanese, that sentence should be translated as <code><nowiki>この項目では、{{{1}}}について説明しています。</nowiki></code>. I mean, another translation template is needed after <code><nowiki>{{{1}}}</nowiki></code> to simply substitute. Some similar issue should be aroud here and there since Japanese has quite different word-order to English or other Europian languages, so I want to know how to translate in such cases.

(reference: [https://ja.wikipedia.org/wiki/Template:Otheruses#%E4%BB%96%E3%81%AE%E9%A0%85%E7%9B%AE%E3%81%B8%E3%81%AE%E8%AA%98%E5%B0%8E Template:Otheruses in Japanese Wikipedia], which is used as equivalent of [https://en.wikipedia.org/wiki/Template:About Template:About in the other languages].){{Unsigned|Fried biter|13:20, 10 March 2018‎}}

:Sadly there is no good way to solve this issue. Due to how translations are set up on this wiki, I can't add another translation template after the <code><nowiki>{{{1}}}</nowiki></code>, or include it in the template used for the sentence, neither of these options would yield the desired result. So, your options now are either making template:about/ja and translating the template directly, or rewording the sentence in a way that uses the English sentence structure, which would be preferable. I can understand that the second option may be very hard to do, which is why the first option would be acceptable. This issue and the options to solve it vary on a case by case basis, so please let me know of any other templates where you also have this problem before doing anything with them. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 14:03, 11 March 2018 (UTC)

:: Okay, I will postpone translating [https://wiki.factorio.com/Special:AllPages?from=&to=&namespace=10 the templates] until the consensus about how to translate them has reached by the Japanese editors community. Additionally, I will inspect them and try translations by rewording. If it's done, I will notice you. --[[User:Fried biter|Fried biter]] ([[User talk:Fried biter|talk]]) 05:30, 12 March 2018 (UTC)

== Getting rid of BurnerNav template ==

Hi, Thanks for the initial warm welcome!

I've seen that the [https://wiki.factorio.com/index.php?title=Template:BurnerNav Template:BurnerNav] didn't get the same treatment as other nav templates, so I've added missing links. However, I've now realised that the content of this template is entirely covered by other nav templates (Intermediate products, Production items, Logistics templates). What about getting rid of that template and relaying on the existing ones instead? [[User:Spyhawk|Spyhawk]] ([[User talk:Spyhawk|talk]]) 17:53, 28 March 2018 (UTC)

:I agree, so I added the valid fuel row to the infoboxes to completely replace the template, the template will be deleted soon. Please next time think about these kind of implications before editing some of the most used templates on the wiki. Thank you. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 18:37, 28 March 2018 (UTC)

:: Yes, definitely a big oversight from my side. Sorry about that! [[User:Spyhawk|Spyhawk]] ([[User talk:Spyhawk|talk]]) 18:58, 28 March 2018 (UTC)

== Roadmap ==

Hi,

The [[Roadmap]] page is deceptively empty. What about merging <nowiki>[[Roadmap/Coming_Releases]]</nowiki> with it, as it serves as the actual Roadmap page anyway? [[User:Spyhawk|Spyhawk]] ([[User talk:Spyhawk|talk]]) 13:47, 1 April 2018 (UTC)

: Hey, this had been planned for a while, thank you for reminding me. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 14:43, 1 April 2018 (UTC)

:: Thank you, this is much better now. [[User:Spyhawk|Spyhawk]] ([[User talk:Spyhawk|talk]]) 14:57, 1 April 2018 (UTC)

== Tutorial: Combinator tutorial edit ==

Hey Bilka. This was my first edit, so forgive me for overlooking the summary section of the edit page. I removed a link that serves no educational purpose and seems self-promotional to me. Exploring this youtube channel does lead to some videos that may or may not be relevant, but the link itself is too aspecific. And because of the other link (reddit), it is also redundant.

Even if it were just plain text, claiming ownership of an idea on this wiki seems inappropriate to me, although I'm not sure if there's a specific rule against it.

By the way, is this the place to post this, or should I use the discussion page of the page in question? {{Unsigned|Koekjesfabriek|20:55, 30 April 2018‎}}

:The design is mostly known under the name of the original designer ("Madzuris train loader"), so it is not directly self-promotional. I however agree that the link to the reddit thread is enough, so I removed the youtube link again, and included the name with the reddit link, so that people searching for the design can still find it.

:This is the right place; a big reason for reverting your edit was that it was your first edit, and a "controversial" one, so I expected some kind of reasoning. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 07:49, 1 May 2018 (UTC)

== New translation language - pt-pt ==

Hey Bilka, I am new to the wiki and I would like to contribute translations in pt-pt. Can you please add support for this language? Thanks. [[User:FranzPT|FranzPT]] ([[User talk:FranzPT|talk]]) 15:03, 4 July 2018 (UTC)

:Thanks for the notice, I have added support for pt-pt. Have fun translating! -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 15:06, 4 July 2018 (UTC)

::Nice, thanks for the quick response. I will carefully read about the translation rules/procedures and start asap. [[User:FranzPT|FranzPT]] ([[User talk:FranzPT|talk]]) 16:30, 4 July 2018 (UTC)

== What is the standard on what information is useful? ==

Are you always this hostile to everyone? Honestly, this explains why the wiki has so much outdated information. I'm just trying to follow some kind of consistent guideline.

A number of pages already use smallest whole-number ratios as building guidelines, especially for early and midgame structures. https://wiki.factorio.com/Solar_panel 23.8 solar panels per megawatt is somehow "useful information", and 1,000 / 42 is apparently not "easy to calculate"? What exactly is the standard?

If power grid information is that obvious, does the laser turret page really need a note about energy usage at all? Again, I'm just trying to find a consistent standard. Does every single page for a high-energy drain building need a "don't forget to build accumulators and steam storage" reminder? The roboport page only has a much less specific "make sure your power grid can handle the load" reminder (again, is it really necessary to even have that, when the building clearly consumes up to 5 MW when active?). But then it just copy-pastes numbers from the sidebar. The numbers are literally right next to duplicate information. That's "helpful" and "not easy to calculate"? You're really going to need to explain, clearly and precisely, what the standard is, instead of making rude, passive-aggressive remarks. {{Unsigned|Arrkhal|20:19, 10 July 2018}}

:Since you presented examples I will explain the rough guidelines using them:

::The information on the solar panel page is useful because you deal in predictable units in the electric system; usually you will know how much power you want your solar panels to supply. This amount of power can usually be obtained directly from the game when you are building solar panels to replace another energy source, or from online calculators when you are planning a setup. It shouldn't have its own section though, that is likely just a relict from an earlier version of the page.

:: In contrast, when dealing with enemies nothing is predictable: Neither the number of enemies, when they will attack, or their strength can be reliably predicted, meaning that you will never know how much shots your turrets will fire. So, the information does not have a use case.

::I am still unsure about how suitable the sentence on the laser turret page is, which is why I modified it when I reverted your edit. I will put further thought into whether it should be removed completely. In general, the high power demand should not be mentioned on every page. The roboport section wasn't changed since the guidelines were established, so I took the liberty to fix it.

:As you can see, there can't really be a consistent standard about something where context matters immensely. I recommend you to just edit the pages while trying to follow the general style. After a while you will get a feeling for what is suitable, and until then, your edits will be corrected. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 19:26, 10 July 2018 (UTC)

::Thanks for taking the time to explain the general guidelines more clearly, and I apologize if my first comment was itself passive-agressive, I was just a little frustrated with the lack of consistency with page information, and lack of clear communication about exactly what was amiss with my edits, instead of just generic "not helpful" and "then don't edit" notes. Anyway, if specific power grid management tips shouldn't go on most buildings, maybe it should just a basic "this building has unpredictable and high power needs which can lead to brownouts or blackouts, unless the power grid is able to compensate" with a link to the power grid guide, rather than the much more specific advice for accumulators and steam storage? [[User:Arrkhal|Arrkhal]] ([[User talk:Arrkhal|talk]]) 03:33, 15 July 2018 (UTC)

:::I don't think that a generic sentence is better than a specific one, so I will keep it how it is for now. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 09:52, 15 July 2018 (UTC)

== Code for blueprint ==

I can place the code of the <nowiki>[[:File:5to2_balancer.png]]</nowiki>? [[User:AiltonCow|AiltonCow]] ([[User talk:AiltonCow|Talk]]) ([http://steamcommunity.com/id/ailtoncow Steam]) - Okarin. 06:14, 29 July 2018 (UTC)

:Sure, the balancers should have blueprint strings. Just remember to include all 3 belt tiers in the book and to name the blueprints and book.

:And while I am talking with you, please add the ratio sections to the 3 science pack pages that your partially translated. Thank you. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 19:49, 27 July 2018 (UTC)

== disambiguation ==

Hi again, can you see the page [[Furnace/pt-br]]? the disambiguation template its not translating the page name -- [[User:AiltonCow|AiltonCow]] ([[User talk:AiltonCow|Talk]]) ([http://steamcommunity.com/id/ailtoncow Steam]) - Okarin. 10:51, 31 July 2018 (UTC)

:Fixed. If you ever want different text than the page title there, use <nowiki>{{Disambiguation|my different text}}</nowiki>. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:55, 31 July 2018 (UTC)

== The history section in translated pages ==
Hi. So... why the historical section should not be in the translated pages? I don't understand it. Because I would like to see a history of changes of a particular thing from update to update. And, by the way, in all the articles I translated, the historical section was also.
And, yeah, this is article where you wrote message about history section:
https://wiki.factorio.com/Firearm_magazine/ru
By some reason there's no my nickname... I'm Aldekotan, russian translator.{{Unsigned|Aldekotan|08:02, 1 August 2018‎}}

:For the same reason the version history is not translated: The history section is copied from the in-game changelog, which also is not translated. Furthermore, users would often only partially translate the history section, like on the page you linked. However, it is just a guideline, so if you want you can still translate the history section and include it. You sign talk page messages like this: <code><nowiki>~~~~</nowiki></code>. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 08:11, 1 August 2018 (UTC)

== Localisation stringtables ==

- Can't find 'em. Is there a page containing the translations like "Power Production"->"Stromerzeugung", which you can edit, or is it only accessible to the staff ? {{Unsigned|Factoruser|19:33, 20 August 2018‎}}

:You can find them here: [[Template:Translation/de]]. Please read the [[Factorio:translation guide|translation guide]] for help with translations. I also saw that you summarized your edits in German. While I can understand it, it would be nice if you wrote your summaries in English so that they are accessible to all wiki users. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 19:45, 20 August 2018 (UTC)

== Images ==

As you can see, I'm pretty good at making images/gifs/whatever. Wherever I make an edit, you don't seem to be far behind. So I might as well ask you directly: are there any more pages in need of images? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 01:46, 6 October 2018 (CDT)

:And yet you managed to catch me on a weekend off work :P One article that I can think of is [[deconstruction planner]] — it needs a general update to include the filter functionality which should include images of the GUI. If you are able to make gifs using an external program/website, you could also have a stab at making all the biter/spitter/worm images on [[enemies]] transparent gif using the files from the game files, like the small biter and spitter. You could also make more of the "[thing] entity" images that are included in the infoboxes, you seem to know the general rules for those already, but here they are again: Entity on grass, zoom level 2, alt mode on, images 300 or 400 px width/height if possible, no clutter/smoke/clouds/decoratives as usual.

:Something to keep in mind when uploading images: Add <nowiki>{{Screenshot}}</nowiki> to screenshots, and <nowiki>{{Game image}}</nowiki> to game images (and the enemy gif renders) in the file description to categorize them correctly and to keep the licensing clear. Furthermore, please name your images with spaces/underscores, it makes them more readable and easier to search for. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 12:14, 7 October 2018 (CDT)

::The thing about the images of enemies... Do they need to be animated? Or is that just a bonus? Also, could you elaborate on the "zoom level 2" thing? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:26, 10 October 2018 (CDT)

:::Yes, animation and transparency is a requirement. If you don't know how to do that (I don't completely know myself...), don't worry about them. With "zoom level 2" I mean that your screenshots for the entities in the infoboxes should be taken at that zoom level (of course with hr graphics). You can do that with the screenshot command (and setting it there) or by pressing F5 and using the zoom level that you can find at the top left. It's a way to ensure that all images have the same scale.-- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 15:35, 10 October 2018 (CDT)

::::Going through the files of the game and seeing how the enemies are drawn in-game, it's no secret why we don't have pixel-perfect animations of the all the enemies. They are drawn by very strange layers and the image files don't show up as we see living creatures in-game. I could *try* to come up with something, but it would take me a very long time so I wouldn't look forward to any miracles. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:27, 23 October 2018 (CDT)

== Starter map ==

I think I need to bring in some context for this one. The save I found was on the forums and I did some editing to it. I thought it was one of the greatest starter saves ever. I don't know how that made you feel when you saw it added here, but your "no. just no." comment shed some light on that. If it makes you feel any better, I'll never do such edits without your consent again. I don't want to mess up your wiki, I want to make this the best wiki anyone has ever known. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:26, 10 October 2018 (CDT)
:I'm sorry reacting in such a way, I didn't intend to make you feel bad about the edit. My reaction stems from the fact that the wiki should not show off "the best setup" to players. Tutorials are somewhat exempt from that, but even they should not include images that simply show "the best setup" or "I use this setup". This is especially about including a way for the player to gain access to the design without "thinking about it" - so blueprint strings, and map downloads. Including a save in the quick start guide encourages the player to just use something premade for them without ever learning about the options, or finding out if they even need such an optimized map. We as the wiki want to encourage exploration, not discourage it. I hope that is more clear now, sorry again for being rude. Please do continue to make your edits, their quality was rather good so far. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 15:35, 10 October 2018 (CDT)

== Wanted pages for script ==

Hi Bilka! I'm writing some quick-and-dirty translation helper script, which automates routine works such as item-name link translations (and include NO google-translation, of course). As of now, I scrape [[Factorio:Wanted_pages/ja]] to obtain Japanese wanted pages. Is it acceptable way? Or should I hit the wiki API with <code>?action=query&list=querypage&qppage=Wantedpages</code> by myself? [https://github.com/Bilka2/Wiki-scripts/blob/master/wanted_pages.py#L88-L89 Fetching top 10k results like your bot] require me 20 requests, perhaps more expensive than a <code>index.php?action=raw</code> request. --[[User:Fried biter|Fried biter]] ([[User talk:Fried biter|talk]]) 17:11, 12 December 2018 (UTC)
: Scraping is acceptable for now. What exactly does your script do? I would be okay with giving you a bot account to make the queries, but for that I need to know what exactly you are doing (and I'd prefer if the script was open source :)). If it is possible for you, please message me on discord (I'm Bilka#2444) so that we can work out the details. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 17:19, 12 December 2018 (UTC)

== Multiplayer and fluids ==

I don't see why the images on the multiplayer page were removed. I mean, the image showed what multiplayer looked like on a page ''about'' multiplayer. The images gave the page some flavor, rather than just text. Also, is it allowed to have pictures of fluids in pipes/storage tanks for the actual fluid pages (water/heavy oil/etc.)? Better I ask than risk getting any more warnings or whatever. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:12, 19 December 2018 (UTC)
: The only difference in multiplayer is that there may be multiple players. There a plenty of images on the wiki that show more than 1 player, so I don't see the need to add one to the multiplayer page. You are however right in that it gives the page some flavor. You can add another image, but please avoid excess clutter and sharing real players names (privacy concerns) — perhaps simply host your own local multiplayer game and join yourself with some generic user names. The console is not a multiplayer feature and as such a screenshot of it is not related to multiplayer.
:: I think an image of the fluid in a storage tank would work for the infobox images of the fluid pages. So, if you want to make those, please go ahead.
::: Thank you for the amazing enemy gifs, I am glad that we could finally replace the old images with something nice and proper. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 21:04, 19 December 2018 (UTC)
:::: If Wube or any higher-up gives you some sort of praise for the wiki, which I know happened at least once because I saw your name in one of Factorio's Steam updates, please mention my name. I want to say that it took me 2-4 hours per image, and might have been the most work I've ever done in my life in terms of making a gif - as I've had to work with nothing but vague overlays, tedious photoshop work and a bit of pure luck all at once. Anyway, how do I make a bunch of "dummy" players joining a local server? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 23:14, 19 December 2018 (UTC)
::::: You can run multiple instances on your PC, for example using the zip download. Host a LAN game and disable user verification, then join yourself (since you don't need to log in, just set the name in the "other" settings). If that sounds a bit complicated/your PC can't handle a high sprite res instance besides other factorio instances, I can make an image tomorrow no problem. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 23:19, 19 December 2018 (UTC)
:::::: If I were to make custom cursors for this wiki, would you add them? [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 13:21, 20 December 2018 (UTC)
::::::: No. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 14:35, 20 December 2018 (UTC)
:::::::: You're... You're being serious? Even if the cursors are subtle? I heard this rumor that... that uh... if your wiki doesn't have custom cursors, then uh... you're not a cool kid. You wanna be a cool kid right? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:36, 20 December 2018 (UTC)
::::::::: I asked Albert for his opinion and he gave the same answer as me :P -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 14:51, 20 December 2018 (UTC)
:::::::::: I never seen a small idea get rejected so fast. I don't know who Albert is, but I'm spreading around that you and this Albert guy aren't cool kids. Seriously? Not even so much as a cursor with just a different color? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:01, 20 December 2018 (UTC)
::::::::::: Albert is the art director :) He does not like custom cursors. Btw, you can add the cursor for yourself by putting it into your [[User:Zippy/common.css|user css]] -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 17:06, 20 December 2018 (UTC)
:::::::::::: An art director that doesn't like custom cursors? Sorry but I gotta call the cops on both of you. rip. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:59, 20 December 2018 (UTC)
::::::::::::: Hey, sorry for not being clear about this. You can use the css code, but please don't host the images on the wiki. You can upload them anywhere (like imgur) and simply link to them in your user css. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 22:41, 20 December 2018 (UTC)
:::::::::::::: I should've known, sorry. I linked all my cursors to imgur urls. Still calling the cops though. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 09:39, 21 December 2018 (UTC)
::::::::::::::: One more thing, if you want me to make ''you'' anything custom. Ask me anything. On the house. Because I'm the nicest guy ever. [https://ioneblackamericaweb.files.wordpress.com/2018/08/arabella-juniper-torres.jpg?quality=99&strip=all&w=700&h=400 Still on the phone with the law though. Bet you're scared right now.] -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 12:19, 21 December 2018 (UTC)
:::::::::::::::: Another 'one more thing', am I allowed to make a "sandbox" page for myself to test things? Like a 'zippy/sandbox' page? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:56, 28 December 2018 (UTC)

Of course, you can do whatever you want in your userspace as long as it's within the rules. The rule explicitly mentions sandbox pages, so those are okay :P -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:55, 30 December 2018 (UTC)
:Don't worry it's totally not Zippy spamming your talk page. Are there any more high quality images needed anywhere that I missed? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 01:52, 7 January 2019 (UTC)
::Not that I know of. With 0.17 a lot more sprites will be high resolution, so that will bring back the demand. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 09:46, 7 January 2019 (UTC)
:::Is it alright if I leave tiny-text notices about the animated APNG's in that they don't animate for every browser? Or should I just leave it? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 20:03, 21 January 2019 (UTC)
::::I don't think you need to leave a note. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 20:20, 21 January 2019 (UTC)
:::::Why did you remove the images for the construction and logistics robots' infoboxes? And not to sound like I'm arguing, but what was the issue with me changing the text color by 10% on the fuel page? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:31, 24 January 2019 (UTC)
::::::The images were removed because they were not used for multiple weeks. If you upload something, please use it. I removed the text color because it is not needed to help make the page more clear. Our style guide states that text color and styles should not be overused. Some of your additions of colors on page were on the boundary of that, but as long as it was directly related to the content of the text (like the rail signal colors), I kept it. Making "unusable" colored fails that point of reasoning, so I removed it. Don't worry about questioning what I do, it makes sure I keep my decisions well reasoned. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 19:46, 24 January 2019 (UTC)
:::::::Should there be a page for the game's "planning/ghost mode" (shift+click when placing) mode? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:51, 25 January 2019 (UTC)
:::::::: Yes. There is a redlink on [[blueprint]] to "entity ghost". You could make that page and put it on there. Some other info that would be useful on that page is how long ghosts last (infinite from blueprints, some other time from destroyed entities). -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 20:02, 25 January 2019 (UTC)
:::::::::Well the page exists now. I forgot to ask this before. Am I allowed to add images for every single type of damage on the [[Damage]] page? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 23:50, 26 January 2019 (UTC)
:::::::::: The page is great, thank you. What would images of damage types show? (Feel free to upload an example image to explain. I simply don't know how you'd do that) -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:05, 27 January 2019 (UTC)
:::::::::::Anymore pages that need to be made? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 22:47, 27 January 2019 (UTC)
:::::::::::: Nothing that would be worth it before 0.17. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 19:21, 28 January 2019 (UTC)
:::::::::::::Will you have the time to add any of that stuff? It seems like there's a plethora of new things coming. Enough to make our faces explode 4 times over. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 15:58, 31 January 2019 (UTC)
:::::::::::::: I hope I do, it is my job after all :) I am already preparing for 0.17, so I hope to have most pages prepared before 0.17 comes out. Once it is out, it will be a community effort to finish updating the entire wiki, but it should definitely be doable. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:02, 31 January 2019 (UTC)
:::::::::::::::Can I make a "bus" page? Since there's one on balancers? As well as a page titled "Warnings" that redirect to "Alerts"? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 06:09, 9 February 2019 (UTC)
:::::::::::::::: We already have [[Tutorial:Main bus]], so no. Yes. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 17:50, 9 February 2019 (UTC)
::::::::::::::::: Probably a good time to bring this up *before* 0.17 comes. I recommend taking screenshots with something like Fraps, because using the screenshot feature from Steam just compresses the hell out of the images like a low quality .jpg. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 23:47, 11 February 2019 (UTC)
:::::::::::::::::: I use either ShareX or the screenshot feature built into the game which both produce high quality images. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 07:56, 12 February 2019 (UTC)
You know how some of the images I made have the checkered background? Is it valid to make the pictures of buildings entities also have that? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 16:26, 12 February 2019 (UTC)
: No, I dont want to stray so far from the vanilla game. The images are there so that players can know how something looks like in-game before they see it. If that is shown in a completely different context than the player will ever encounter, it will make it harder for the player to recognize the building. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:31, 12 February 2019 (UTC)
:: Do you happen to know what the "dot" and "info" signals are in 0.17? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:29, 2 March 2019 (UTC)
::: They were added because the Introduction uses them in the guis. As far as I know it's on the to do to remove them again since they never really were meant to be in the base game as signals. Other than that they are just virtual signals, nothing special. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 17:31, 2 March 2019 (UTC)
:::: Can I add the 'stop conditions' to the locomotives page? (cargo empty, cargo full, etc.)? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 01:49, 9 March 2019 (UTC)
::::: Also, to save myself a lot of work if need be, do ALL images need to be redone for 0.17? Even if the older image gets the point across to what something is? Like say, some belt images on the transport belt system page. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 02:09, 10 March 2019 (UTC)
:::::: The conditions fit better on [[Railway#Train_schedule]], you could link to that if it's not easy to find on the locomotive page. No, they don't need to be all redone. I think once 1.0 is out we will make such a "full pass" and make sure that every image is up to date, now it would be too much work for something that might change again. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 19:07, 10 March 2019 (UTC)
::::::: Are there any pages that still need redoing, or any more (animated) images I've missed? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:49, 19 March 2019 (UTC)
:::::::: Only the really big pages (inserters, map editor, world generator) and small pages that I don't have on my list are left. I kind of want to do those big pages mostly myself, I hope that is okay. I've not been keeping track of the images, sorry. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:19, 19 March 2019 (UTC)
::::::::: Permission to make a template for glowing and/or outline text? You never know when you might need something like that. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:40, 21 March 2019 (UTC)
:::::::::: No. Please see the rules on templates for why not. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 23:32, 21 March 2019 (UTC)
::::::::::: I see, what if there just so happened to be a glowing text thing in the game itself, and we were making it match in the wiki? Regardless of what you're answer is, have a sensational day! Are there any unrelated template pages that need making anyway? Also, can add a super subtle glow effect to the words "everything", "anything" and "each" on the circuit network page? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 10:53, 22 March 2019 (UTC)
:::::::::::: When that happens we will make the appropriate changes, no need to make them now. No not currently, and no. Don't overdo it. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 17:51, 22 March 2019 (UTC)
::::::::::::: One of your edit notes was "Factorio gui style: Round corncers = can be interacted with. This cannot be interacted with." I'm sorry but I haven't the slightest clue in the world what you're saying here. Also am I allowed to make those colorboxes rounded for *just* the lamp page? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 04:58, 23 March 2019 (UTC)
:::::::::::::: Basically, one of the "standards" in the GUI style introduced in 0.17 is that when an element has rounded corners, it can be modified by the user. You can see this all over the vanilla game — textfields have rounded corners, buttons do not etc. In the long run, the plan is to make the wiki use the in-game GUI style. So anything new that is created should already follow that style, to make transitioning to it easier. So no, you are not allowed to make them round for the lamp page. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 11:13, 23 March 2019 (UTC)
::::::::::::::: Is there a way I can edit my .css page so they appear rounder just for me? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:23, 23 March 2019 (UTC)
:::::::::::::::: I added the class "template-color" to the template, so you can use that for your user css. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 19:45, 23 March 2019 (UTC)
: Can I add a template for a "map icon"? Like for the little arrow icons you see for tanks/locomotives/cars in the mini-map? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 22:45, 23 March 2019 (UTC)
:: I don't get what this template would do. Could you create it in your userspace so that I can have a look, please. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 12:07, 24 March 2019 (UTC)
::: Am I allowed to make prototype template(s) to help demonstrate my point? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 12:49, 25 March 2019 (UTC)
:::: Yes, create the template in your userspace, like I said. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 18:18, 25 March 2019 (UTC)
::::: I was gonna redo all the inserter images to make them more 0.17 related. Though the alt-mode in 0.17's inserters looks real cluttery. It might look better with alt-mode off. Is uh... will that work? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 22:01, 5 April 2019 (UTC)
:::::: Oh, be sure to check out my workbench page. [https://wiki.factorio.com/Infobox:Zippy/workbench Look at the fake car infobox]. See the little arrow icon? Pretend that "Storage Size" says "Map Icon". That's what I propose what this wiki should have. I can't edit the main templates so... yeah that's all you. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 00:20, 6 April 2019 (UTC)
::::::: The alt-mode did not change with 0.17, so it is not okay to turn it off for images that had it on. The car icon looks okay, but it doesn't use any template. If you just want the property for it added to the infoboxes, I can do that no problem. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 18:20, 6 April 2019 (UTC)
:::::::: Could I just upload updated inserter images but photoshop the yellow arrow and bar on them? And yes, I'd very much like for you to add that property if that's alright. Though it's for the good of the wiki more than it is for me. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 23:52, 6 April 2019 (UTC)
::::::::: I already updated the images. I will add the property tomorrow morning. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 23:57, 6 April 2019 (UTC)
:::::::::: Actually, I meant the individual inserter pages: yellow inserter, fast inserter, filter, etc. The images in the infoboxes. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 01:18, 7 April 2019 (UTC)
::::::::::: Okay, for those you definitely have to use "alt-mode" and please do not photoshop them beyond cropping. Thank you. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 12:35, 7 April 2019 (UTC)
:::::::::::: Am I allowed to add a mini-section on the circuit network on the transport belt system page about how they connect to the circuit network? And did you add the 'map icon' thing to the template page? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 23:01, 7 April 2019 (UTC)
::::::::::::: Yes. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 08:18, 8 April 2019 (UTC)
: Say what's that trick again where you can add another "fake" player to the game? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 04:00, 13 April 2019 (UTC)
:: The one I explained to you was making a LAN multiplayer game and joining yourself locally. You can however also use /c game.player.surface.create_entity{name="player", force="player", position={0,0}}, but that player wont have a name and it cant move. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 07:59, 13 April 2019 (UTC)

== Strange link in Power_production#Ensuring_enough_energy_is_produced ==

Hi Bilka,
the section "[[Power_production#Ensuring_enough_energy_is_produced]]" contains a link that leads to: https://en.wikipedia.org/wiki/Feedback
It has only marginally to do with "brownouts/blackouts"!?
I assume https://en.wikipedia.org/wiki/Brownout_(electricity) or https://en.wikipedia.org/wiki/Power_outage was meant. {{unsigned|VandenPlas|15:44, 9 January 2019}}
:That is the result of an discussion over whether the feedback loop is positive or negative. You can find the discussion here [[User_talk:AnthonyQBachler]] and on power production talk page. Feel free to link to brownout instead, the link to "feedback" never really made sense. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:22, 9 January 2019 (UTC)

== Headline change to different language ==

Hi Bilka,
how do I change the headline of a page to a different language (german in this case)?
Please see: wiki.factorio.com/Refined_hazard_concrete/de, wiki.factorio.com/Refined_concrete/de {{Unsigned|VandenPlas|08:21, 22 February 2019}}
: Add the title (Refined hazard concrete, Refined concrete) to [[Template:Translation/de]]. You can find more tips for translation here: [[Factorio:Translation_guide]] -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 08:38, 22 February 2019 (UTC)

== Revising my edits ==

Hey, just wanted to say thanks for revising and especially commenting on my last set of edits. It's good to know how to keep to wiki style and make things consistent. [[User:Techhead7890|Techhead7890]] ([[User talk:Techhead7890|talk]]) 14:49, 5 April 2019 (UTC)

== Understanding logistic chests ==

Yeah, constantly expanding that "multiplayer and fluids" section was getting old. Logistic chests, for me, was not something I could understand so easily from the start. If I made an image, giving accurate visuals to what each chest does, would it be allowed on this wiki? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:53, 14 April 2019 (UTC)
:Depends on the image, but generally yes. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 09:01, 14 April 2019 (UTC)
:: How do you feel about this idea: imagine having more signal labels, but some of them are symbolic and interactive. Look at this image: https://i.imgur.com/EB0HJoq.png - Now imagine you pick the first bullseye-looking signal, and that signal is activated. So you get an effect like 'this' on the minimap (https://i.imgur.com/OQjJBJr.gif). You think something like that would be a good add to the game? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 04:53, 17 April 2019 (UTC)
::: Uhh, yes? No? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 06:24, 20 April 2019 (UTC)
:::: Vacation :) Ideas and suggestions for the game have no place on this wiki; make a forum post for that. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 19:19, 22 April 2019 (UTC)
::::: Is a multiplayer image of players fighting off enemies allowed if there's no mod elements? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 15:56, 29 April 2019 (UTC)
:::::: What value do you think the image would add to the page? -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:30, 29 April 2019 (UTC)
::::::: An interesting image that's different from one player just standing around a bunch of enemies. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 04:26, 30 April 2019 (UTC)
:::::::: Okay, add it. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:36, 30 April 2019 (UTC)
::::::::: Wait... You mean add the image from before or the alternate "non-mod" one I brought up? Also, am I allowed to add gif's for all the weapons? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 13:40, 30 April 2019 (UTC)
:::::::::: The non-mod one. Yes. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 13:52, 30 April 2019 (UTC)
::::::::::: I mean, couldn't I just crop out the mod stuff and post the same image..? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 06:34, 1 May 2019 (UTC)
:::::::::::: Please make a new image, the coin/random beams are in the middle of the image/directly where the fighting happens, so cropping it is nearly impossible. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 08:50, 1 May 2019 (UTC)
::::::::::::: Is there a way to find out which articles are visited the most? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 15:47, 16 June 2019 (UTC)
:::::::::::::: Yes, [[Factorio:Top pages]]. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 21:09, 17 June 2019 (UTC)
:::: I was wondering, you know how you can change the style of this wiki through the user page preferences thing? What if I designed a bunch of different colored CSS templates for people to pick from? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 07:27, 21 September 2019 (UTC)
::::: The wiki is pending a major-ish style rework in corporation with the Factorio graphics department soon™ (not this year probably), so I don't think putting work into changing the current style is a good idea. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 11:14, 23 September 2019 (UTC)
:::::: Am I allowed to make a template (similar to the "stub" one) that says something like "this page has outdated images"? Or does that already exist? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 06:29, 17 August 2020 (UTC)
::::::: Wait nvm that already exists. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 07:16, 17 August 2020 (UTC)

== Wanted pages/de ==

Hey Bilka, from time to time I translate a page in German and I noticed that some of the pages listet at [[Factorio:Wanted_pages/de]] have only one page referring to them which should not be referring to them in my opinion. An example is [[Special:WhatLinksHere/Mods/de]]. The referring page is the uk translation and I couldn't find the link on that page.--[[User:Ickputzdirwech|Ickputzdirwech]] ([[User talk:Ickputzdirwech|talk]]) 09:57, 26 July 2019 (UTC)
: The language template on the uk page refers to the German page, even if you can't see it. Just ignore any page that doesn't have an English version, that is what the column is for. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:05, 26 July 2019 (UTC)

== Two things... ==

It's me again making your talk page doubly longer than it should be. Just throwing this out there, is there a way to add .webp image support to this wiki? I don't know if you understand how that format works, but it would allow .gifs to be resized and still animate. Also, this one is minor, but are you alright with having a GUI image for buffer chests? The deletion log says you got rid of it for being too similar to another image or something, though the only difference is one chest has as extra option on the GUI. Don't know if that counts. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 01:43, 24 September 2020 (UTC)
: Mediawiki recommends against using webp's for images since not all browsers support their display. Furthermore, adding support for displaying them properly looks pretty complicated, so I don't think it's likely to be added. The buffer chest image is alright to add - the deletion in the log was me accidentally uploading the requester chest image as a buffer chest image and then moving it to the right place, nothing to do with the actual buffer chest GUI. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 06:30, 24 September 2020 (UTC)

== Localisation misinformation? ==

Hi. You reverted my edits on mod Localisation, citing "misinformation". Could you elaborate? I use rich text formatting in my mods, as do other people, so that definitely works, and it was the Factorio developers themselves that have clearly stated that the final string cannot be accessed in scripts. Where's the misinformation?
{{Unsigned|Modo lv|16:24, 22 January 2021‎}}
:Whether rich text can be used depends on where the locale is used. E.g. rich text does not work in script render text. The final string can be accessed via LuaPlayer.request_translation. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:29, 22 January 2021 (UTC)
::OK, but shouldn't the info be updated to reflect that then, instead of removing all mention of these features? I originally came to localisation page to figure out how to color text and add images, and it does not give any information on that at all (instead the given examples lead me to believe that the only way was to use parameters to insert images programmatically, and colors/fonts were simply not an option). As for reading the result, Google (specifically on the API docs!) and forum search on the issue only led me to the (outdated) forum post stating that it can't be done. {{Unsigned|Modo lv|16:39, 22 January 2021‎}}
:::If you can find a way to mention rich text without it ending up as misinformation, feel free. Regarding reading the result, I'd personally prefer if the page stays the way it is, as request_translation is basically a newbie trap. At the point that you'll be able to determine what it's useful for, you'll have found it in the docs/in another mod anyway. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:50, 22 January 2021 (UTC)
::::Well, I didn't find it. :) I have no idea how to tell if a mod might be using request_translation (since it's such an advanced and specific feature, I would guess that not a lot of them do, at least in singleplayer) and all my attempts at googling "lua read localisedstring" and similar only lead to the forum post saying it can't be done (and so I naturally stopped looking for it). So there is already misinformation out there that people do find and we can't remove, but we can ensure that the wiki — the first place a person looks — is accurate, thorough and and up-to-date. {{Unsigned|Modo lv|17:00, 22 January 2021‎}}
::::Okay, good point. How about you implement your vision (with the new info) on the page and we'll work with that. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 17:06, 22 January 2021 (UTC)
:::::Already on it! :) Ideally I would love to see a list somewhere of what supports rich text and what doesn't, but starting a whole new page seemed a bit much so soon. :D So I'll just add what I know to localisation page for now and we can go from there. Thank you for your time & patience!

== Heatpipe in german ==

Hello,
I have a problem. In German factorio heat-pipes are called "Wärmerohre" but here the wiki calls ist "Hitzerohre". How can I change the name?
Thanks {{Unsigned|Jojo04|14:46, 24 February 2021‎}}
:Hey, you can change it in [[Template:Translation/de]]. Just click edit, search for the heat pipe and change the entry. You can find more information on translating here: [[Factorio:Translation guide]]. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:53, 24 February 2021 (UTC)

== Iron gear ==

Hey, just wanted to thank you for the detailed explanation on the [https://wiki.factorio.com/index.php?title=Iron_gear_wheel&type=revision&diff=184666 iron gear diff], it was very helpful. I'd still like to expand on "many basic and advanced recipes" a little bit, as the page seems a bit like a stub at present. (For example, I should note that the first sentence is actually describing the ingredient information, which is present in the infobox.) Would you be opposed to the following (without the miscellaneous categories originally present):

<blockquote>It is very important for many basic and advanced recipes, including all levels of [[Belt transport system|belts]], the basic [[inserter]] and [[Assembling machine 1|assembler]], and raw resource extraction equipment such as the [[electric mining drill]].</blockquote>

I feel like this gives a bit more detail on basic, highly-produced items using the gear wheel, with recipes have been left unchanged in quite some time. Additionally, the prose allows grouping and categorisation of the items (rather than having to understand exactly which item icon is in the infobox's list, and then know the item's significance). Thanks in advance (and PS, thanks for tidying up the [[Assembling machine 1]] page for conciseness!). [[User:Techhead7890|Techhead7890]] ([[User talk:Techhead7890|talk]]) 11:10, 14 March 2021 (UTC)

:I'll be transparent here, the iron gear change was sitting in my to-do for a few days because I could not figure out how to handle it. Looking at it again now, I agree that the page should be longer and your proposed sentence fits well, so I added it. I think the description on [[electronic circuit]] pretty much nails what I think fits well for these item pages - some concrete examples and category mentions, but not so much/so detailed that it begins to look like an exhaustive list. But I want to stress again that I am not very set in my opinion here, so please keep proposing things/changing pages around and we'll keep communicating so we hopefully find the best solution :) Additionally, I want to say thank you for the history section additions, they are great. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 11:59, 15 March 2021 (UTC)

== German Mainpage ==

The German main page contains several outdated info. For example, the German version of the "get the game" part contains the info that Factorio is currently under development and is available as early access. Other parts of the main page are outdated as well. Is it allowed to update these important subpages to the current state of the English ones on my own? Is there some kind of review process?

Another question: A few German pages contain elaborate details that are not present in the English version. They look as if they are WIP relics from the game development stage, when the corresponding features were not yet stable or not yet fully understood by the wiki community. As far as I see it, all translated wiki pages should contain exactly the same information, regardless the language. So the task is to remove these details and replace them with exactly the information that is in the English version of that page. Not less, and not more. Is this the intended approach?
[[User:Tertius3|Tertius3]] ([[User talk:Tertius3|talk]]) 16:53, 28 March 2021 (UTC)
:You can update the main page subpages on your own. Yes, updating translated pages to the state of the English page is the intended approach. However, if you find that the extra information that is on the German page is valuable, you could add it to the English page. There is nothing that speaks against expanding pages with valuable information. Thank you for reaching out and making sure that you're working on the right things :) -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:15, 29 March 2021 (UTC)
::Another question: how should the player (reader) be addressed in German? In English you address everyone as "you", but in German you address someone formally as "Sie", informally as "Du", and some kind of middle ground is "Ihr". Usually, German game wikis, especially fan-based ones, address players as "Du" and sometimes as "Ihr", but never as "Sie". "Sie" is used with professional texts, but usually not with leisure/gaming topics. Given that Factorio started as indie game and still looks like one, I recommend addressing the player with "Du". This is how friends are talking to each other. Is this ok? I found a mix of "Sie" (in some tutorial, sounds a bit strange) and "Du" (in the old installation instructions and probably elsewhere), so I'm asking for consistency. [[User:Tertius3|Tertius3]] ([[User talk:Tertius3|talk]]) 16:42, 29 March 2021 (UTC)
:::For that and most other things we follow the in-game translations, which go with "Du". Im Internet duzt man sich ;) -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:53, 29 March 2021 (UTC)

:::So I think the Best way to this in german is with "Man", because it is some kind of bad language, to adress the reader directly. (In german) ~ [[User:Jojo04|Jojo04]] 08:50, 5 April 2021
::::I personally consider "man" as bad language. I prefer "Du". It's a good way to 'involve' the reader and keep him/her reading. --[[User:Ickputzdirwech|Ickputzdirwech]] ([[User talk:Ickputzdirwech|talk]]) 09:13, 5 April 2021 (UTC)

:::: As in most cases the english "you" refers to everyone, the correct German word is "Man". The translation with "Du" is an anglizism and so an bad language. Also the Wiki style guide says, that (in english) "you" should be avoided. [[User:Jojo04|Jojo04]] ([[User talk:Jojo04|talk]]) 09:50, 5 April 2021 (UTC)
::::: I usually go with "man" on my translated pages, and it looks better than the direct "du" in my opinion. In english, some sentence is "To achieve this, you click on this and do that", the corresponding translated phrase as I see it is "Um dies zu erreichen, klickt man auf dies und tut das". In many articles on this wiki, "you" is used like this, and translation to "man" feels quite natural. It's simply factual, not too personal. Really bad would be, if you translate to "Um dies zu erreichen, klicken Sie auf dies und tun das". I use Deepl for initial translation work, and it often starts to address the reader as "Sie" - this is what I rework to "man". I would use "Du" in elaborate tutorials, which at the most part are not yet translated. The only one is the Quickstart tutorial, but unfortunately this addresses the player as "Sie". [[User:Tertius3|Tertius3]] ([[User talk:Tertius3|talk]]) 11:17, 5 April 2021 (UTC)
:::::: Generally, the aim should be to keep articles that aren't tutorials in passive voice, so for example "this can be achieved, by clicking on this and doing that" or using phrases like "the player inventory" instead of "your inventory". This goes for both English and German. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:36, 8 April 2021 (UTC)

== This Wiki's Origins... ==
Me and the creator of the game "Song of Syx" are discussing starting a wiki. He actually said he was curious to how THIS very wiki got started. Did you buy a site and make this all from scratch? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 23:39, 6 May 2021 (UTC)
:Back in the day, the wiki was hosted on the same server as the forums, it didn't even have its own subdomain. [https://www.mediawiki.org/wiki/MediaWiki MediaWiki] is free and open software, so there is nothing to pay for there. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 09:39, 7 May 2021 (UTC)
::Does MediaWiki provide you with its own server space or do you need a server of your own. The dev of Song of Syx seems to think you need one. Also, I noticed that you updated some of the images in the 'combinator tutorial' page, but you left some not updated. Is that because you want to save space to not stretch the page? Because the new GUI for the combinators are way fatter and space-taking. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 01:52, 9 May 2021 (UTC)
:::MediaWiki is just software, no server and no service included. So you need to provide your own server. The Factorio wiki probably started as additional install on the official forum server and was later carved out to its own server because of the growth. Despite its power, MediaWiki is very easy to install.
:::Apropos combinator tutorial - could you take a look at this image made by yourself: {{fullurl:File:Onetime_Clock.png}}? It's not only a bit outdated, it's wrong unfortunately. The bottom decider has to be "input count". The previous image in the history has the correct setting. [[User:Tertius3|Tertius3]] ([[User talk:Tertius3|talk]]) 14:11, 9 May 2021 (UTC)
:::As Tertuis3 says, you need to have a server to host the wiki software. I updated the images on the combinator tutorial page that had mistakes and left the rest the same for the reason you give. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 09:30, 10 May 2021 (UTC)
::::I think I asked you this, but is there a tutorial on how to make templates from scratch? You had to have learned somehow as there's hundreds of templates made by you. Also, what's the name of the file you edit to change the main CSS of the entire wiki? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 12:56, 11 May 2021 (UTC)
:::::The MediaWiki help pages are linked in the sidebar of this wiki. They are rather good at answering questions like this. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 13:49, 12 May 2021 (UTC)
::::::I'll try to make this my last question. And yes, I went through the MediaWiki help pages. You know how it says "Factorio Wiki" in the browser? Can that be changed with ease? Mind you, I'm an admin of the wiki I'm working on, but not the actual owner. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 18:37, 18 May 2021 (UTC)
:::::::[https://www.mediawiki.org/wiki/Change_the_name_of_the_wiki This page] has some info on how to change the wiki name. You will need to be able to access LocalSettings.php for that, some info on that is here: https://www.mediawiki.org/wiki/LocalSettings.php#Location_on_the_server. Good luck with your endeavors! -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 18:51, 18 May 2021 (UTC)
:::::::: Might as well throw this in. When a transparent image is resized in a thumb image, it has a white background which looks kind of... "loud" and off on this site's color scheme. You can change that by editing the background-color of "html .thumbimage". I'm sure you knew that for the longest time. Just throwing that out there just for the sake of it.

<pre>html .thumbimage {
background-color: #222;
border: 1px solid #797979;
}</pre>

^ I think something LIKE that could maybe work.-- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:44, 30 May 2021 (UTC)
::::::::: I did not know that, thanks for the info! -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 12:15, 1 June 2021 (UTC)

== Spam ==
May I ask what you use to keep the spambots out? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 04:19, 6 October 2021 (UTC)
: We have editing disabled for people without accounts. And then for getting an account, we use [https://www.mediawiki.org/wiki/Extension:ConfirmAccount Extension:ConfirmAccount], it provides [[Special:RequestAccount]]. It's working well so far, but certainly not without weaknesses. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:04, 6 October 2021 (UTC)
:: Do spambot accounts still slip in? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:01, 15 October 2021 (UTC)
::: Also, [https://songsofsyx.com/wiki/index.php?title=Main_Page this] is the wiki, if you're interested in knowing what it looks like. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 18:10, 15 October 2021 (UTC)
:::: I'd prefer not to further comment on how we combat spam. If you know the techniques, they are much easier to work around. I hope you can understand this. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:38, 29 October 2021 (UTC)
::::: I wouldn't want you spilling the beans on your techniques, either. But I have to ask this, even with your spam-fighting methods, do you still get spam accounts that slip in every now and then? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 15:38, 23 November 2021 (UTC)
:::::: Not in a way that they are of any concern to me/affect the wiki. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:29, 29 November 2021 (UTC)

== Mass search and replace ==

Do you have a bot that is able to mass replace every
"<nowiki>[[Damage/de|Schaden & Resistenzen]]</nowiki>"
and
"<nowiki>[[Damage|Schaden & Resistenzen]]</nowiki>"
and
"<nowiki>{{TransLink|Damage|Schaden & Resistenzen}}</nowiki>"
to
"<nowiki>[[Damage/de|Schaden & Widerstand]]</nowiki>"
within the German pages?
And could you please run it?

I just reworked the German article about damage and found that German ingame terminology for resistance is not "Resistenz" but actually "Widerstand". However, Resistenz is used in all of the footers of the ammo and weapon articles.

Or if you are lazy, you can give me a hint how to make such a bot myself (I'm able to script programming with the major script languages on Linux. It would be the perfect exercise to <s>destroy the whole wiki</s> improve my Python knowledge). [[User:Tertius3|Tertius3]] ([[User talk:Tertius3|talk]]) 16:56, 12 October 2021 (UTC)
:I don't have one right away, but making it wouldn't be an issue. This is a great example to highlight why [[Template:L]] is so good when not manually overridden - it would adjust all those links automatically, though generally outdated translations aren't the biggest issue. This may be a good time to think about whether the page should maybe be moved, should be split into separate pages, whether the links to it should be in the see also at all, whether they should link to a redirect (which auto-translates) instead. What do you think here? These changes would affect English and all other language, but may have better long term results. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:58, 13 October 2021 (UTC)
::Do you mean the "damage" article that is linked by these links? It deals with damage and damage mitigation (resistance). We can split it to a damage-only article and a new resistance-only article and change all links from <nowiki>[[Damage|Damage & Resistances]]</nowiki> (which are many as well) to either just <nowiki>[[Damage]]</nowiki> or into two links to the two articles. I'm at a loss here, I'm not a person that intends to question and change all design choices made long before I joined. I just want to translate what currently exists. If you ask me, I would not change/split the damage article but change all references to it to just <nowiki>[[Damage]]</nowiki> and leave out the extension "& resistances". A redirect from "Resistance" to Damage#resistance would be useful for search. And keep all the "see also" references. May be only me, but I'm using these links very often to get a broader picture of some topic, especially if I don't know that much yet. With redirects, there is the next question I wanted to ask: the search function is useful only for English. It would be useful to create redirects in all the languages to all the "English topic/<language>" pages, for example Schaden -> Damage/de. This can probably be automated if you use all the custom language templates as source and a little bit of text processing and scripting magic. However, I don't know if this clutters the pages too much. What a pity this wiki doesn't use the native translation module available for MediaWiki. --[[User:Tertius3|Tertius3]] ([[User talk:Tertius3|talk]]) 16:26, 14 October 2021 (UTC)
:::Thank you for still providing your opinion despite not wanting to question old design choices. The damage page is a design I wanted to question because to my knowledge, the current form of the page is just an expanded version of what was created back in 2013, during the "birth" of the wiki. Both the wiki and the game have changed a lot since then, so it can be good to take another look. I like your suggestion of keeping the page as is, but changing the links to remove the resistance part. The redirect you suggest already exists (in English at least), so that is good too. So, I took the freedom of taking 10 minutes out of my day to do the change manually, both for English and German pages. Doing it manually allowed me to directly link to the resistances redirect for the armor and tank pages, since it is a bit more fitting. I created the appropriate redirect for German (the translation already existed). I hope you don't mind that I just ran with your suggestion :)
:::Regarding general language redirects - they are allowed, but I'd rather not create them in bulk, as the <code>Redirects created with the idea of "This might be useful someday" are noise and provide nothing.</code> note from the rules still applies here. This also gets difficult due to changing translations and overlapping languages. E.g. there is both an Eisenstange and Eisenstab redirect for the German iron stick. An example for overlapping would be logistic system (the research) in German and Danish - it's the same translation, so which language do you redirect to. So, I would instead suggest to try to create the redirects mostly as search enhancers. For example, searching for "Zug" doesn't result in railway/de. So that would be good to have as a redirect. On the other hand, searching for "Öl" yields crude oil/de, so that doesn't really need a redirect. I hope that still helps to make the search more usable in German.
:::Regarding the translation module, could you link what exactly you mean? Last I looked at things, there was an extension that allowed translations, but it wasn't really fitting for the wiki ([https://forums.factorio.com/viewtopic.php?f=50&t=85616]), but maybe you mean something else/the extension has been improved. I'm quite open to changing the translation system (as long as the new solution is better) because our current system is rather obviously running on technology from 2014. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 17:29, 29 October 2021 (UTC)

== Creating infoboxes on SpaceExploration wiki ==

Hello Bilka, there is an official wiki for the Space Exploration mod. However, there isn't much content. I wanted to try contributing, but I think the most important starting place is to get working infoboxes. I figured stealing infobox source code from this wiki would be the best way, since the types of infoboxes needed are the same. I (and a couple other people based on the history) have tried copying over and failed.

I'm wondering if you have any guidance on how to get infoboxes setup on that wiki.

https://spaceexploration.miraheze.org/wiki/Main_Page
https://spaceexploration.miraheze.org/wiki/Template:Infobox

--[[User:Vicarious|Vicarious]] ([[User talk:Vicarious|talk]]) 23:56, 7 November 2021 (UTC)
:Hey. I cannot assist you in breaking the license of this wiki. However, infoboxes are rather widespread concept, so there should be plenty of non-license-breaking inspiration out there. I would recommend to look into modern technology like [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Scribunto Extension:Scribunto] to build your infoboxes if you want to get as complicated as this wiki. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:00, 8 November 2021 (UTC)

:: Hm, I guess I should have looked closer at each wiki's license. Thanks for your time. --[[User:Vicarious|Vicarious]] ([[User talk:Vicarious|talk]]) 16:55, 8 November 2021 (UTC)

== Expandable tables/divs/etc ==

I noticed you didn't want a long list of sounds on the [[programmable speaker]] page. What if the list was put into an expandable table so that it didn't stretch the page by default? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 07:08, 19 November 2021 (UTC)
:That would improve the collapsed case, but once expanded, a list of over 300 things would still be a lot at once. So some kind of solution that collapses the contents of the second dropdown in the in-game GUI may be better, but that seems weird for example for the Miscellaneous category where the contents of the second dropdown is all that is interesting. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 12:17, 23 November 2021 (UTC)
::What if the table was designed in a way where the speaker choices were in rows? That is, if the table was 7-8 columns long, it would only be 37-50 cells tall. Which would be very tall, but no so much that it ruins the page? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 15:35, 23 November 2021 (UTC)
:::That sounds quite big still, especially for an item page. But it may be worth a try (perhaps with only some of the content, so that it's not a lot of work). -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:29, 29 November 2021 (UTC)

== Rocket rush ready to merge in ==

Hi, I decided to make my very first wiki contribution ever and created a page for the [[Rocket rush]] scenario. I have 0 experience contributing to a MediaWiki, so I have no idea if I followed the right protocol while building out the page--forgive me if I made things inconvenient. I linked the draft page off of my user page to facilitate building it out. Per the [[Factorio:Wiki_rules|rules]], I'm here asking an admin to merge this page into [[Game_modes_and_options]] -- [[User:While 1|While 1]] ([[User talk:While 1|talk]]) 14:08, 10 April 2022 (UTC)
: Thank you for the page! I made some formatting and wording changed and then merged it into the main namespace. The page must have been a lot of work with the item list, thank you for contributing it! -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:47, 11 April 2022 (UTC)

== Is it appropriate to add usage information for a linked belt, somewhere on this wiki? ==

Hi [[User:Bilka|Bilka]],

Hope all is well. Thanks for all you have done for this wiki -- it has provided me value on numerous occasions.

I read all of your edit summaries of your recent linked belt edits. Thanks for the information.

I also read [[Factorio:Wiki_rules|the rules]] and [[Factorio:Style_guide|the style guide]]. I apologize for not having read them before my edits. My bad.

Additionally, I read the [[Factorio:Editor_noticeboard|editor]] and [[Factorio:Admin_noticeboard|admin]] noticeboards to possibly further familiarize myself.

I want to keep this wiki being good.

I had spent a lot of time trying to figure out how to use a linked belt, that one can see in the vanilla map editor. Initially, I did not find linked belt usage information from [https://www.google.com/search?q=factorio+how+to+use+linked+belt my web searching]. I eventually found some information on how to use a linked belt from the Factorio Discord server.

This required more effort than getting the information from direct web searching. Thus, I wanted to record the information in a canonical, more accessible location, and I thought this wiki would be appropriate for this linked belt usage information.

Is it appropriate to add usage information for a linked belt, somewhere on this wiki?

If so, where would it be appropriate to add it? Perhaps at [[Prototype/LinkedBelt]]?

Thanks again.

Best, 
[[User:Snayday|Snayday]] ([[User talk:Snayday|talk]]) 18:44, 20 July 2022 (UTC)

: Hey, thank you for the nice words. I agree that usage information is good to have. My intention was to take all the info you added to the linked belt page and merge it into the prototype page. I see now that I missed mentioning that mods or console commands are needed for executing the linked script function. I added that to the page now.
: Another place where there could be more information is the console commands page, I could add a command to connect two linked belts. I don't know if that would help your usecase since your original page only mentioned "use mods". So, if my edit is not enough, feel free to add more info on Prototype/LinkedBelt. Or let me know what exactly you would like to add and we can figure out the best place to put it here on the wiki. Thank you for reaching out about this :) -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 19:30, 20 July 2022 (UTC)

:: Hey [[User:Bilka|Bilka]], thanks for your kind words as well. I felt like responding here to possibly make the dialogue here more complete, in case it's of use to anyone. Hopefully this is okay.
:: I believe I have made changes that cause the wiki to provide better usage information for [[Prototype/LinkedBelt|linked belts]]: On the [[console]] page (which is the redirect of [[console commands]]), I added the section [[Console#Connect_linked_belts]], and this new section is linked to in the [[Prototype/LinkedBelt|Prototype/LinkedBelt (linked belt)]] page.
:: (I also accidentally forgot to include an edit summary for one of my edits to [[Prototype/LinkedBelt]]. My bad. I don't think it's really an issue, but want you to know I intend to succinctly summarize my edits, if necessary.)
:: Thanks for getting back to me :)
:: Best, [[User:Snayday|Snayday]] ([[User talk:Snayday|talk]]) 05:50, 25 July 2022 (UTC)
::: Thank you for the great edits! The console command is clever, I wouldn't have thought of using the entity tags but it's quite convenient with the map editor interface for them. So thank you for that and your other edits, I look forward to seeing more contributions from you :) -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 13:50, 25 July 2022 (UTC)

== New language: Traditional Chinese (zh-TW, 繁體中文)==

Hello Bilka. Currently there's only Simplified Chinese (zh-CN, 简体中文) translation for the wiki. Simplified Chinese is mostly used in China, Singapore, Malaysia, while '''Tradtional Chinese (zh-TW, 繁體中文)''' is mostly used in Taiwan, Hong Kong, Korea and Japan.

Is it possible to add Traditioanl Chinese to the wiki? The difference between Simplified Chinese and Traditional Chinese mostly lies in expressions and terms. While they have much in common, I'd say the difference is much more significant than, for example, the difference between UK English and US English. Many platforms (such as [https://partner.steamgames.com/doc/store/localization/languages Steam]) also treat them as different languages.

If there's any criteria to add new language for Factorio wiki, feel free to let me know. Thank you for your good work!

--[[User:Johnruby|Johnruby]] ([[User talk:Johnruby|talk]]) 17:43, 3 March 2023 (UTC)

: See [[Factorio_talk:Editor_noticeboard#Request_to_add_new_language:_Traditional_Chinese_(zh-TW,_繁體中文)]]. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:51, 7 March 2023 (UTC)

== Translation verification ==
Hi Bilka, as you might have seen I tried to clean-up the category system and categorized a lot of uncategorized pages. Hope I wasn't to bold with my changes. I also build the [[Template:Translation verification]]. It basically just compares a revision-ID it is given to the revision-ID of the corresponding English page and depending on whether they match or not categorizes the page accordingly. I would like to suggest to add it to all translated pages (maybe it could even be directly integrated in [[Template:Languages]]?), so that editors know, when they have to update the translations again. Since it's quite a big change (and a lot of work) I wanted to consult with you before I start to add it to a lot of pages. I added it to [[:Category:Main/de]] and [[Main Page/Advanced/de]] as first examples. So: what do you think? :-) --[[User:Ickputzdirwech|Ickputzdirwech]] ([[User talk:Ickputzdirwech|talk]]) 23:07, 24 September 2023 (UTC)

: To answer your first concerns you mentioned on the forums:
:* How it works: The template does not simply compare revision dates. Instead when an editor updates a translation, they should also update the revision-ID in the template to the ID of the revision the translation was based on. (I find it hard to explain it properly, so best if you take a look at it yourself. No hurry.)
:* I can understand that you don't want to flood the wiki with notices, that basically every translation is outdated. A notice has two benefits however: 1. Without a notice hardly any casual reader would think: "That translation is outdated, let me fix it really quick". 2. In the notice I included a link to the differences between the current revision and the revision the translation was made for, so translators wouldn't have to check the whole page, but could simply click the link, see what has changed and update the translation accordingly. The notice could be omitted and only a categories would be added, but that would mean only experienced editors would know what to do, and there wouldn't be a quick link available.
:* To make it less intrusive the template could be added manually to one page after the other while updating the translations, not to all of them at once. This way we ensure that most pages the template is used on would be up do date. And the categories could be marked as hidden of course.
:I think it is vital to have a system in place to automatically check whether a translation is still up to date. Currently it's impossible to translate pages systematically. Unless someone put some useful information in the edit summary (and looking through the history is tedious anyway) you can't even see at first glace when a translation IS up to date. And every time, the whole page has to be checked, even if just one word has changed since you don't know, which revision the current translation references. --[[User:Ickputzdirwech|Ickputzdirwech]] ([[User talk:Ickputzdirwech|talk]]) 17:03, 25 September 2023 (UTC)
:: Hey! You were quite bold with your changes, especially to the navboxes and templates included in many pages. As we already talked about, that generated quite a bit of server load, but it's fine now. And your changes look good!
:: Regarding the template, thank you for responding to my initial concerns we talked about via Forum PM. The revision ID based approach you explain/the page uses is indeed better than what I was thinking it was after a quick glance (I thought it was taking the current ID and comparing its timestamp with the English page).
:: In my experience, adding more notices will just lead to readers missing them because they become so commonplace. We already have problems with people missing the "Archived" box. So I don't think the notice would have the desired effect you describe and I would prefer to do only categorization. That means we indeed lose the diff link, but it could be explained how to make it on the category page, since the revision id itself will be in the page source.
:: Adding the template as you translate sounds good! It would replace the tracking of the translated revision ID that some people have been doing via the edit summary (you included :)) and would make it easy to get an overview via the categories. I would say that is a good usecase for the template and at least partially solves the problem you describe. Maybe you can also find a good spot to link the categories in the [[Factorio:Translation guide]] together with mentioning the template. That way the categories on the pages would also serve as a (less intrusive) notice for translators.
:: Would it help at all if I updated [[User:Bilka/Outdated_pages]] more frequently or made it a proper page? I somewhat abandoned that project once it was clear that nearly everything was outdated and the date comparison was very inaccurate. But it's an existing script after all, so it doesn't cost me anything to run it every Friday or every month or something. For what it's worth, I just ran the script and it updated the page.
:: So what is to be done here now is: Removing the notice from the template. Giving usage instructions in the translation guide. And using it :D -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:39, 4 October 2023 (UTC)

== Is it possible to restore this image? ==

Hello Bilka

I had added an example to [[Tutorial:Circuit network cookbook#Optimal usage of fuel for nuclear power]] [https://wiki.factorio.com/index.php?title=Tutorial:Circuit_network_cookbook&diff=prev&oldid=185730] with the picture [[:File:NuclearCircuits2.jpg]], but it has been removed by [[User:Samzvr|Samzvr]] without discussion [https://wiki.factorio.com/index.php?title=Tutorial:Circuit_network_cookbook&diff=prev&oldid=190516] (and you deleted the pic because it didn't have any use).

I don't understand the first example, and despite what Samzvr says, mine was working fine.

Would it be possible to restore this picture to put this example back, or at least so that I can use it in my personal page?

Ragards, [[User:SyntaxTerror|Şÿℵדαχ]][[User talk:SyntaxTerror|₮ɘɼɾ๏ʁ]] 05:12, 11 October 2023 (UTC)

: Hey, the image was an input inserter for a reactor connected to the circuit network with the enable condition [steam = 2k], reading from one steam storage tank. The wiki is not the right place for a personal design library, so I'd rather not add the image back. The cookbook already shows simple setups with just one condition for turning on inserter, so I don't think it adds anything to show it again. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 16:28, 24 November 2023 (UTC)

== Syntax highlighting and category tree extensions ==
Hey Bilka, I would like to suggest to install the following extensions:
* [https://www.mediawiki.org/wiki/Extension:CodeMirror Extension:CodeMirror] and
* [https://www.mediawiki.org/wiki/Extension:CategoryTree Extension:CategoryTree]
While the former makes the use of the in-browser-editor much simpler, the later improves the navigation through categories. --[[User:Ickputzdirwech|Ickputzdirwech]] ([[User talk:Ickputzdirwech|talk]]) 09:03, 11 October 2023 (UTC)
:And I thought of another one :)
:* [https://www.mediawiki.org/wiki/Extension:Display_Title Extension:Display Title]
:As I understand it, it would make the whole [[Template:TransLink]] shenanigans obsolete. But what would be the main advantage imo, would be that even on category pages the display titles would be shown. For example on [[:Category:Fluids/de]] the first entry "Crude oil/de" would instead be "Rohöl". Thanks for consideration! --[[User:Ickputzdirwech|Ickputzdirwech]] ([[User talk:Ickputzdirwech|talk]]) 09:32, 11 October 2023 (UTC)
:: Hey, thank you for the suggestions!
:: The CodeMirror extension looks very useful, I'll look into getting it installed by the ops people.
:: For CategoryTree, could you elaborate on where you'd use the display? Our category setup is quite shallow in general and mostly replicates the in-game organisation, which is already better visible in the navboxes and Template:Inventory. So I'm not directly seeing a spot where browsing the categories and subcategories needs improvement.
:: For the display title expansion, I'm divided. We'd still need TransLink for the automatic suffixing of links in templates. For the page source text there would not be much of a difference between <code><nowiki>[[Plastic bar/de]]</nowiki></code> and <code><nowiki>{{L|Plastic bar}}</nowiki></code>. And the former has the disadvantage of making it less clear where the translation is coming from. But the point regarding page names in categories is very good, that would be quite nice. Which ends up with me being divided on whether it should be added. Do you have further points for/against the extension? Thank you for the effort you put into improving the wiki! -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 17:23, 1 December 2023 (UTC)

== New pages are not appearing in Language category ==

Hi, I noticed that something strange is going on with the new pages. I translated a few pages and none of them weren't added to the [[:Category:Ukrainian_page]] automatically. Am I missing something or is this a bug? Or is there a delay?

https://wiki.factorio.com/Utility_science_pack_(research)/uk
https://wiki.factorio.com/Production_science_pack_(research)/uk
https://wiki.factorio.com/Combinators/uk
https://wiki.factorio.com/Tutorial:Keyboard_shortcuts/uk {{Unsigned|Factorles|09:46, 27 February 2024‎}}
: Hey, there is a small delay/cache, but it should not be very long. It looks like the cache of the category/pages just didn't get refreshed for some reason. As you can see, I edited Production_science_pack_(research)/uk again and it now shows up, almost instantly. You can make similar edits, or [https://meta.wikimedia.org/wiki/Help:Dummy_edit#Null_edit Null edits] to the other pages and they should show up too. Sorry for the inconvenience, but the wiki software heavily utilises caching and sometimes things just go wrong :/ -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:41, 27 February 2024 (UTC)

== About an destroyer capsule page ==

Sorry, I made a mistake. The Destroyer page said "unlimited laser energy" and I misunderstood. Can I correct the Destroyer page to "electrical energy"? --[[User:Zefard|Zefard]] ([[User talk:Zefard|talk]]) 12:09, 18 May 2024 (UTC)
: No worries, these damage types can be confusing! Of course you can correct the page, any page is open for edits :) -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 12:14, 18 May 2024 (UTC)
:: Thanks! --[[User:Zefard|Zefard]] ([[User talk:Zefard|talk]]) 12:29, 18 May 2024 (UTC)

== Beaconed oil throughput ==

About your edit in https://wiki.factorio.com/index.php?title=Pumpjack&type=revision&diff=198674&oldid=198673
As far as I see, your value of 0.5 additional oil per beacon is wrong. Original output for 20% is 2. Productivity from 2 speed modules is +50%+50%=+100%. With 50% beacon efficiency, it's +50%. 50% of 2 is 1. Not 0.5. That's also what will result from the formula in the article. (Just asking here instead of starting some edit war.)
[[User:Tertius3|Tertius3]] ([[User talk:Tertius3|talk]]) 14:04, 13 June 2024 (UTC)
: Thanks! You are right, I was thinking of 0.5 additional mining speed. Which is correct, but the sentence is talking about the oil output per second, which indeed is 1/s extra with 0.5 extra mining speed. Thank you for pointing this out! -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 14:12, 13 June 2024 (UTC)

== Increasing amount of tab-headers for the Inventory-like templates ==

Hello. There is this part of the code in the Mediawiki:Common.js, featuring tab-heads. I want to create a Template:Factoriopedia, similar to the Template:Inventory, but I need 11 tab-heads for that and currently there are only 4 of them supported. I would be grateful if they were added to the Common.js file. 01:00, 21 October 2024 (UTC)
: Hey, I added support for up to 11 tab heads. However, I'd prefer if we didn't have separate inventory and factoripedia templates, since they serve quite similar purposes. Instead, it would be nice if you could try to update Template:Inventory with the new Space Age features and other relevant stuff but leave out tabs that are useless on the wiki because we merge pages. I'm thinking leaving out the signals, unsorted, enemies and tiles tabs. The enemies could have one icon per type (biter/spitter and so on) and go into an environment tab that roughly reflects what is in [[Template:EnvironmentNav]] right now. Similarly, the fluids can likely stay in the intermediates tab, same for the remotes and other things now spawned via the shortcut bar. I used a script to upload all the icons you'll need :D -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 08:04, 21 October 2024 (UTC)

:: Thanks for the quick response! I understand the idea about keeping only relevant to the normal playthrough information on the Template:Inventory and I will update that too, corresponding to the new SA Inventory screen. However I think it still will be useful to have a Template:Factoriopedia, which looks the same way the in-game version does. Also I think that Template:Inventory deserves some sort of indication based on the 2.0/SA version(still hesitant about that), though that can be achieved with small inline icon (DLC or SA), without making a separate Inventory template for SA content to keep things more organized.
:: I also want to change the InfoBox, to contain the info listed in the Factoriopedia. And I not sure how to approach the stack<->bulk inserter name change, do you have ideas about that? Would be confusing for user to leave old stack inserter name unchanged.
:: Also I can't see any new icons added to the uploaded files.
:: - LoerisOtter 09:52, 21 October 2024 (UTC)
::: My concern with making tabs for things like tiles and signals is that the icons currently aren't on the wiki and I don't think we should have separate pages for them. There is not relevant information for us to give on say dirt 7 vs dirt 6 or signal-x vs signal-y. So you'd have to upload and show a lot of icons for things that will all end up linking to the same overview page ([[Tile]] and [[Circuit network]]). Maybe there is a way to adjust the Template:Inventory to reflect the Factoriopedia organisation more without that pitfall.
::: The bulk and stack inserter rename will be present for everyone, so it's a simple matter of moving those page. I'm in the process of creating a script that will do rename-related page moves upon release. The pages can then get [[Template:About]] added to them to point to each other to reduce confusion.
::: Please let me handle Template:Infobox itself, it's protected for normal editors anyway. But for things to add there, the talk page of the template is the right place for suggestions, I will definitely take those into account! There just needs to be a lot adjusted to account for the ability to turn on/off space age, similar to how expensive mode is currently handled, so it might take a bit to get updated. (See also https://forums.factorio.com/108987)
::: Because I used a bot to update the icons they don't show in the recent changes by default. You can either check the option to show bot changes in the upload log or check [[Special:Contributions/BilkaBot]] to see them. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:05, 21 October 2024 (UTC)

:::: Okay, I see how tiles tab and signals tab might be confusing, because there's little sense in creating separate page for each tile. Regarding the bot - Thanks for the icons. I now see the uploads, however the Fluoroketone.png image is blank and I also need these files: (currently has mockup image) - "Item-group space" "Item-group enemies".(currently has placeholder image) - "Item-group unsorted" "Item-group tiles" "Item-group environment"
:::: - LoerisOtter 09:52, 21 October 2024 (UTC)
::::: Oops, Fluoroketone.png shouldn't have been uploaded, it does not appear to be used from what I could find quickly - the game always distinguishes between hot and cold fluoroketone. Item groups updated :D -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 10:26, 21 October 2024 (UTC)

== Prototype type link in infobox ==

I think that when you are at the process of upgrading {{T|Infobox}}, you can change "prototype type" to actually link to [https://lua-api.factorio.com/latest/ api page] not wiki page. Since there is no wiki page for [[cargo landing pad]] prototype, and these pages are not updated. ~~ [[User:Mefisto1029|Mefisto1029]] ([[User talk:Mefisto1029|talk]]) 19:36, 24 October 2024 (UTC)
: Yep, that was in my todo list for the 2.0 update and it's now done :D -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - Admin 13:39, 25 October 2024 (UTC)

== Wiki skin refresh ==

The current wiki skin seems a bit outdated and boring, especially when compared to other places like the main Factorio website and mod portal. I'm taking a lot of reference from the [https://terraria.wiki.gg/wiki/Terraria_Wiki Terraria] and the [https://minecraft.wiki/ Minecraft] wikis. It doesn't have to be much, just enough to make it not look entirely plain and gray.

- [[User:EpicPuppy613|EpicPuppy613]] ([[User talk:EpicPuppy613|talk]]) 00:36, 3 November 2024 (UTC)

: I experimented a little bit with a general idea of what a wiki skin refresh could look like, as seen in my [[User:EpicPuppy613/common.css]].

: - [[User:EpicPuppy613|EpicPuppy613]] ([[User talk:EpicPuppy613|talk]]) 03:25, 3 November 2024 (UTC)

== Infobox Issue ==

I'm sure you're aware of this already, but as you can see from [[Epic_quality_(research)|this page]], the effect (which is supposed to be the quality icons) won't show. Not sure how to rectify that, since the Infobox page is locked down. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:13, 10 November 2024 (UTC)
:Nevermind, someone figured it out. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:47, 10 November 2024 (UTC)
::I fixed it so the icon shows but there is probably a more correct workaround instead of linking "Quality epic" --[[User:Thoxo|Thoxo]] ([[User talk:Thoxo|talk]]) 10:38, 10 November 2024 (UTC)

Infobox:Epic quality (research)

2024-11-10T03:41:17Z

Thoxo: Fixed missing icon in effects

{{Infobox
|cost = Time, 60 + Automation science pack + Logistic science pack + Chemical science pack + Utility science pack + Space science pack + Agricultural science pack
|cost-multiplier = 5000
|effects = quality epic
|prototype-type = technology
|internal-name = epic-quality
| category = Crafting
|allows = Legendary quality
}}<noinclude>[[Category:Infobox page]]</noinclude>

Oil processing

2024-11-10T03:21:49Z

Thoxo: /* Overview */ fixed icon for calcite processing research

{{Languages}}
'''Oil processing''' is a large part of Factorio. Oil processing may refer to [[Oil processing (research)|the researched technology]], the recipe used in the [[oil refinery]], or the overall workings of oil.

== Overview ==
There are various recipes that can be used to process [[crude oil]] into its fractions. Its fraction ([[heavy oil]], [[light oil]] and [[petroleum gas]]) can also be cracked into each other. Their recipes and technology requirements can be seen below.

{|class="wikitable"
|-
! Process !! Input !! Output !! Machine !! Required technology !! Internal name
|-
| {{Icon|Basic oil processing||}} Basic oil processing || {{icon|time|5}} + {{Icon|Crude oil|100}} || {{Icon|Petroleum gas|45}} || {{Icon|Oil refinery}} || {{icontech|Oil processing (research)|}} [[Oil processing (research)|Oil processing]] || basic-oil-processing
|-
| {{Icon|Advanced oil processing||}} Advanced oil processing || {{icon|time|5}} + {{Icon|Crude oil|100}} + {{icon|water|50}} || {{Icon|Heavy oil|25}} + {{Icon|Light oil|45}} + {{Icon|Petroleum gas|55}} || {{Icon|Oil refinery}} || {{icontech|Advanced oil processing (research)|}} [[Advanced oil processing (research)|Advanced oil processing]] || advanced-oil-processing
|-
| {{Icon|Heavy oil cracking||}} Heavy oil cracking || {{icon|time|2}} + {{Icon|Heavy oil|40}} + {{icon|water|30}} || {{Icon|Light oil|30}} || {{Icon|Chemical plant}} || {{icontech|Advanced oil processing (research)|}} [[Advanced oil processing (research)|Advanced oil processing]] || heavy-oil-cracking
|-
| {{Icon|Light oil cracking||}} Light oil cracking || {{icon|time|2}} + {{Icon|Light oil|30}} + {{icon|water|30}} || {{Icon|Petroleum gas|20}} || {{Icon|Chemical plant}} || {{icontech|Advanced oil processing (research)|}} [[Advanced oil processing (research)|Advanced oil processing]] || light-oil-cracking
|-
| {{Icon|Simple coal liquefaction||space-age=yes}} Simple coal liquefaction || {{icon|time|5}} + {{icon|coal|10}} + {{icon|Calcite|2|space-age=yes}} + {{icon|Sulfuric acid|25}} || {{Icon|Heavy oil|50}} || {{Icon|Oil refinery}} || {{icontech|calcite processing (research)}} [[Calcite processing (research)|Calcite processing]] || simple-coal-liquefaction
|-
|| {{Icon|Coal liquefaction||}} Coal liquefaction || {{icon|time|5}} + {{icon|coal|10}} + {{Icon|Heavy oil|25}} + {{icon|steam|50}} || {{Icon|Heavy oil|90}} + {{Icon|Light oil|20}} + {{Icon|Petroleum gas|10}} || {{Icon|Oil refinery}} || {{icontech|coal liquefaction|}} [[Coal liquefaction (research)|Coal liquefaction]] || coal-liquefaction
|}

== Setting up oil processing ==
[[Pumpjack]]s need to be placed on top of the middle of the oil well, which is highlighted with a green box when the pumpjack is held. Pumpjacks produce a certain amount of [[Crude oil]] per second, shown on the right, at the bottom of the information panel.

Crude oil must be refined in an [[oil refinery]]. The oil refinery needs to have a recipe set (see above for available recipes). Once it is set and "alt-mode" is active, the input and output locations and the expected fluids are shown. The locations of these cannot be changed, only the entire machine can be rotated.

Advanced oil processing and coal liquefaction produce multiple fluids: [[heavy oil]], [[light oil]] and [[petroleum gas]]. The refinery will stop production of all products if one product output is full, so it should be ensured that the products are transported out of the refinery; any products that cannot be used should be (temporarily) stored in a [[storage tank]]. Furthermore, both heavy oil and light oil can be cracked to the next lower type in a [[chemical plant]] (recipe above). This is useful if the player has an abundance of one product, but is lacking another (a common problem).

=== Tips ===
* The [[circuit network]] can be used to easily control how much fluid gets used for each recipe, to ensure that the player always has enough. For examples on how to do this, see the [[Tutorial:Circuit network cookbook#Oil_Setups|circuit-network cookbook]].
* If you run your heavy oil pipe from the refineries past a lubricant-making chemical plant before sending it to the cracking chemical plants, you can be sure that the lubricant production will have priority over cracking.
* [[Solid fuel]] is most efficient when created from light oil. If the player has too much heavy oil, cracking it to light oil then making it into fuel is more efficient than making heavy oil into fuel directly.

=== Coal Liquefaction ===
Once coal liquefaction is researched, the player can manufacture oil products anywhere without a need for crude oil: the player can set up an oil refinery to utilize coal liquefaction and use an [[assembling machine]] and [[barrel]]s to manually insert a small amount of heavy oil into the system to initiate production. As long as the heavy oil output is routed back into the refinery before being sent anywhere else, the refinery will be self-sustaining in terms of heavy oil, only requiring steam and coal to run. To prevent fluid back-up, the player will need to ensure all output fluids are being consumed or stored somehow.

While a single refinery using this set-up this will not produce a large amount of oil products overall, the fact it does not require crude oil to run means it can be placed anywhere the player needs a small, steady supply of oil products, saving the need to transport oil over large distances by pipes or trains. Such uses include:

* A refueling outpost that produces [[solid fuel]] and/or [[rocket fuel]].
* A defensive outpost that uses oil to fuel [[flamethrower turret]]s.
* With a supply of [[iron ore]], this set-up can produce [[sulfuric acid]], allowing the mining of [[uranium ore]].
* A supply of iron ore also allows the manufacture of ammunition: [[cluster grenade]]s, [[land mine]]s, and [[cannon shell]]s.
* With a supply of both iron ore and [[copper ore]], [[rocket]]s and [[artillery shell]]s can be manufactured, as well as all [[capsules]].

More broadly, a sufficiently large network of refineries utilizing coal liquefaction could produce enough oil products to run the player's factory without a need for crude oil anymore, allowing much more flexibility in the layout and placement of facilities that require oil products to function. The downside of relying entirely on coal liquefaction are an overall slightly lower output of oil products compared to advanced oil processing, a need for more chemical plants to crack the large amounts of heavy oil produced, and the system will shut down entirely if its supply of coal or steam runs out.

=== Transporting fluids ===
There are many ways to move fluids in Factorio, they are listed below:

* [[Pipe]]s
* [[Fluid wagon]]s
* Loading the fluids into [[Barrel]]s and transporting them by [[Railway]], [[Transport belts]], or the [[Logistic network]]

== Optimal Ratios ==
The optimal ratio is the ratio of production that ensures no waste of time or materials.

=== Petroleum gas production ===

For producing petroleum gas, the optimal advanced oil processing ratio is 20:5:17 (advanced oil processing : heavy oil cracking : light oil cracking), and 8:2:7 is close enough. Using coal liquefaction, the ratio is 60:39:55 (coal liquefaction : heavy oil cracking : light oil cracking), and 12:8:11 is close enough.

One refinery running basic oil processing produces 9 petroleum gas per second. One refinery running advanced oil processing combined with one of each oil cracking chemical plant produces 19.5 petroleum gas per second in total. One refinery running coal liquefaction combined with one of each oil cracking chemical plant produces close to 11.2 petroleum gas per second in total (taking into consideration the recycling of the heavy oil).

The refining can be sped up with [[module]]s; to prevent jams or inactive buildings it is recommended to speed everything up evenly. When slowing the process down (by using [[productivity module]]s) you are better off experimenting on altering the ratio or the speed on certain buildings, since the default ratios given above only hold if all the structures involved run at the same speed and have 100% productivity (in other words, no bonuses).

{| class="wikitable mw-collapsible mw-collapsed" style="text-align: center;"
!colspan="5" |Petroleum production output with modules
|-
!colspan="1" style="width: 230px; text-align: left;" |Module configuration
!colspan="1" style="width: 75px;" |None
!colspan="1" style="width: 75px;" |Config 1 (*)
!colspan="1" style="width: 75px;" |Config 2
!colspan="1" |Units
|-
!colspan="5"|Oil refinery
|-
! style="text-align: left;" | Crude oil consumption
| 100 || 100 || 100 ||
|-
! style="text-align: left;" | Water consumption
| 50 || 50 || 50 ||
|-
! style="text-align: left;" | Crafting speed
| 5 || 5 || 5 || s / final item
|-
! style="text-align: left;" | Heavy oil output
| 25 || 25 || 25 ||
|-
! style="text-align: left;" | Light oil output
| 45 || 45 || 45 ||
|-
! style="text-align: left;" | Petroleum output
| 55 || 55 || 55 ||
|-
! style="text-align: left;" | Base machine crafting speed
| 1 || 1 || 1 || crafts / s
|-
! style="text-align: left;" | Crafting speed multiplier
| 100% || 455% || 855% ||
|-
! style="text-align: left;" | Output multiplier
| 100% || 130% || 130% || final items
|-
! style="text-align: left;" | Total Crude oil consumption
| 20 || 91 || 171 || per second
|-
! style="text-align: left;" | Total Water consumption
| 10 || 45.5 || 85.5 || per second
|-
! style="text-align: left;" | Total Heavy oil output
| 5 || 29.575 || 55.575 || per second
|-
! style="text-align: left;" | Total Light oil output
| 9 || 53.235 || 100.035 || per second
|-
! style="text-align: left;" | Total Petroleum output
| 11 || 65.065 || 122.265 || per second
|-
!colspan="5"|Heavy oil cracking
|-
! style="text-align: left;" | Heavy oil consumption
| 40 || 40 || 40 ||
|-
! style="text-align: left;" | Water consumption
| 30 || 30 || 30 ||
|-
! style="text-align: left;" | Crafting speed
| 2 || 2 || 2 || s / final item
|-
! style="text-align: left;" | Light oil output
| 30 || 30 || 30 ||
|-
! style="text-align: left;" | Base machine crafting speed
| 1 || 1 || 1 || crafts / s
|-
! style="text-align: left;" | Crafting speed multiplier
| 100% || 455% || 655% ||
|-
! style="text-align: left;" | Output multiplier
| 100% || 130% || 130% || final items
|-
! style="text-align: left;" | Total Heavy oil consumption
| 20 || 91 || 131 || per second
|-
! style="text-align: left;" | Total Water consumption
| 15 || 68.25 || 98.25 || per second
|-
! style="text-align: left;" | Total Light oil output
| 15 || 88.725 || 127.725 || per second
|-
!colspan="5"|Light oil cracking
|-
! style="text-align: left;" | Light oil consumption
| 30 || 30 || 30 ||
|-
! style="text-align: left;" | Water consumption
| 30 || 30 || 30 ||
|-
! style="text-align: left;" | Crafting speed
| 2 || 2 || 2 || s / final item
|-
! style="text-align: left;" | Petroleum output
| 20 || 20 || 20 ||
|-
! style="text-align: left;" | Base machine crafting speed
| 1 || 1 || 1 || crafts / s
|-
! style="text-align: left;" | Crafting speed multiplier
| 100% || 455% || 655% ||
|-
! style="text-align: left;" | Output multiplier
| 100% || 130% || 130% || final items
|-
! style="text-align: left;" | Total Light oil consumption
| 15 || 68.25 || 98.25 || per second
|-
! style="text-align: left;" | Total Water consumption
| 15 || 68.25 || 98.25 || per second
|-
! style="text-align: left;" | Total Petroleum output
| 10 || 59.15 || 85.15 || per second
|-
!colspan="5"|Ratio
|-
! style="text-align: left;" | Heavy oil cracking
| 0.25 || 0.325 || 0.424 ||
|-
! style="text-align: left;" | Light oil cracking
| 0.85 || 1.2025 || 1.57 ||
|-
! style="text-align: left;" | Petroleum gas output
| 19.5 || 136.193 || 255.923 || per second
|-
|colspan="5" style="width: 600px; text-align: left;" | '''* Notes to table:''' ''Config 1'' is 3 Productivity modules 3 in each production building and 8 Beacons with 2 Speed modules 3 each in range of each production building. ''Config 2'' is 3 Productivity modules 3 in each production building and the highest achievable number of Beacons (16 for Refinery, 12 for Chemical plant) with 2 Speed modules 3 each in range of each prod. building.
|}

For config 2 in the above (possibly collapsed) table, a good enough ratio is 7:3:11, and the next ratio that is better is 165:70:259. The optimal ratio involves over 50000 refineries, and so is practically useless. But, for reference, it's 52400:22230:82251.

== History ==
{{history|0.17.60|
* Basic oil processing produces only petroleum gas.}}

{{history|0.17.0|
* Coal liquefaction now produces 90 heavy oil, 20 light oil and 10 petroleum gas, consuming 25 heavy oil, 10 coal and 50 steam.}}

{{history|0.15.0|
* Added coal liquefaction oil processing recipe.}}

{{history|0.9.1|
* Added heavy oil cracking and light oil cracking.}}

{{history|0.9.0|
* Introduced
**Basic oil processing
**Advanced oil processing}}

== See also ==
* [[Fluid system]]
* [[Crude oil]]
* [[Barrel]]

{{C|Main}}

Simple coal liquefaction

2024-11-10T03:18:56Z

Thoxo: Created redirect page

#REDIRECT [[Oil processing]]

Oil processing

2024-11-10T03:18:10Z

Thoxo: /* Overview */ Add simple coal liquefaction

{{Languages}}
'''Oil processing''' is a large part of Factorio. Oil processing may refer to [[Oil processing (research)|the researched technology]], the recipe used in the [[oil refinery]], or the overall workings of oil.

== Overview ==
There are various recipes that can be used to process [[crude oil]] into its fractions. Its fraction ([[heavy oil]], [[light oil]] and [[petroleum gas]]) can also be cracked into each other. Their recipes and technology requirements can be seen below.

{|class="wikitable"
|-
! Process !! Input !! Output !! Machine !! Required technology !! Internal name
|-
| {{Icon|Basic oil processing||}} Basic oil processing || {{icon|time|5}} + {{Icon|Crude oil|100}} || {{Icon|Petroleum gas|45}} || {{Icon|Oil refinery}} || {{icontech|Oil processing (research)|}} [[Oil processing (research)|Oil processing]] || basic-oil-processing
|-
| {{Icon|Advanced oil processing||}} Advanced oil processing || {{icon|time|5}} + {{Icon|Crude oil|100}} + {{icon|water|50}} || {{Icon|Heavy oil|25}} + {{Icon|Light oil|45}} + {{Icon|Petroleum gas|55}} || {{Icon|Oil refinery}} || {{icontech|Advanced oil processing (research)|}} [[Advanced oil processing (research)|Advanced oil processing]] || advanced-oil-processing
|-
| {{Icon|Heavy oil cracking||}} Heavy oil cracking || {{icon|time|2}} + {{Icon|Heavy oil|40}} + {{icon|water|30}} || {{Icon|Light oil|30}} || {{Icon|Chemical plant}} || {{icontech|Advanced oil processing (research)|}} [[Advanced oil processing (research)|Advanced oil processing]] || heavy-oil-cracking
|-
| {{Icon|Light oil cracking||}} Light oil cracking || {{icon|time|2}} + {{Icon|Light oil|30}} + {{icon|water|30}} || {{Icon|Petroleum gas|20}} || {{Icon|Chemical plant}} || {{icontech|Advanced oil processing (research)|}} [[Advanced oil processing (research)|Advanced oil processing]] || light-oil-cracking
|-
| {{Icon|Simple coal liquefaction||space-age=yes}} Simple coal liquefaction || {{icon|time|5}} + {{icon|coal|10}} + {{icon|Calcite|2|space-age=yes}} + {{icon|Sulfuric acid|25}} || {{Icon|Heavy oil|50}} || {{Icon|Oil refinery}} || {{icontech|calcite-processing|space-age=yes}} [[Calcite processing (research)|Calcite processing]] || simple-coal-liquefaction
|-
|| {{Icon|Coal liquefaction||}} Coal liquefaction || {{icon|time|5}} + {{icon|coal|10}} + {{Icon|Heavy oil|25}} + {{icon|steam|50}} || {{Icon|Heavy oil|90}} + {{Icon|Light oil|20}} + {{Icon|Petroleum gas|10}} || {{Icon|Oil refinery}} || {{icontech|coal liquefaction|}} [[Coal liquefaction (research)|Coal liquefaction]] || coal-liquefaction
|}

== Setting up oil processing ==
[[Pumpjack]]s need to be placed on top of the middle of the oil well, which is highlighted with a green box when the pumpjack is held. Pumpjacks produce a certain amount of [[Crude oil]] per second, shown on the right, at the bottom of the information panel.

Crude oil must be refined in an [[oil refinery]]. The oil refinery needs to have a recipe set (see above for available recipes). Once it is set and "alt-mode" is active, the input and output locations and the expected fluids are shown. The locations of these cannot be changed, only the entire machine can be rotated.

Advanced oil processing and coal liquefaction produce multiple fluids: [[heavy oil]], [[light oil]] and [[petroleum gas]]. The refinery will stop production of all products if one product output is full, so it should be ensured that the products are transported out of the refinery; any products that cannot be used should be (temporarily) stored in a [[storage tank]]. Furthermore, both heavy oil and light oil can be cracked to the next lower type in a [[chemical plant]] (recipe above). This is useful if the player has an abundance of one product, but is lacking another (a common problem).

=== Tips ===
* The [[circuit network]] can be used to easily control how much fluid gets used for each recipe, to ensure that the player always has enough. For examples on how to do this, see the [[Tutorial:Circuit network cookbook#Oil_Setups|circuit-network cookbook]].
* If you run your heavy oil pipe from the refineries past a lubricant-making chemical plant before sending it to the cracking chemical plants, you can be sure that the lubricant production will have priority over cracking.
* [[Solid fuel]] is most efficient when created from light oil. If the player has too much heavy oil, cracking it to light oil then making it into fuel is more efficient than making heavy oil into fuel directly.

=== Coal Liquefaction ===
Once coal liquefaction is researched, the player can manufacture oil products anywhere without a need for crude oil: the player can set up an oil refinery to utilize coal liquefaction and use an [[assembling machine]] and [[barrel]]s to manually insert a small amount of heavy oil into the system to initiate production. As long as the heavy oil output is routed back into the refinery before being sent anywhere else, the refinery will be self-sustaining in terms of heavy oil, only requiring steam and coal to run. To prevent fluid back-up, the player will need to ensure all output fluids are being consumed or stored somehow.

While a single refinery using this set-up this will not produce a large amount of oil products overall, the fact it does not require crude oil to run means it can be placed anywhere the player needs a small, steady supply of oil products, saving the need to transport oil over large distances by pipes or trains. Such uses include:

* A refueling outpost that produces [[solid fuel]] and/or [[rocket fuel]].
* A defensive outpost that uses oil to fuel [[flamethrower turret]]s.
* With a supply of [[iron ore]], this set-up can produce [[sulfuric acid]], allowing the mining of [[uranium ore]].
* A supply of iron ore also allows the manufacture of ammunition: [[cluster grenade]]s, [[land mine]]s, and [[cannon shell]]s.
* With a supply of both iron ore and [[copper ore]], [[rocket]]s and [[artillery shell]]s can be manufactured, as well as all [[capsules]].

More broadly, a sufficiently large network of refineries utilizing coal liquefaction could produce enough oil products to run the player's factory without a need for crude oil anymore, allowing much more flexibility in the layout and placement of facilities that require oil products to function. The downside of relying entirely on coal liquefaction are an overall slightly lower output of oil products compared to advanced oil processing, a need for more chemical plants to crack the large amounts of heavy oil produced, and the system will shut down entirely if its supply of coal or steam runs out.

=== Transporting fluids ===
There are many ways to move fluids in Factorio, they are listed below:

* [[Pipe]]s
* [[Fluid wagon]]s
* Loading the fluids into [[Barrel]]s and transporting them by [[Railway]], [[Transport belts]], or the [[Logistic network]]

== Optimal Ratios ==
The optimal ratio is the ratio of production that ensures no waste of time or materials.

=== Petroleum gas production ===

For producing petroleum gas, the optimal advanced oil processing ratio is 20:5:17 (advanced oil processing : heavy oil cracking : light oil cracking), and 8:2:7 is close enough. Using coal liquefaction, the ratio is 60:39:55 (coal liquefaction : heavy oil cracking : light oil cracking), and 12:8:11 is close enough.

One refinery running basic oil processing produces 9 petroleum gas per second. One refinery running advanced oil processing combined with one of each oil cracking chemical plant produces 19.5 petroleum gas per second in total. One refinery running coal liquefaction combined with one of each oil cracking chemical plant produces close to 11.2 petroleum gas per second in total (taking into consideration the recycling of the heavy oil).

The refining can be sped up with [[module]]s; to prevent jams or inactive buildings it is recommended to speed everything up evenly. When slowing the process down (by using [[productivity module]]s) you are better off experimenting on altering the ratio or the speed on certain buildings, since the default ratios given above only hold if all the structures involved run at the same speed and have 100% productivity (in other words, no bonuses).

{| class="wikitable mw-collapsible mw-collapsed" style="text-align: center;"
!colspan="5" |Petroleum production output with modules
|-
!colspan="1" style="width: 230px; text-align: left;" |Module configuration
!colspan="1" style="width: 75px;" |None
!colspan="1" style="width: 75px;" |Config 1 (*)
!colspan="1" style="width: 75px;" |Config 2
!colspan="1" |Units
|-
!colspan="5"|Oil refinery
|-
! style="text-align: left;" | Crude oil consumption
| 100 || 100 || 100 ||
|-
! style="text-align: left;" | Water consumption
| 50 || 50 || 50 ||
|-
! style="text-align: left;" | Crafting speed
| 5 || 5 || 5 || s / final item
|-
! style="text-align: left;" | Heavy oil output
| 25 || 25 || 25 ||
|-
! style="text-align: left;" | Light oil output
| 45 || 45 || 45 ||
|-
! style="text-align: left;" | Petroleum output
| 55 || 55 || 55 ||
|-
! style="text-align: left;" | Base machine crafting speed
| 1 || 1 || 1 || crafts / s
|-
! style="text-align: left;" | Crafting speed multiplier
| 100% || 455% || 855% ||
|-
! style="text-align: left;" | Output multiplier
| 100% || 130% || 130% || final items
|-
! style="text-align: left;" | Total Crude oil consumption
| 20 || 91 || 171 || per second
|-
! style="text-align: left;" | Total Water consumption
| 10 || 45.5 || 85.5 || per second
|-
! style="text-align: left;" | Total Heavy oil output
| 5 || 29.575 || 55.575 || per second
|-
! style="text-align: left;" | Total Light oil output
| 9 || 53.235 || 100.035 || per second
|-
! style="text-align: left;" | Total Petroleum output
| 11 || 65.065 || 122.265 || per second
|-
!colspan="5"|Heavy oil cracking
|-
! style="text-align: left;" | Heavy oil consumption
| 40 || 40 || 40 ||
|-
! style="text-align: left;" | Water consumption
| 30 || 30 || 30 ||
|-
! style="text-align: left;" | Crafting speed
| 2 || 2 || 2 || s / final item
|-
! style="text-align: left;" | Light oil output
| 30 || 30 || 30 ||
|-
! style="text-align: left;" | Base machine crafting speed
| 1 || 1 || 1 || crafts / s
|-
! style="text-align: left;" | Crafting speed multiplier
| 100% || 455% || 655% ||
|-
! style="text-align: left;" | Output multiplier
| 100% || 130% || 130% || final items
|-
! style="text-align: left;" | Total Heavy oil consumption
| 20 || 91 || 131 || per second
|-
! style="text-align: left;" | Total Water consumption
| 15 || 68.25 || 98.25 || per second
|-
! style="text-align: left;" | Total Light oil output
| 15 || 88.725 || 127.725 || per second
|-
!colspan="5"|Light oil cracking
|-
! style="text-align: left;" | Light oil consumption
| 30 || 30 || 30 ||
|-
! style="text-align: left;" | Water consumption
| 30 || 30 || 30 ||
|-
! style="text-align: left;" | Crafting speed
| 2 || 2 || 2 || s / final item
|-
! style="text-align: left;" | Petroleum output
| 20 || 20 || 20 ||
|-
! style="text-align: left;" | Base machine crafting speed
| 1 || 1 || 1 || crafts / s
|-
! style="text-align: left;" | Crafting speed multiplier
| 100% || 455% || 655% ||
|-
! style="text-align: left;" | Output multiplier
| 100% || 130% || 130% || final items
|-
! style="text-align: left;" | Total Light oil consumption
| 15 || 68.25 || 98.25 || per second
|-
! style="text-align: left;" | Total Water consumption
| 15 || 68.25 || 98.25 || per second
|-
! style="text-align: left;" | Total Petroleum output
| 10 || 59.15 || 85.15 || per second
|-
!colspan="5"|Ratio
|-
! style="text-align: left;" | Heavy oil cracking
| 0.25 || 0.325 || 0.424 ||
|-
! style="text-align: left;" | Light oil cracking
| 0.85 || 1.2025 || 1.57 ||
|-
! style="text-align: left;" | Petroleum gas output
| 19.5 || 136.193 || 255.923 || per second
|-
|colspan="5" style="width: 600px; text-align: left;" | '''* Notes to table:''' ''Config 1'' is 3 Productivity modules 3 in each production building and 8 Beacons with 2 Speed modules 3 each in range of each production building. ''Config 2'' is 3 Productivity modules 3 in each production building and the highest achievable number of Beacons (16 for Refinery, 12 for Chemical plant) with 2 Speed modules 3 each in range of each prod. building.
|}

For config 2 in the above (possibly collapsed) table, a good enough ratio is 7:3:11, and the next ratio that is better is 165:70:259. The optimal ratio involves over 50000 refineries, and so is practically useless. But, for reference, it's 52400:22230:82251.

== History ==
{{history|0.17.60|
* Basic oil processing produces only petroleum gas.}}

{{history|0.17.0|
* Coal liquefaction now produces 90 heavy oil, 20 light oil and 10 petroleum gas, consuming 25 heavy oil, 10 coal and 50 steam.}}

{{history|0.15.0|
* Added coal liquefaction oil processing recipe.}}

{{history|0.9.1|
* Added heavy oil cracking and light oil cracking.}}

{{history|0.9.0|
* Introduced
**Basic oil processing
**Advanced oil processing}}

== See also ==
* [[Fluid system]]
* [[Crude oil]]
* [[Barrel]]

{{C|Main}}

Talk:Spoilage

2024-11-10T03:00:49Z

Thoxo: Created page with "== Freshness calculation == Can someone please confirm if the freshness of a product of two spoilable ingredients is just the average of the ingredients? -- ~~~~"

== Freshness calculation ==
Can someone please confirm if the freshness of a product of two spoilable ingredients is just the average of the ingredients? -- [[User:Thoxo|Thoxo]] ([[User talk:Thoxo|talk]]) 03:00, 10 November 2024 (UTC)

Spoilage

2024-11-10T02:55:28Z

Thoxo: /* Spoilage Mechanics */ Corrected wrong equation for calculating spoilage of item created from multiple ingredients

{{Languages}}
{{:Infobox:Spoilage}}
{{Stub}}
{{About/Space age}}
'''Spoilage''' is generated by letting most spoilable items spoil. This often happens on [[Gleba]], but it can happen anywhere, notably with [[agricultural science pack|agricultural science packs]] or [[fish]].

Spoilage can be directly harvested from stingfrond, sunnycomb, hairy clubnub and other flora present in Gleba. In addition, [[recycler|recycling]] [[nutrients]] will behave as if the nutrients were made using the [[nutrients from spoilage]] recipe, thereby yielding conciderably more spoilage than simply allowing the nutrients to spoil naturally.

== Alternative recipes ==
{|class = "wikitable"
! Recipe !! Ingredients !! Result !! Produced by !! Crafted only on
|-
| {{Icon|Iron bacteria}} || {{Icon|Time|1}} + {{Icon|Jelly|6}} || {{Icon|Iron bacteria|10%}} + {{Icon|Spoilage|4}} || {{Icon|Biochamber}} {{Icon|Assembling machine 2}} {{Icon|Assembling machine 3}} {{Icon|Player}} || {{Icon|Gleba}}
|-
| {{Icon|Copper bacteria}} || {{Icon|Time|1}} + {{Icon|Yumako mash|3}} || {{Icon|Copper bacteria|10%}} + {{Icon|Spoilage|1}} || {{Icon|Biochamber}} {{Icon|Assembling machine 2}} {{Icon|Assembling machine 3}} {{Icon|Player}} || {{Icon|Gleba}}
|}

== Spoilage Mechanics ==
Most biological products on Gleba are "spoilable". A spoilable item has an inherent timer attached to it, which begins at the item's creation. When the timer reaches 0, the item is transformed into [[spoilage]]{{SA}}, with a few exceptions. This process is inevitable and cannot be stopped.

The exact time differs per item, ranging anywhere from a few minutes to 2 hours. This means that item throughput is more important than ever on Gleba, and buffering a large stockpile is ineffective, as items can spoil within containers.

When crafting with spoilable items, the final product will inherit the freshness value of the ingredients. The three exceptions are [[Iron Bacteria|iron]] and [[copper bacteria]] cultivation, [[pentapod eggs]] and [[fish]] breeding, whose recipes will always result in a 100% fresh product, regardless of the freshness of the ingredients.

When crafting with two different spoilable items of different freshness values, like in the [[agricultural science pack]]{{SA}} and [[bioflux]]{{SA}} recipes, the final product's freshness is determined by the average of the ingredients' freshness.

The agricultural science pack does spoil, which will gradually decrease its research value, so the player is incentivized to build a fast space platform to bring them back to Nauvis.

Spoilable items are used as ingredients in a few non-spoilable items, such as the [[biochamber]]{{SA}}. In these, the freshness value of the ingredients do not matter in the product being produced.

{| class="wikitable"
|+ Spoilable Item Times
|-
! Item !! Time !! Special effect on spoiling
|-
| {{imagelink|Agricultural science pack|space-age=yes}} || 1 hour ||
|-
| {{imagelink|Biter egg|space-age=yes}} || 30 minute || Spawns a Big Biter
|-
| {{imagelink|Bioflux|space-age=yes}} || 2 hours ||
|-
| {{imagelink|Copper bacteria|space-age=yes}} || 1 minute || Turns into [[copper ore]]
|-
| {{imagelink|Raw fish}} || 2 hours, 5 minutes, 50 seconds ||
|-
| {{imagelink|Iron bacteria|space-age=yes}} || 1 minute || Turns into [[iron ore]]
|-
| {{imagelink|Jelly|space-age=yes}} || 4 minutes ||
|-
| {{imagelink|Jellynut|space-age=yes}} || 1 hour ||
|-
| {{imagelink|Nutrients|space-age=yes}} || 5 minutes ||
|-
| {{imagelink|Pentapod egg|space-age=yes}} || 15 minutes || Spawns a wriggler
|-
| {{imagelink|Yumako|space-age=yes}} || 1 hour ||
|-
| {{imagelink|Yumako mash|space-age=yes}} || 3 minutes ||
|-
|}

== History ==
{{History|2.0.7|
* Introduced in [[Space Age]]{{SA}} expansion.
}}

== See also ==
* [[Gleba]]{{SA}}

{{IntermediateNav}}

Console

2024-10-30T17:23:44Z

Thoxo: /* Teleport player */ Added in teleporting to a different surface

{{Languages}}
The '''console''' is Factorio's in-game command-line interface. See [[command line parameters]] for the command line interface of the Factorio executable.

The in-game console can be used for:

* Chatting with other players
* Occasional status updates
* Running commands / scripts / cheats

There are three types of commands:

* '''[[#Normal commands|Normal]]''' - Display information about the game and customize your experience.
* '''[[#Multiplayer commands|Multiplayer]]''' - Message filtering, banning users, etc.
* '''[[#Scripting and cheat commands|Scripting/Cheating]]''' - Run small Lua scripts (but they disable achievements for the save game)

__TOC__

=== Using the console ===
The console display can be toggled with the {{Keybinding|grave}} key (<code>`</code>). This is the key located to the left of the <code>1</code> key, above <code>Tab</code>.

You can customize the keys via '''Settings menu → Controls → Toggle chat (and Lua console)'''.
When the console is open, you'll see a blinking cursor at the bottom of the screen; type your message or command and hit '''Return''' to send it (this will also close the console).
Documentation about message and command prefixes can be found further down this page.

The console supports [[rich text]] tags. These tags are useful for sharing blueprints, marking map locations in chat or adding icons to map markers and train stations. Ctrl + Alt-clicking the map or ground will automatically insert a GPS tag and post it into the console. Shift-clicking most things with the console open will insert a tag for that thing into the console.

When the console is closed, only the most recent messages/commands will be displayed, but they will gradually fade away (opening the console will immediately re-display all recent messages).
Note that by default, all executed commands are made visible to all users. The fade-out time can be changed via '''Settings menu → Interface → Chat message delay'''.

The console can be cleared with the '''/clear''' command.

Use the {{keybinding|↑}} and {{keybinding|↓}} keys to scroll through the console history. The {{keybinding|Tab}} key provides intelligent code completion on commands, options and player names.

== Normal commands ==

{| class="wikitable"
|-
! style="width:25%"| Command
! style="width:25%"| Example
! style="width:46%"| Description
! style="width:4%"| Admin only
|-
| /alerts <enable/disable/mute/unmute> <alert>
| /alerts disable turret_fire
| Enables, disables, mutes, or unmutes the given [[alerts|alert]] type. Available alerts: entity_destroyed, entity_under_attack, not_enough_construction_robots, no_material_for_construction, not_enough_repair packs, turret_fire, custom, no_storage, train_out_of_fuel, fluid_mixing.
| No
|-
| /clear
| /clear
| Clears the console.
| No
|-
| /color <color>
| /color 20 255 255
| Changes your color. Can either be one of the pre-defined colors or [[:Wikipedia:RGB_color_space|RGB value]] in the format of “# # #”. Available colors: default, red, green, blue, orange, yellow, pink, purple, white, black, gray, brown, cyan, acid.
| No
|-
| /enable-research-queue
| /enable-research-queue
| Enables the [[research]] queue.
| Yes
|-
| /evolution
| /evolution
| Prints info about the alien evolution factor.
| No
|-
| /help [command]
| /help
| Prints a list of available commands, the optional argument can specify the command that should be described.
| No
|-
| /h [command]
| /h
| Same as /help.
| No
|-
| /mute-programmable-speaker <mute/unmute> <local/everyone>
| /mute-programmable-speaker mute local
| Mutes or unmutes the global sounds created by the Programmable Speaker. Use “local” to mute just the local client. Admins can use “everyone” to mute the sounds for everyone on the server.
| No
|-
| /perf-avg-frames <number>
| /perf-avg-frames 100
| Number of ticks/updates used to average performance counters. Default is 100. Value of 5-10 is recommended for fast convergence, but numbers will jitter more rapidly.
| No
|-
| /permissions
| /permissions
| Opens the [[permissions]] GUI.
| Yes
|-
| /permissions <action> <parameters>
| /permissions add-player DeveloperGroup kovarex
| Available actions are add-player <group> <player>, create-group <name>, delete-group <group>, edit-group <group> <input_action> <true/false>, get-player-group <player>, remove-player <group> <player>, rename-group <group> <new_name> and reset
| Yes
|-
| /reset-tips
| /reset-tips
| Resets the state of the tips and tricks as if the game was just started for the first time.
| No
|-
| /screenshot [x resolution] [y resolution] [zoom]
| /screenshot
| Takes a screenshot with the GUI hidden, centered on the player. It is saved in the "script-output" subfolder of your [[User data directory]]. Resolution is optional and defaults to the current window size. Zoom is optional and defaults to 1.
| No
|-
| /seed
| /seed
| Prints the starting map seed.
| No
|-
| /time
| /time
| Prints info about how old the map is.
| No
|-
| /toggle-action-logging
| /toggle-action-logging
| Toggles logging all input actions performed by the game. This value isn’t persisted between game restarts and only affects your local game in multiplayer sessions.
| Yes
|-
| /toggle-heavy-mode
| /toggle-heavy-mode
| Used to investigate [[Desynchronization#Using_heavy_mode_command|desyncs]]. Will slow down the game and make multiplayer unplayable.
| Yes
|-
| /unlock-shortcut-bar
| /unlock-shortcut-bar
| Unlocks all [[shortcut bar]] items, including blueprint string import, copy & paste, deconstruction and upgrade planner.
| No
|-
| /unlock-tips
| /unlock-tips
| Unlocks all tips and tricks entries.
| No
|-
| /version
| /version
| Prints the current game version.
| No
|-
|}

== Multiplayer commands ==
{| class="wikitable"
|-
! style="width:25%"| Command
! style="width:25%"| Example
! style="width:46%"| Description
! style="width:4%"| Admin only
|-
| <message>
| Hello team!
| Console input that does not start with {{keybinding|/}} is shown as a chat message to your team.
| No
|-
| /admin
| /admin
| Opens the player management GUI.
| Yes
|-
| /admins
| /admins
| Prints a list of game admins.
| No
|-
| /ban <player> <reason>
| /ban xTROLLx Throwing grenades in base
| Bans the specified player.
| Yes
|-
| /bans
| /bans
| Prints a list of banned players.
| No
|-
| /banlist <add/remove/get/clear> <player>
| /banlist get
| Adds or removes a player from the banlist. Same as /ban or /unban.
| No
|-
| /config
| /config
| Opens the server configuration GUI.
| Yes
|-
| /config <get/set> <option> <value>
| /config set password hunter2
| Gets or sets various multiplayer game settings. Available configs are: afk-auto-kick, allow-commands, allow-debug-settings, autosave-interval, autosave-only-on-server, ignore-player-limit-for-returning-players, max-players, max-upload-speed, only-admins-can-pause, password, require-user-verification, visibility-lan, visibility-public. The units for the options afk-auto-kick and autosave-interval are in minutes.
| Yes
|-
| /delete-blueprint-library <player>
| /delete-blueprint-library everybody confirm
| Deletes the blueprint library storage for the given offline player from the save file. Enter “everybody confirm” to delete the storage of all offline players.
| Yes
|-
| /demote <player>
| /demote AzureDiamond
| Demotes the player from admin.
| Yes
|-
| /ignore <player>
| /ignore Cthon98
| Prevents the chat from showing messages from this player. Admin messages are still shown.
| No
|-
| /ignores
| /ignores
| Prints a list of ignored players.
| No
|-
| /kick <player> <reason>
| /kick xTROLLx Throwing grenades in base
| Kicks the specified player.
| Yes
|-
| /mute <player>
| /mute Cthon98
| Prevents the player from saying anything in chat.
| Yes
|-
| /mutes
| /mutes
| All players that are muted (can’t talk in chat).
| No
|-
| /open <player>
| /open AzureDiamond
| Opens another player’s inventory.
| Yes
|-
| /o <player>
| /o AzureDiamond
| Same as /open.
| Yes
|-
| /players [online/o/count/c]
| /players
| Prints a list of players in the game. (parameter online/o, it prints only players that are online, count/c prints only count)
| No
|-
| /p [online/o/count/c]
| /p o c
| Same as /players.
| No
|-
| /promote <player>
| /promote AzureDiamond
| Promotes the player to admin.
| Yes
|-
| /purge <player>
| /purge Cthon98
| Clears all the messages from this player from the chat log.
| Yes
|-
| /reply <message>
| /reply oh, really?
| Replies to the last player that whispered to you.
| No
|-
| /r <message>
| /r oh, really?
| Same as /reply.
| No
|-
| /server-save
| /server-save
| Saves the game on the server in a multiplayer game.
| Yes
|-
| /shout <message>
| /shout Hello world!
| Sends a message to all players including other forces.
| No
|-
| /s <message>
| /s Hello world!
| Same as /shout.
| No
|-
| /swap-players <player> [player]
| /swap-players AzureDiamond
| Swaps your character with the given player’s character, or if two players are given swaps the two player characters.
| Yes
|-
| /unban <player>
| /unban xTROLLx
| Unbans the specified player.
| Yes
|-
| /unignore <player>
| /unignore Cthon98
| Allows the chat to show messages from this player.
| No
|-
| /unmute <player>
| /unmute Cthon98
| Allows the player to talk in chat again.
| Yes
|-
| /whisper <player> <message>
| /whisper AzureDiamond that's what I see
| Sends a message to the specified player.
| No
|-
| /w <player> <message>
| /w AzureDiamond that's what I see
| Same as /whisper.
| No
|-
| /whitelist <add/remove/get/clear> [player]
| /whitelist get
| Adds or removes a player from the whitelist, where only whitelisted players can join the game. Enter nothing for “player” when using “get” to print a list of all whitelisted players. An empty whitelist disables the whitelist functionality allowing anyone to join.
| No
|}

== Scripting and cheat commands ==
{| class="wikitable"
|-
! Command
! Description
|-
| /cheat <all>
| Researches all technologies and enables cheat mode. Using the '''all''' option also gives the player some additional items.
|-
| /command <command>
| Executes a Lua command (if allowed).
|-
| /c <command>
| Executes a Lua command (if allowed).
|-
| /editor
| Toggles the map editor.
|-
| /measured-command <command>
| Executes a Lua command (if allowed) and measures time it took.
|-
| /mc <command>
| Executes a Lua command (if allowed) and measures time it took.
|-
| /silent-command <command>
| Executes a Lua command (if allowed) without printing it to the console.
|-
| /sc <command>
| Executes a Lua command (if allowed) without printing it to the console.
|}

This is a very powerful feature, which also allows cheating, and as such achievements will be permanently disabled for the save as soon as you use a script command.

== Basic example scripts ==

=== Use it as calculator ===
<syntaxhighlight lang="lua">
/c game.player.print(1234*5678)
</syntaxhighlight>

=== Zoom beyond normal bounds ===
Note that zooming too far out can cause performance hits. Be careful.
<syntaxhighlight lang="lua">
/c game.player.zoom=0.1
</syntaxhighlight>

=== Mine faster ===
<syntaxhighlight lang="lua">
/c game.player.force.manual_mining_speed_modifier=1000
</syntaxhighlight>

=== Craft faster ===
<syntaxhighlight lang="lua">
/c game.player.force.manual_crafting_speed_modifier=1000
</syntaxhighlight>

=== Unlock and research all technologies ===
<syntaxhighlight lang="lua">
/c game.player.force.research_all_technologies()
</syntaxhighlight>

Undo this with the command in the next section.

Note: Specific technologies can be researched using the [[map editor]] by shift clicking the "start research" button on the technology GUI.

=== Unresearch all technologies ===
This does not reset manually applied bonuses
<syntaxhighlight lang="lua">
/c for _, tech in pairs(game.player.force.technologies) do
tech.researched=false
end
</syntaxhighlight>

Note: Specific technologies can be unresearched using the [[map editor]] by clicking the "un-research" button on the technology GUI.

=== Reset your force ===
This resets all data for your force, including kill and production statistics, technologies, bonuses and charting status.
<syntaxhighlight lang="lua">
/c game.player.force.reset()
</syntaxhighlight>

=== Always show rail block visualization ===
Permanently show the rail block visualization instead of only when holding a rail signal. Disable by replacing true with false.

<syntaxhighlight lang="lua">
/c game.player.game_view_settings.show_rail_block_visualisation = true
</syntaxhighlight>

=== Set all trains to Automatic mode ===
Set all trains to automatic mode - for example after building them with a blueprint.

<syntaxhighlight lang="lua">
/c for key,ent in pairs (game.player.surface.find_entities_filtered{name="locomotive"}) do
ent.train.manual_mode = false
end
</syntaxhighlight>

== Inventory manipulation scripts ==

=== Cheat mode ===
Allows for infinite free crafting. Disable by replacing true with false.
<syntaxhighlight lang="lua">
/c game.player.cheat_mode=true
</syntaxhighlight>

=== Refill resources (refill oil, iron etc.) ===
While holding the cursor over a resource tile in-game:
<syntaxhighlight lang="lua">
/c game.player.selected.amount=7500
</syntaxhighlight>

Alternatively you can refill all resources in the map with the following command. Change ore.amount to the desired value.
<syntaxhighlight lang="lua">
/c surface = game.player.surface
for _, ore in pairs(surface.find_entities_filtered({type="resource"})) do
ore.amount = 10000
end
</syntaxhighlight>

=== Add items to the player's inventory ===
Replace iron-plate with the [[data.raw|internal name]] of the item desired.
<syntaxhighlight lang="lua">
/c game.player.insert{name="iron-plate", count=100}
</syntaxhighlight>

For instance, here's a stack of the god-mode energy system interface:
<syntaxhighlight lang="lua">
/c game.player.insert{name="electric-energy-interface"}
</syntaxhighlight>

There are several god-mode items available:

* <code>infinity-chest</code>
* <code>infinity-pipe</code>
* <code>electric-energy-interface</code>
* <code>heat-interface</code>

Add a powerful armor with equipment and some tools for construction:
<syntaxhighlight lang="lua">
/c local player = game.player
player.insert{name="power-armor-mk2", count = 1}
local p_armor = player.get_inventory(5)[1].grid
p_armor.put({name = "fusion-reactor-equipment"})
p_armor.put({name = "fusion-reactor-equipment"})
p_armor.put({name = "fusion-reactor-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "exoskeleton-equipment"})
p_armor.put({name = "energy-shield-mk2-equipment"})
p_armor.put({name = "energy-shield-mk2-equipment"})
p_armor.put({name = "personal-roboport-mk2-equipment"})
p_armor.put({name = "night-vision-equipment"})
p_armor.put({name = "battery-mk2-equipment"})
p_armor.put({name = "battery-mk2-equipment"})
player.insert{name="construction-robot", count = 25}
</syntaxhighlight>

=== Increase player inventory slots ===
Gives 100 additional bonus inventory slots to your entire force. Used by the [[Toolbelt (research)]].
<syntaxhighlight lang="lua">
/c game.player.force.character_inventory_slots_bonus=100
</syntaxhighlight>

== World manipulation scripts ==

=== Reveal the map around the player ===

Reveals the map around the player, similar to a [[radar]].
<syntaxhighlight lang="lua">
/c local radius=150
game.player.force.chart(game.player.surface, {{game.player.position.x-radius, game.player.position.y-radius}, {game.player.position.x+radius, game.player.position.y+radius}})
</syntaxhighlight>
or from start position
<syntaxhighlight lang="lua">
/c local radius=150
game.player.force.chart(game.player.surface, {{x = -radius, y = -radius}, {x = radius, y = radius}})
</syntaxhighlight>
Change 150 to the desired radius, higher values take longer.

=== Hide revealed map ===

Hides all revealed chunks, inverted map revealing.
<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local force = game.player.force
for chunk in surface.get_chunks() do
force.unchart_chunk({x = chunk.x, y = chunk.y}, surface)
end
</syntaxhighlight>

=== Reveal all generated map ===

Revels all of the generated map to the player's team.
<syntaxhighlight lang="lua">
/c game.player.force.chart_all()
</syntaxhighlight>

=== Delete chunks ===
If much of the map is revealed, it increases the size of the save file. The following command cancels the generation of all chunks that are currently queued for generation and removes chunks outside a 32 chunks radius around 0,0. Note that this will remove player entities if there are any on these chunks.
<syntaxhighlight lang="lua">
/c local surface = game.player.surface;
game.player.force.cancel_charting(surface);
local chunk_radius = 32;
for chunk in surface.get_chunks() do
if (chunk.x < -chunk_radius or chunk.x > chunk_radius or chunk.y < -chunk_radius or chunk.y > chunk_radius) then
surface.delete_chunk(chunk)
end
end
</syntaxhighlight>

=== Delete unrevealed chunks ===
This command deletes chunks that are not revealed by the player. Can be used after the command for [[#Hide revealed map|hiding revealed map]] to delete the chunks not covered by radar.

<syntaxhighlight lang="lua">/c local surface = game.player.surface
local force = game.player.force
for chunk in surface.get_chunks() do
if not force.is_chunk_charted(surface, chunk) then
surface.delete_chunk(chunk)
end
end</syntaxhighlight>

=== Turn off night ===
Enables eternal day.
<syntaxhighlight lang="lua">
/c game.player.surface.always_day=true
</syntaxhighlight>

=== Change game speed ===
0.5 is half speed, 1 is default, 2 is double speed, etc. Minimum is 0.01. This can be used for a lot of things like when you know you will have to wait for long periods of time for something to complete. Increasing will decrease performance, be careful.
<syntaxhighlight lang="lua">
/c game.speed=X
</syntaxhighlight>

=== Freeze time ===
Stops the advancement of the time. Unfreezes it if you by replace "true" with "false".
<syntaxhighlight lang="lua">
/c game.player.surface.freeze_daytime=true
</syntaxhighlight>

=== Remove all pollution ===
<syntaxhighlight lang="lua">
/c game.player.surface.clear_pollution()
</syntaxhighlight>

=== Completely turn off pollution ===

<syntaxhighlight lang="lua">
/c for _, surface in pairs(game.surfaces) do
surface.clear_pollution()
end
game.map_settings.pollution.enabled = false
</syntaxhighlight>

=== Add a lot of pollution ===
<syntaxhighlight lang="lua">
/c game.player.surface.pollute(game.player.position, 1000000)
</syntaxhighlight>

=== Where speakers are, who placed them ===
<syntaxhighlight lang="lua">
/c local speakers = game.player.surface.find_entities_filtered{force = game.player.force, type="programmable-speaker"}
for key, speaker in pairs(speakers) do
game.player.print(speaker.last_user.name .. " placed a speaker at " .. speaker.gps_tag)
end
</syntaxhighlight>

=== Disable friendly fire for your force ===
<syntaxhighlight lang="lua">
/c game.player.force.friendly_fire = false
</syntaxhighlight>

=== Add new resource patch ===
This creates a new 11×11 patch of resources, centered on the player character, where the ground is not water.
The patch it creates is perfectly square but it randomizes the amount similar to natural generation, with fewer ore at the edges and more ore in the center.
The default numbers result in a patch with 2500-3000 ore.

If you want a larger patch, change "local size = 5" to a larger number.
A larger patch will have exponentially more ore.
Entering a number above 30 is not recommended.

If you want a richer patch, change "local density = 10" to a larger number.
Entering a very large number shouldn't hurt anything but you probably don't need to go above 100.

To choose which resource is spawned, change "stone" near the bottom to "iron-ore", "copper-ore", "coal", or "uranium-ore".

<syntaxhighlight lang="lua">
/c local surface=game.player.surface
local ore=nil
local size=5
local density=10
for y=-size, size do
for x=-size, size do
a=(size+1-math.abs(x))*10
b=(size+1-math.abs(y))*10
if a<b then
ore=math.random(a*density-a*(density-8), a*density+a*(density-8))
end
if b<a then
ore=math.random(b*density-b*(density-8), b*density+b*(density-8))
end
if surface.get_tile(game.player.position.x+x, game.player.position.y+y).collides_with("ground-tile") then
surface.create_entity({name="stone", amount=ore, position={game.player.position.x+x, game.player.position.y+y}})
end
end
end
</syntaxhighlight>

For more flexibility, the [[map editor]] can also be used to create/alter/remove resource patches.

=== Remove resources around the player ===
Removes all resource patches from the ground in a 50 x 50 area around the player.

<syntaxhighlight lang="lua">
/c local surface=game.player.surface
local size=50
local pos=game.player.position

for _, e in pairs(surface.find_entities_filtered{area={{pos.x-size, pos.y-size},{pos.x+size, pos.y+size}}, type="resource"})
do e.destroy()
end
</syntaxhighlight>

=== Add new oil patch ===
This creates 9 crude oil patches in a 3×3 square.
<syntaxhighlight lang="lua">
/c for y=0,2 do
for x=0,2 do
game.player.surface.create_entity({name="crude-oil", amount=100000, position={game.player.position.x+x*7-7, game.player.position.y+y*7-7}})
end
end
</syntaxhighlight>

or randomly without any collision:
<syntaxhighlight lang="lua">
/c local position=nil
for i=1,9 do
position=game.player.surface.find_non_colliding_position("crude-oil", game.player.position, 0, i/2+1.5)
if position then
game.player.surface.create_entity({name="crude-oil", amount=100000, position=position})
end
end
</syntaxhighlight>

=== Regenerate resources ===
For solid resources like iron, destroys all resource entities and creates resource entities as in the original map generation. For fluid resources like oil, sets the yield of all existing resource entities to the original amount. Regenerates resources on the entire surface.
<syntaxhighlight lang="lua">
/c local surface = game.player.surface
for _, e in pairs(surface.find_entities_filtered{type="resource"}) do
if e.prototype.infinite_resource then
e.amount = e.initial_amount
else
e.destroy()
end
end
local non_infinites = {}
for resource, prototype in pairs(game.get_filtered_entity_prototypes{{filter="type", type="resource"}}) do
if not prototype.infinite_resource then
table.insert(non_infinites, resource)
end
end
surface.regenerate_entity(non_infinites)
for _, e in pairs(surface.find_entities_filtered{type="mining-drill"}) do
e.update_connections()
end
</syntaxhighlight>

=== Count entities ===
Counts all entities whose name includes the string in local entity.
<syntaxhighlight lang="lua">
/c local entity="belt"
local surface=game.player.surface
local count=0
for key, ent in pairs(surface.find_entities_filtered({force=game.player.force})) do
if string.find(ent.name,entity) then
count=count+1
end
end
game.player.print(count)
</syntaxhighlight>

=== Turn off cliff generation ===
Sets size to "none". Only effective on chunks that are generated after using this command. Use [[#Remove all cliffs]] to delete existing cliffs.

<syntaxhighlight lang="lua">
/c local mgs = game.player.surface.map_gen_settings
mgs.cliff_settings.cliff_elevation_0 = 1024
game.player.surface.map_gen_settings = mgs</syntaxhighlight>

=== Remove all cliffs ===
Removes all cliffs existing cliffs from the world. Use [[#Turn off cliff generation]] to turn off cliff generation in new chunks.

<syntaxhighlight lang="lua">
/c for _, v in pairs(game.player.surface.find_entities_filtered{type="cliff"}) do
v.destroy()
end</syntaxhighlight>

=== Delete all decoratives ===
Delete the decoratives that can be found in the world.

<syntaxhighlight lang="lua">
/c game.player.surface.destroy_decoratives({})</syntaxhighlight>

=== Change map generation settings ===
This allows to change the map generation settings for new chunks; it does not alter already generated chunks. [[#Delete chunks|Deleted chunks]] are affected by the setting change because they are newly generated when they get explored again.

To change resource generation settings, replace "iron-ore" with the [[Data.raw#resource|resource]] that should be changed and replace "very-high" with the desired [https://lua-api.factorio.com/latest/Concepts.html#MapGenSize MapGenSize] in the following command. Replace "iron-ore" with "enemy-base" to change the enemy base generation settings.

<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local resource = "iron-ore"
local mgs = surface.map_gen_settings
mgs.autoplace_controls[resource].size = "very-high"
mgs.autoplace_controls[resource].frequency = "very-high"
mgs.autoplace_controls[resource].richness = "very-high"
surface.map_gen_settings = mgs</syntaxhighlight>

To change water generation settings, replace "very-high" with the desired [https://lua-api.factorio.com/latest/Concepts.html#MapGenSize MapGenSize] in the following command.

<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local mgs = surface.map_gen_settings
mgs.water = "very-high" --[[ size]]
mgs.terrain_segmentation = "very-high" --[[ frequency]]
surface.map_gen_settings = mgs </syntaxhighlight>

=== Making a structure indestructible ===
This makes it impossible for an entity to be damaged or killed, e.g. by biters. Hover over the entity and then run:
<syntaxhighlight lang="lua">
/c game.player.selected.destructible = false
</syntaxhighlight>

=== Connect linked belts ===
If there exist at least two [https://lua-api.factorio.com/latest/prototypes/LinkedBeltPrototype.html linked belts], and one of them has the "Entity tag" <code>in</code>, and another linked belt has the "Entity tag" <code>out</code>, then the following command should link these two linked belts.

<syntaxhighlight lang="lua">
/c local i = game.get_entity_by_tag('in')
local o = game.get_entity_by_tag('out')
i.linked_belt_type = 'input'
o.linked_belt_type = 'output'
i.connect_linked_belts(o)
</syntaxhighlight>

== Enemy/evolution scripts ==

=== Set evolution factor ===
Ranges from 0 (new game) to 1.
<syntaxhighlight lang="lua">
/c game.forces["enemy"].set_evolution_factor(X, game.player.surface)
</syntaxhighlight>

=== Disable time-based evolution & increases pollution-based evolution ===
<syntaxhighlight lang="lua">
/c game.map_settings.enemy_evolution.time_factor=0
/c game.map_settings.enemy_evolution.pollution_factor=game.map_settings.enemy_evolution.pollution_factor*2
</syntaxhighlight>

The "2" at the end of the last command will double the default pollution factor. You can substitute another number to increase (or decrease) the pollution factor further.

=== Kill all biters on the "enemy" force ===
Note that this will kill only mobile units, spawners will not be killed.
<syntaxhighlight lang="lua">
/c game.forces["enemy"].kill_all_units()
</syntaxhighlight>

=== Kill all enemies ===
This will kill all biters, bases and worms. Anything that is an enemy will be completely destroyed. This only affects enemies in the generated world, so any unexplored parts of the map which still need to be generated will still have enemies. You can [[#Prevent biters being on newly generated chunks|prevent biters being on newly generated chunks]] if desired.
<syntaxhighlight lang="lua">
/c local surface=game.player.surface
for key, entity in pairs(surface.find_entities_filtered({force="enemy"})) do
entity.destroy()
end
</syntaxhighlight>

=== Kill all nearby enemies ===

This will kill all biters, bases and worms in a configurable radius. The default, 250 tiles, is about two zoomed-out screen widths on full HD. After destruction, it shows how many objects were destroyed.

<syntaxhighlight lang="lua">
/c local surface=game.player.surface
local pp = game.player.position
local cnt = 0
for key, entity in pairs(surface.find_entities_filtered({force="enemy", radius=250, position=pp })) do
cnt = cnt+1
entity.destroy()
end
game.player.print(cnt)
</syntaxhighlight>

=== Enable/Disable peaceful mode ===
Enabling peaceful mode prevents biter attacks until provoked. Substitute true for false to disable. Already existing biters are not affected by this command so attacks could continue for a while after activating peaceful mode.
<syntaxhighlight lang="lua">
/c game.player.surface.peaceful_mode = true
</syntaxhighlight>

=== Enable/Disable biter expansion ===
Biter expansion allows biters to create new nests, it is enabled by default. Substitute true for false to disable.
<syntaxhighlight lang="lua">
/c game.map_settings.enemy_expansion.enabled = true
</syntaxhighlight>

=== Prevent biters being on newly generated chunks ===
On newly generated chunks no biters will be present, however all current biters will remain unaffected. Equivalent of setting the Enemy Base Size to None under the Terrain settings during map generation but achieved mid game by [[#Change map generation settings|changing map generation settings]].
<syntaxhighlight lang="lua">
/c local surface = game.player.surface
local mgs = surface.map_gen_settings
mgs.autoplace_controls["enemy-base"].size = "none"
surface.map_gen_settings = mgs
</syntaxhighlight>

Instead of the command, it is also possible to use a GUI in the [[map editor]] to changing map generation settings mid game. Access the map editor with <code>/editor</code>, go to the "Surfaces" tab and click "Edit map gen settings".

== Player character scripts ==
Commands concerning the player directly.
=== Get player position ===
Prints coordinates of your current position.
<syntaxhighlight lang="lua">
/c game.player.print(game.player.position)
</syntaxhighlight>

=== Teleport player ===
Moves the player to the specified location. You should be able to teleport to a specific player if you obtain their coordinates via them executing the previous command and giving them to you.
<syntaxhighlight lang="lua">
/c game.player.teleport({X, Y})
</syntaxhighlight>

To teleport to the world's origin, use 0,0.

To teleport to a different planet / surface, use:
<syntaxhighlight lang="lua">
/c game.player.teleport({X, Y}, 'surface_name')
</syntaxhighlight>

=== Enable god mode ===
God mode removes your player character allowing you to fly over obstacles and take no damage.

Disassociate your controls from the character and destroy it:
<syntaxhighlight lang="lua">
/c game.player.character.destroy()
</syntaxhighlight>

To undo, spawn a player character. This will spawn a new character at the spawn point of the world, and connect your controls to it.
<syntaxhighlight lang="lua">
/c game.player.create_character()
</syntaxhighlight>

=== Enable long reach ===
Enables long reach, which allows the player to build and interact with entities at a greater distance. The default reach is 10.
<syntaxhighlight lang="lua">
/c local reach = 10000
game.player.force.character_build_distance_bonus = reach
game.player.force.character_reach_distance_bonus = reach
</syntaxhighlight>

=== Find player corpses ===
Pings player corpses on the map.
<syntaxhighlight lang="lua">
/c local found_corpses = game.player.surface.find_entities_filtered{type="character-corpse"}
for _,corpse in pairs(found_corpses) do
local player = game.get_player(corpse.character_corpse_player_index)
local name = player and player.name or "????"
game.player.print(name .. " --> " .. corpse.gps_tag)
end
</syntaxhighlight>

=== Run faster ===
<syntaxhighlight lang="lua">
/c game.player.character_running_speed_modifier=3
</syntaxhighlight>

== Research scripts ==
=== Enable faster research ===
<syntaxhighlight lang="lua">
/c game.player.force.laboratory_speed_modifier=1
</syntaxhighlight>
-0.5 is half speed, 0 is normal speed, 1 is double speed, 2 is triple etc.

=== Research specific technologies ===
The internal technology names can be found in the infoboxes on their respective pages.
<syntaxhighlight lang="lua">
/c game.player.force.technologies['electric-energy-distribution-1'].researched=true
/c game.player.force.technologies['steel-processing'].researched=true
</syntaxhighlight>

To research a high level of an infinite technology, set its level:
<syntaxhighlight lang="lua">
/c game.player.force.technologies['worker-robots-speed-6'].level = 100
/c game.player.force.technologies['mining-productivity-4'].level = 100
</syntaxhighlight>

=== Unresearch specific technologies ===
The internal technology names can be found in the infoboxes on their respective pages.
<syntaxhighlight lang="lua">
/c game.player.force.technologies['electric-energy-distribution-1'].researched=false
/c game.player.force.technologies['steel-processing'].researched=false
</syntaxhighlight>

=== Enabling specific recipes ===
The internal recipe/item names can be found in the infoboxes on their respective pages.
<syntaxhighlight lang="lua">
/c game.player.force.recipes["electric-energy-interface"].enabled=true
/c game.player.force.recipes["rocket-silo"].enabled=true
/c game.player.force.recipes.loader.enabled=true
/c game.player.force.recipes["fast-loader"].enabled = true
/c game.player.force.recipes["express-loader"].enabled = true
</syntaxhighlight>

=== Enable all recipes ===
<syntaxhighlight lang="lua">
/c for name, recipe in pairs(game.player.force.recipes) do recipe.enabled = true end
</syntaxhighlight>

=== Resetting technology effects to default ===
This will reset the enabled/unlocked state of all recipes to what they would be purely based on the currently researched technologies, as well as resetting other technology effects like mining speed, etc. Any manual modifications to these effects and recipe unlocks will be undone.
<syntaxhighlight lang="lua">
/c game.player.force.reset_technology_effects()
</syntaxhighlight>
Note: Can be used as a quick workaround when recipes are unavailable after adding or changing mods even though the technology unlocking them has already been researched.

== Modding tools ==
A list of the internal names of most things in the vanilla game can also be found on [[data.raw]].

=== Access a mod's data ===
If the first word of the command is __mod-name__ it will run in the context of the mod with the same name. For instance, this command prints the data from the Even Distribution mod:
<syntaxhighlight lang="lua">
/c __even-distribution__ game.player.print(serpent.dump(global))
</syntaxhighlight>

=== Print to console the tile under the player ===
<syntaxhighlight lang="lua">
/c game.player.print(game.player.surface.get_tile(game.player.position).name)
</syntaxhighlight>

=== Write all researched technologies to file ===
<syntaxhighlight lang="lua">
/c local list = {}
for _, tech in pairs(game.player.force.technologies) do
if tech.researched then
list[#list+1] = tech.name
end
end
game.write_file("techs.lua", serpent.block(list) .. "\n", true)
</syntaxhighlight>

=== Write all enabled recipes to file ===
<syntaxhighlight lang="lua">
/c local list = {}
for _, recipe in pairs(game.player.force.recipes) do
if recipe.enabled then
list[#list+1] = recipe.name
end
end
game.write_file("recipes.lua", serpent.block(list) .. "\n", true)
</syntaxhighlight>

=== Write mod list to file ===
Write all currently active mods and their version to the file script-output/mods.txt in the [[user data directory]].

<syntaxhighlight lang="lua">
/c game.write_file("mods.txt", serpent.block(game.active_mods))
</syntaxhighlight>

== History ==
{{History|1.1.92|
* Added a notification when a technology is researched.
* Added /enable-research-queue console command to enable the research queue without disabling achievements.}}

== See also ==
* [[Command line parameters]]
* https://lua-api.factorio.com/latest/index-runtime.html - Factorio API reference for latest version

{{C|Modding}}

Blueprint string format

2024-10-29T00:09:59Z

Thoxo: /* Entity object */ Added note about direction changing with 2.0 blueprints

[[File:blueprint_string_preview.png|thumb|340px|right|Preview of a blueprint string.]]This is a technical description of the blueprint string format, used to share blueprints with other users.

A blueprint string is a JSON representation of the blueprint, compressed with zlib deflate using compression level 9 and then encoded using base64 with a version byte in front of the encoded string. The version byte is currently 0 (for all Factorio versions through 1.1).
So to get the JSON representation of a blueprint from a blueprint string, skip the first byte, base64 decode the string, and finally decompress using zlib inflate.

== Json representation of a blueprint/blueprint book ==

The json representation of a blueprint or blueprint book is one large object inside another "wrapping" object, its key inside that object is either blueprint or blueprint-book.

=== Blueprint book object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| item
| String, the name of the item that was saved ("blueprint-book" in vanilla).
| String
|-
| label
| String, the name of the blueprint set by the user.
| String
|-
| label_color
| The color of the label of this blueprint. Optional. [[#Color object]].
| Object
|-
| blueprints
| The actual content of the blueprint book, array of objects containing an "index" key and 0-based value and a "blueprint" key with a [[#Blueprint object]] as the value.
| Array
|-
| active_index
| Index of the currently selected blueprint, 0-based.
| Integer
|-
| icons
| The icons of the blueprint book set by the user, array of [[#Icon object]]s.
| Array
|-
| description
| The description of the blueprint book. Optional.
| String
|-
| version
| The map version of the map the blueprint was created in, see [[Version string format]].
| Integer (long)
|}

=== Blueprint object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| item
| String, the name of the item that was saved ("blueprint" in vanilla).
| String
|-
| label
| String, the name of the blueprint set by the user.
| String
|-
| label_color
| The color of the label of this blueprint. Optional. [[#Color object]].
| Object
|-
| entities
| The actual content of the blueprint, array of [[#Entity object]]s.
| Array
|-
| tiles
| The tiles included in the blueprint, array of [[#Tile object]]s.
| Array
|-
| icons
| The icons of the blueprint set by the user, array of [[#Icon object]]s.
| Array
|-
| schedules
| The schedules for trains in this blueprint, array of [[#Schedule object]]s.
| Array
|-
| description
| The description of the blueprint. Optional.
| String
|-
| snap-to-grid
| The dimensions of the grid to use for snapping. Optional. [[#Position object]].
| Object
|-
| absolute-snapping
| Whether the blueprint uses absolute or relative snapping. Optional.
| Boolean
|-
| position-relative-to-grid
| Offset relative to the global absolute snapping grid. Optional. [[#Position object]].
| Object
|-
| version
| The map version of the map the blueprint was created in.
| Integer (long)
|}

=== Icon object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| index
| Index of the icon, 1-based.
| Integer
|-
| signal
| The icon that is displayed, [[#SignalID object]].
| Object
|}

=== SignalID object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Name of the signal prototype this signal is set to.
| String
|-
| type
| Type of the signal. Either "item", "fluid" or "virtual". '''Note for 2.x:''' property appears to be optional
| String
|}

=== Entity object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| entity_number
| Index of the entity, 1-based.
| Integer
|-
| name
| Prototype name of the entity (e.g. "offshore-pump").
| String
|-
| position
| [[#Position object]], position of the entity within the blueprint.
| Object
|-
| direction
| Direction of the entity, uint (optional). '''Note for 2.x:''' Direction appears to be double the previous values
| Integer
|-
| orientation
| Orientation of cargo wagon or locomotive, value 0 to 1 (optional).
| Floating Point
|-
| connections
| Circuit connection, object with keys starting from 1, values are [[#Connection object]]s (optional).
| Object
|-
| neighbours
| Copper wire connections, array of entity_numbers (optional).
| Array
|-
| control_behavior
| [[#Control behavior object]] of this entity (optional).
| Object
|-
| items
| Item requests by this entity, this is what defines the item-request-proxy when the blueprint is placed, optional. [[#Item request object]]
| Object
|-
| recipe
| Name of the recipe prototype this assembling machine is set to, optional, string.
| String
|-
| bar
| Used by [[Prototype/Container]], optional. The index of the first inaccessible item slot due to limiting with the red "bar". 0-based [[Types/ItemStackIndex]].
| Integer
|-
| inventory
| Cargo wagon inventory configuration, optional. [[#Inventory object]]
| Object
|-
| infinity_settings
| Used by [[Prototype/InfinityContainer]], optional. [[#Infinity settings object]]
| Object
|-
| type
| Type of the underground belt or loader, optional. Either "input" or "output".
| String
|-
| input_priority
| Input priority of the splitter, optional. Either "right" or "left", "none" is omitted.
| String
|-
| output_priority
| Output priority of the splitter, optional. Either "right" or "left", "none" is omitted.
| String
|-
| filter
| Filter of the splitter, optional. Name of the item prototype the filter is set to, string.
| String
|-
| filters
| Filters of the filter inserter or loader, optional. Array of [[#Item filter object]]s.
| Array
|-
| filter_mode
| Filter mode of the filter inserter, optional. Either "whitelist" or "blacklist".
| String
|-
| override_stack_size
| The stack size the inserter is set to, optional. [[Types/uint8]].
| Integer
|-
| drop_position
| The drop position the inserter is set to, optional. [[#Position object]].
| Object
|-
| pickup_position
| The pickup position the inserter is set to, optional. [[#Position object]].
| Object
|-
| request_filters
| Used by [[Prototype/LogisticContainer]], optional. [[#Logistic filter object]].
| Array
|-
| request_from_buffers
| Boolean. Whether this requester chest can request from buffer chests.
| Boolean
|-
| parameters
| Used by [[Programmable speaker]], optional. [[#Speaker parameter object]].
| Object
|-
| alert_parameters
| Used by [[Programmable speaker]], optional. [[#Speaker alert parameter object]]
| Object
|-
| auto_launch
| Used by the rocket silo, optional. Boolean, whether auto launch is enabled.
| Boolean
|-
| variation
| Used by [[Prototype/SimpleEntityWithForce]] or [[Prototype/SimpleEntityWithOwner]], optional. [[Types/GraphicsVariation]]
|
|-
| color
| Color of the [[Prototype/SimpleEntityWithForce]], [[Prototype/SimpleEntityWithOwner]], or train station, optional. [[#Color object]].
| Object
|-
| station
| The name of the train station, optional.
| String
|-
| manual_trains_limit
| The manually set train limit of the train station, optional.
| Integer
|-
| switch_state
| The current state of the power switch, optional.
| Boolean
|-
| tags
| Dictionary of arbitrary data, optional. [https://lua-api.factorio.com/latest/concepts.html#Tags Tags].
| Object
|}

=== Inventory object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| filters
| Array of [[#Item filter object]]s.
| Array
|-
| bar
| The index of the first inaccessible item slot due to limiting with the red "bar". 0-based, optional. [[Types/ItemStackIndex]].
| Integer
|}

=== Schedule object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| schedule
| Array of [[#Schedule Record object]]s.
| Array
|-
| locomotives
| Array of entity numbers of locomotives using this schedule.
| Array
|}

=== Schedule Record object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| station
| The name of the stop for this schedule record.
| String
|-
| wait_conditions
| Array of [[#Wait Condition object]]s.
| Array
|-
| temporary
| Whether this is a temporary schedule record. Optional.
| Boolean
|}

=== Wait Condition object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| type
| One of "time", "inactivity", "full", "empty", "item_count", "circuit", "robots_inactive", "fluid_count", "passenger_present", "passenger_not_present".
| String
|-
| compare_type
| Either "and", or "or". Tells how this condition is to be compared with the preceding conditions in the corresponding wait_conditions array.
| String
|-
| ticks
| Number of ticks to wait or of inactivity. Only present when type is "time" or "inactivity". Optional.
| uint
|-
| condition
| [https://lua-api.factorio.com/latest/concepts.html#CircuitCondition CircuitCondition object], only present when type is "item_count", "circuit" or "fluid_count".
| Object
|}

=== Tile object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Prototype name of the tile (e.g. "concrete")
| String
|-
| position
| [[#Position object]], position of the entity within the blueprint.
| Object
|}

=== Position object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| x
| X position within the blueprint, 0 is the center.
| Floating point
|-
| y
| Y position within the blueprint, 0 is the center.
| Floating point
|}

=== Connection object ===
Object containing information about the connections to other entities formed by red or green wires.

{| class="wikitable"
! Key !! Description !! Data type
|-
| 1
| First connection point. The default for everything that doesn't have multiple connection points.[[#Connection point object]]
| Object
|-
| 2
| Second connection point. For example, the "output" part of an arithmetic combinator.[[#Connection point object]]
| Object
|}

=== Connection point object ===
The actual point where a wire is connected to. Contains information about where it is connected to.

{| class="wikitable"
! Key !! Description !! Data type
|-
| red
| An array of [[#Connection data object]] containing all the connections from this point created by red wire.
| Array
|-
| green
| An array of [[#Connection data object]] containing all the connections from this point created by green wire.
| Array
|}

=== Connection data object ===
Information about a single connection between two connection points.

{| class="wikitable"
! Key !! Description !! Data type
|-
| entity_id
| ID of the entity this connection is connected with.
| Integer
|-
| circuit_id
| The circuit connector id of the entity this connection is connected to, see [https://lua-api.factorio.com/latest/defines.html#defines.circuit_connector_id defines.circuit_connector_id].
| Integer
|}

=== Item request object ===
1 or more instances of key/value pairs.
Key is the name of the item, string.
Value is the amount of items to be requested, [[Types/ItemCountType]].

=== Item filter object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Name of the item prototype this filter is set to.
| String
|-
| index
| Index of the filter, 1-based.
| Integer
|}

=== Infinity settings object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| remove_unfiltered_items
| Boolean. Whether the "remove unfiltered items" checkbox is checked.
| Boolean
|-
| filters
| Filters of the infinity container, optional. Array of [[#Infinity filter object]]s.
| Array
|}

=== Infinity filter object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Name of the item prototype the filter is set to, string.
| String
|-
| count
| Number the filter is set to, [[Types/ItemCountType]].
| Integer
|-
| mode
| Mode of the filter. Either "at-least", "at-most", or "exactly".
| String
|-
| index
| Index of the filter, 1-based.
| Integer
|}

=== Logistic filter object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| name
| Name of the item prototype this filter is set to.
| String
|-
| index
| Index of the filter, 1-based.
| Integer
|-
| count
| Number the filter is set to, [[Types/ItemCountType]]. Is 0 for storage chests.
| Integer
|}

=== Speaker parameter object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| playback_volume
| [[Types/double]]. Volume of the speaker.
| Floating point
|-
| playback_globally
| Boolean, whether global playback is enabled.
| Boolean
|-
| allow_polyphony
| Boolean, whether polyphony is allowed.
| Boolean
|}

=== Speaker alert parameter object ===
{| class="wikitable"
! Key !! Description !! Data type
|-
| show_alert
| Boolean, whether an alert is shown.
| Boolean
|-
| show_on_map
| Boolean, whether an alert icon is shown on the map.
| Boolean
|-
| icon_signal_id
| The icon that is displayed with the alert, [[#SignalID object]].
| Object
|-
| alert_message
| String, message of the alert.
| String
|}

=== Color object ===

{| class="wikitable"
! Key !! Description !! Data type
|-
| r
| red, number from 0 to 1.
| Floating point
|-
| g
| green, number from 0 to 1.
| Floating point
|-
| b
| blue, number from 0 to 1.
| Floating point
|-
| a
| transparency, number from 0 to 1.
| Floating point
|}

=== Control behavior object ===

'''ALL fields are optional''' and depend on the type of the entity.

{| class="wikitable"
|-
! Key !! Description !! Data type
|-
| logistic_condition
| [https://lua-api.factorio.com/latest/concepts.html#CircuitCondition CircuitCondition]
| Object
|-
| connect_to_logistic_network
| Whether this entity is connected to the logistic network and enables/disables based on logistic_condition.
| Boolean
|-
| circuit_close_signal
| Whether this rail signal can be closed by circuit_condition.
| Boolean
|-
| circuit_read_signal
| Whether or not to read the state of this rail/chain signal.
| Boolean
|-
| red_output_signal
| [[#SignalID]] to use if the rail/chain signal is currently red.
| Object
|-
| orange_output_signal
| [[#SignalID]] to use if the rail/chain signal is currently orange.
| Object
|-
| green_output_signal
| [[#SignalID]] to use if the rail/chain signal is currently green.
| Object
|-
| blue_output_signal
| [[#SignalID]] to use if the chain signal is currently blue.
| Object
|-
| circuit_condition
| [https://lua-api.factorio.com/latest/concepts.html#CircuitCondition CircuitCondition]
| Object
|-
| circuit_enable_disable
| Enable or disable based on circuit_condition.
| Boolean
|-
| send_to_train
| Send circuit values to the train to use in schedule conditions.
| Boolean
|-
| read_from_train
| Get the currently stopped trains cargo.
| Boolean
|-
| read_stopped_train
| Get the currently stopped trains ID.
| Boolean
|-
| train_stopped_signal
| [[#SignalID]] to output the train ID on.
| Object
|-
| set_trains_limit
| Whether this stations trains limit will be set through circuit values.
| Boolean
|-
| trains_limit_signal
| [[#SignalID]] to use to set the trains limit.
| Object
|-
| read_trains_count
| Whether to read this stations currently on route trains count.
| Boolean
|-
| trains_count_signal
| [[#SignalID]] to output the on route trains count on.
| Object
|-
| read_logistics
| Whether this roboport should output the contents of its network.
| Boolean
|-
| read_robot_stats
| Whether this roboport should output the robot stats of its network.
| Boolean
|-
| available_logistic_output_signal
| [[#SignalID]] to output available logistic robots on.
| Object
|-
| total_logistic_output_signal
| [[#SignalID]] to output the total count of logistic robots on.
| Object
|-
| available_construction_output_signal
| [[#SignalID]] to output available construction robots on.
| Object
|-
| total_construction_output_signal
| [[#SignalID]] to output the total count of construction robots on.
| Object
|-
| circuit_open_gate
| Whether to limit the gate opening with circuit_condition.
| Boolean
|-
| circuit_read_sensor
| Whether to send the wall-gate proximity sensor to the circuit network.
| Boolean
|-
| output_signal
| [[#SignalID]] to output the wall-gate sensor / accumulator charge on.
| Object
|-
| circuit_read_hand_contents
| Whether to read this belts content or inserters hand.
| Boolean
|-
| circuit_contents_read_mode
| [https://lua-api.factorio.com/latest/defines.html#defines.control_behavior.transport_belt.content_read_mode defines.control_behavior.transport_belt.content_read_mode]
| Integer
|-
| circuit_mode_of_operation
|
| Integer
|-
| circuit_hand_read_mode
| [https://lua-api.factorio.com/latest/defines.html#defines.control_behavior.inserter.hand_read_mode defines.control_behavior.inserter.hand_read_mode]
| Integer
|-
| circuit_set_stack_size
| Whether to set the inserters stack size from a circuit signal.
| Boolean
|-
| stack_control_input_signal
| [[#SignalID]] to use to set the inserters stack size.
| Object
|-
| circuit_read_resources
| Whether this miner should output its remaining resource amounts to the circuit network.
| Boolean
|-
| circuit_resource_read_mode
| [https://lua-api.factorio.com/latest/defines.html#defines.control_behavior.mining_drill.resource_read_mode defines.control_behavior.mining_drill.resource_read_mode]
| Integer
|-
| is_on
| Whether this constant combinator is currently on or off.
| Boolean
|-
| filters
| Array of [https://lua-api.factorio.com/latest/concepts.html#ConstantCombinatorParameters ConstantCombinatorParameters].
| Array
|-
| arithmetic_conditions
| [https://lua-api.factorio.com/latest/concepts.html#ArithmeticCombinatorParameters ArithmeticCombinatorParameters]
| Object
|-
| decider_conditions
| [https://lua-api.factorio.com/latest/concepts.html#DeciderCombinatorParameters DeciderCombinatorParameters]
| Object
|-
| circuit_parameters
| [https://lua-api.factorio.com/latest/concepts.html#ProgrammableSpeakerCircuitParameters ProgrammableSpeakerCircuitParameters]
| Object
|-
| use_colors
| Whether this lamp should use colors or not.
| Boolean
|}

[[Category:Technical]]

== Example code ==

On a typical Bash command line, the blueprint can be decoded like so:

<syntaxhighlight lang="bash">echo "$blueprint_string" | cut -c2- | base64 -d | pigz -d</syntaxhighlight>

How to decode a string to lua table:
<syntaxhighlight lang="lua">
local str="$blueprint_string";

local bp_to_table=function(instr)

--[[version and the body part]]
local version=string.sub(instr,1,1);
local body=string.sub(instr,2);
--[[then decode it]]
local json_str=game.decode_string(body);
--[[then turn it into table]]
local output=game.json_to_table(json_str);

return output;
end

--[[and this could test if it print properly]]
game.print( serpent.block( bp_to_table(str) ) );

</syntaxhighlight>

Ice

2024-10-28T22:51:05Z

Thoxo: Created page with "{{Languages}} {{:Infobox:Ice}} {{Stub}} {{About/Space age}} '''Ice''' is a resource added in the Space Age{{SA}} expansion. == History == {{history|2.0.7| * Introduced in Space Age{{SA}} expansion. }} {{IntermediateNav}} {{C|Components}}"

{{Languages}}
{{:Infobox:Ice}}
{{Stub}}
{{About/Space age}}
'''Ice''' is a resource added in the [[Space Age]]{{SA}} expansion.

== History ==
{{history|2.0.7|
* Introduced in [[Space Age]]{{SA}} expansion.
}}

{{IntermediateNav}}
{{C|Components}}

Infobox:Ice

2024-10-28T22:48:39Z

Thoxo: Created infobox to create the item page

{{Infobox
|prototype-type =
|space-age = yes
|internal-name =
|category = Intermediate products
|stack-size=50
|rocket-capacity=1000
|consumers = Ice platform + Ice melting + Space science pack + Cryogenic science pack
|producers = Scrap recycling + Ammoniacal solution separation + Oxide asteroid crushing + Advanced oxide asteroid crushing
}}<noinclude>
[[Category:Infobox page]]
</noinclude>

Iron stick

2024-10-28T22:37:20Z

Thoxo: /* Version history */ Added revision notes for 2.0.11

{{Languages}}
{{:Infobox:Iron stick}}

'''Iron sticks''' are a basic intermediate product. They are used in a few early and mid-game recipes.

== Version history ==
{{History|2.0.11|
* {{SA}}Fulgora ruins now also drop iron sticks when mined so electric poles could be crafted without recyclers at the start.
}}

{{History|0.17.0|
* Medium and big electric pole, train stop, and programmable speaker now use this as an ingredient. [[Lamp]] recipe iron sticks ingredient changed to [[copper cable]]s.
}}

{{IntermediateNav}}
{{C|Components}}

Scrap

2024-10-28T22:34:34Z

Thoxo: Redid the recycling results table and added link to recycler

{{Languages}}
{{:Infobox:Scrap}}
{{Stub}}
{{About/Space age}}
'''Scrap''' is a resource found on [[Fulgora]]{{SA}}. It needs to be recycled by hand or in the [[recycler]]{{SA}} to get usable products.

{| class="wikitable sortable"
|+ Recycling results
|-
! Item !! Percent
|-
| {{Imagelink|Processing unit}} || 2%
|-
| {{Imagelink|Advanced circuit}} || 3%
|-
| {{Imagelink|Low density structure}} || 1%
|-
| {{Imagelink|Solid fuel}} || 7%
|-
| {{Imagelink|Steel plate}} || 4%
|-
| {{Imagelink|Concrete}} || 6%
|-
| {{Imagelink|Battery}} || 4%
|-
| {{Imagelink|Ice|space-age=yes}} || 5%
|-
| {{Imagelink|Stone}} || 4%
|-
| {{Imagelink|Holmium ore|space-age=yes}} || 1%
|-
| {{Imagelink|Iron gear wheel}} || 20%
|-
| {{Imagelink|Copper cable}} || 3%
|}

== History ==
{{history|2.0.7|
* Introduced in [[Space Age]]{{SA}} expansion.
}}

== See also ==
* [[Fulgora]]{{SA}}
* [[Recycler]]{{SA}}

{{IntermediateNav}}
{{C|Resources}}

Infobox:Fast transport belt

2024-10-28T19:11:54Z

Thoxo: Add foundry to list of producers

{{Infobox
|resistance = {{Translation|Fire}}: 0/50%
|mining-time = 0.1
|map-color = c8a040
|prototype-type = transport-belt
|internal-name = fast-transport-belt
|category = Logistics
|image = fast_transport_belt_entity
|health = 160
|stack-size = 100
|dimensions=1×1
|belt-speed = 30 {{Translation|Items/s}}
|recipe = Time, 0.5 + Iron gear wheel, 5 + Transport belt, 1
|total-raw = Time, 3.5 + Iron plate, 11.5
|required-technologies = Logistics 2
|producers = Player + Assembling machine + Foundry
|consumers = Express transport belt
}}<noinclude>[[Category:Infobox page]]</noinclude>

Infobox:Transport belt

2024-10-28T19:08:55Z

Thoxo: Add Foundry as a producer

{{Infobox
|resistance = {{Translation|Fire}}: 0/90%
|mining-time = 0.1
|map-color = c8a040
|prototype-type = transport-belt
|internal-name = transport-belt
|recipe = Time, 0.5 + Iron gear wheel, 1 + Iron plate, 1 = Transport belt, 2
|category = Logistics
|image = transport_belt_entity
|health = 150
|stack-size = 100
|dimensions=1×1
|belt-speed = 15 {{Translation|Items/s}}
|total-raw = Time, 1 + Iron plate, 3
|producers = Player + Assembling machine + Foundry
|consumers = Fast transport belt + Lab + Logistic science pack + Splitter + Underground belt
}}<noinclude>[[Category:Infobox page]]</noinclude>