Satisfactory Wiki:Admin noticeboard

The Admin noticeboard is one way through which users can notify Administrators of issues needing administrative attention. While users are welcome to directly contact specific administrators (especially if they are seen to be active), posting here can be an easier and quicker way of ensuring that at least one admin will notice an issue and respond to it promptly. Remember to sign (using four tildes: ) when posting an issue.

Before posting an issue here, please consider the following:
 * This page is for reporting wiki issues. Please post discussions |on the talk page.
 * Post only issues that require administrative action, i.e. blocking vandals, protecting pages, restoring deleted pages etc.
 * Do not post deletion requests here. Deletion requests should be made by adding  to the top of the target page, which will then automatically mark the page as a candidate for deletion.
 * Do not post issues regarding content disputes. Try making a request for comment instead.
 * Mediation requests between users should only be made once a resolution could not be reached between users.
 * For issues regarding the use of this wiki, please see our help center.

In case of vandalism, posting about it here is low priority. Revert it first, anyone can do so. If the vandal created a new page, tag it for deletion. Assume good faith and consider leaving a message on that user's talk page to explain the reason. Post here only if the user has made several disruptive edits and/or persists despite a warning. Always avoid a revert war with the vandal; it is far better to wait until an admin has a chance to intervene. If a user must be reported here, please use user, preferably as the topic subject/headline.

[ Please post new topics at the bottom of the page by clicking this link to add a new section.]

= Current Issues =

de:Project:Adminpinnwand fr:Project:Panneau administratif

Adding the Dutch language
I love the game and like the looks of the wiki here. I would like to set up the dutch wiki, therefor the language needs to be added to the main page. Currently (23-5-2019) there are 6 pages with an /nl, I hope any admin member can make an dutch (nl) sub-domain!
 * In order to create a subdomain for another language, we need the front page and at least some of the pages linked from it to be translated, and we'd need ideally a community but at a minimum one person willing to commit to administrating that wiki, which is a bigger task than it may sound. We currently have none of these prerequisites met for Dutch. --Mr Pie 5 (talk) 00:20, 24 May 2019 (UTC)

I messed up on one of my translations
Hey, I messed up with creating one of the translated pages and it created a wrongly named non working page, meaning there is no way to add a delete tag to it. all the links of the broken page link to https://nl/Top_section, which of course does not work. Joerkig (talk) 08:31, 24 May 2019 (UTC)
 * Deleted. --Mr Pie 5 (talk) 08:34, 24 May 2019 (UTC)

Establishment of rules for stale translation projects
Practically all wiki translation projects (except those on separate domains and /zh which has recent activity and is being updated) are unmaintained with barely any activity. Some pages still have information from even pre-Update 1, which means many of them provide flat out inaccurate or misleading information.

I feel like some rules for stale translations should be set up so that unmaintained and/or bad translations are removed from the wiki. --Ondar111 (talk) 18:38, 10 January 2021 (UTC)


 * Suggestions:
 * Stage 1) Call for new maintainers with period of X weeks before proceeding to next stage if no suitable maintainers can be found.
 * Stage 2) Announce grace period of Y weeks for deletion.
 * Stage 3) If possible, lock content against edits then archive content for Z days before deletion.
 * Stage 4) Delete stale content
 * SignpostMarv (talk) 23:30, 11 January 2021 (UTC)
 * p.s. "stale" should be strongly-defined.
 * SignpostMarv (talk) 23:32, 11 January 2021 (UTC)


 * I don't see the gain to deleting them, just removes a starting point if we happen to get someone who wants to pick up the project. Except in cases where there was very little effort put in (e.g. article is still in English, or just one sentence or two is translated), I don't think we should be deleting abandoned translation projects. A notice of how outdated the page is would be more appropriate.
 * I also don't understand your "stage 3", Marv. What does that accomplish? --Mr Pie 5 (talk) 23:05, 30 January 2021 (UTC)


 * Stage 3 means locking the content to avoid having to monitor it for activity while it's in the grace period, while leaving the talk page open for "no wait, don't delete it yet"
 * SignpostMarv (talk) 19:42, 26 February 2021 (UTC)


 * Well, there are some problems caused by keeping the bad translation projects up. Readers in those languages might search for information in their own language, and when they do, they're served with a badly written or outdated article, bringing the overall "quality" of (or trust in) the wiki down. It also clutters up search and wiki maintenance categories.
 * Marking the pages as outdated means marking about 200 pages. --Ondar111 (talk) 09:25, 31 January 2021 (UTC)


 * Unmaintained translated pages are a big hit for the upcoming centralized recipe and infobox system. When the system is being remade, it should be done properly for once without leaving traces of the old system.
 * Currently, the translated pages are still on the Update 2 revision of the system (storing only via infoboxes, resource breakdowns), not even the Update 3 rev (storing via infoboxes and CraftingTable, non-primary recipes and byproducts) and will certainly not support the Update 4 rev (centralized storage, pages only pull data), as a part of it is getting rid of the obscure or unused templates involved, which would stop working either way.
 * This means that the unmaintained translated pages will stop working almost entirely except for plaintext due to both infoboxes and the recipe system changing. Having to fix the templates is a large amount of effort and seems like a waste if noone is gonna work on the pages the templates would be used on.
 * If we get rid of the translated pages, the new system can be implemented smoothly, and ongoing translation projects (especially DE) can benefit from it significantly. I haven't seen any translated page activity in a month.
 * TL;DR: Translated pages use old recipe/infobox templates that were never updated, which will stop working entirely with the new recipe/infobox system. --Ondar111 (talk) 21:37, 26 February 2021 (UTC)


 * I could focus on the German version of this wiki. But it would take a lot of effort and time to update all the articles and translate them again. Cepto (talk) 18:29, 31 January 2021 (UTC)


 * An update for potential readers: the rules have been estabilished and are in effect, see Satisfactory Wiki:Localization project rules. --Ondar111 (talk) 19:42, 22 October 2021 (UTC)

Guidelines or rules regarding screenshots from the game
What rules must be followed when ingame screenshots are taken and used in this wiki? Cepto (talk) 19:15, 28 January 2021 (UTC)
 * Rules for images in general are yet to be defined and listed in the style guide. In short, the what should be commonly applied is:
 * Nothing intrusive in the way (if taking a picture of a Train Station for example, only it should be in shot, not other unrelated factories), take images with photo mode if UI isn't meant to be a part of the image
 * Compressed JPEG is the way, ideally less than 300 kB filesize
 * Use  as license and categorize the image when uploading (e.g. Category:Building screenshots or at least Category:Screenshots)
 * --Ondar111 (talk) 19:35, 28 January 2021 (UTC)

Can't upload any videos, regardless of video size.
All video media uploads now result in the error in the image. Tried several different video sizes, looks like maybe the result of moving from gamepedia to fandom, and fandom doesn't properly chunk their upload streams.


 * I can see you're uploading through VisualEditor, which can give poor error message. Try Special:Upload and see if it gives you anything different. --Mr Pie 5 (talk) 23:04, 28 March 2021 (UTC)

Rebuild the ` ` cargo table

I’ve added the   parameter to CraftingTable in order to correctly classify seasonal event recipes, such as those added by FICS⁕MAS, without needing to add , depending on whether the seasonal event is currently active. The styling for seasonal event recipe stripes is handled by CraftingTable/season.

Please rebuild the relevant cargo table, so that the FICS⁕MAS recipes are correctly marked as such.