Satisfactory Wiki
Satisfactory Wiki
 
Line 5: Line 5:
 
:So I think the best way would be to adjust the [[Template:CraftingTable]] to also save the values in the cargo-database. The cargo_store method was removed in this template, probably because moving it to the infobox. We could use the [https://www.mediawiki.org/wiki/Extension:Cargo/Storing_data#Attaching_to_a_table]-function here. --[[User:Cadaei|Cadaei]] ([[User talk:Cadaei|talk]]) 12:03, 5 May 2019 (UTC)
 
:So I think the best way would be to adjust the [[Template:CraftingTable]] to also save the values in the cargo-database. The cargo_store method was removed in this template, probably because moving it to the infobox. We could use the [https://www.mediawiki.org/wiki/Extension:Cargo/Storing_data#Attaching_to_a_table]-function here. --[[User:Cadaei|Cadaei]] ([[User talk:Cadaei|talk]]) 12:03, 5 May 2019 (UTC)
 
:: Please create a sandbox page to play around with templates like that. Let's not add broken layout to live pages.<br/>--[[User:CerbrusNL|CerbrusNL]] ([[User talk:CerbrusNL|talk]]) 12:37, 5 May 2019 (UTC)
 
:: Please create a sandbox page to play around with templates like that. Let's not add broken layout to live pages.<br/>--[[User:CerbrusNL|CerbrusNL]] ([[User talk:CerbrusNL|talk]]) 12:37, 5 May 2019 (UTC)
  +
::: Storing those alternate recipes in the cargo table makes them show up in their ingredients page's "Crafting" tables, with no indication that these are alternate recipes that require extra research. If we want to automate alternate recipes, they can't show up as an ordinary recipe on the ingredient's pages.<br/>--[[User:CerbrusNL|CerbrusNL]] ([[User talk:CerbrusNL|talk]]) 07:48, 6 May 2019 (UTC)

Latest revision as of 07:48, 6 May 2019

Hi I wanted to try out using info box for alternatives. The problem is that the info box visual become buggy in collapsed table and the next template following this table also become buggy. Need help on the formatting. The idea behind this is, these infoboxes automatically update the component page such as Iron Ingot, you can see alternative steel is being added there. --Kwjcool321 (talk) 04:52, 5 May 2019 (UTC)

Hi, good idea! We need to consider that each infobox will create one database-row, though, so each page should contain at most one infobox. We could just display the resource-breakdown without infobox, as most of the infos in the infobox are identical. The only differences would be the ingredients, the productCount and maybe the craftingTime. I'll set up an example on how it could be displayed. --Cadaei (talk) 10:09, 5 May 2019 (UTC)
Now I see, you want that additional row to be added to have the usedToCraft (Template:CraftingUsage) updated as well. Let's see if that works as expected, would be useful. I think the template:craftingTable breaks the layout if other tables are put between two of these tables.--Cadaei (talk) 10:39, 5 May 2019 (UTC)
So I think the best way would be to adjust the Template:CraftingTable to also save the values in the cargo-database. The cargo_store method was removed in this template, probably because moving it to the infobox. We could use the [1]-function here. --Cadaei (talk) 12:03, 5 May 2019 (UTC)
Please create a sandbox page to play around with templates like that. Let's not add broken layout to live pages.
--CerbrusNL (talk) 12:37, 5 May 2019 (UTC)
Storing those alternate recipes in the cargo table makes them show up in their ingredients page's "Crafting" tables, with no indication that these are alternate recipes that require extra research. If we want to automate alternate recipes, they can't show up as an ordinary recipe on the ingredient's pages.
--CerbrusNL (talk) 07:48, 6 May 2019 (UTC)