Feed The Beast Wiki:Centralized discussion

Random TODO
"Stained clay blocks are renamed from '  Stained Clay ' to '  Hardened Clay '."-mcw:Hardened Clay -Xbony2 (talk) 00:14, 1 September 2016 (UTC)

Guide credits
I really don't like the fact that we put "credits" at the tops of our guides. In many cases that information is accessible via the history. Furthermore it creates a sense of ownership on the articles, potentially discouraging new users from editing it. See also: Wikipedia:Ownership of content. The only case I can see this making sense is for guides which were written by someone, but then put on the wiki by someone else. I don't have a proposal for that situation, but I do propose that for the other cases, we do not put credits on the page. --  Satanic Santa 🎅F T B Wiki Admin 20:06, 5 February 2017 (UTC)
 * As a general principle we should only include credits when content was written by someone not on the wiki and then copied over to the wiki. 22:00, 5 February 2017 (UTC)
 * The thing I don't like is that it gives more respect to guides that were created elsewhere rather than made by the editors here. I'd be okay with it, however, maybe if the note was at the very bottom of the page (ex Foreign relations of Armenia, although probably a bit large than that) instead of blatantly at the top (change would be like this). -Xbony2 (talk) 02:55, 6 February 2017 (UTC)
 * I'm fine with that. It's not the best format but it's definitely better. --  Satanic Santa 🎅F T B Wiki Admin 19:08, 6 February 2017 (UTC)
 * Just a thought on this, what about having a fixed-position small link image, or even just an "@" character, in the bottom right of the content area that links back to the original source in this sort of case? Not too intrusive, and easy enough to write a template for. DSquirrelGM (talk) 18:49, 8 February 2017 (UTC)
 * Not all of them have original sources, like Getting Started (Flaxbeard's Steam Power). I think something that links to the original source for those applicable could be useful though. --  Satanic Santa 🎅F T B Wiki Admin 18:57, 8 February 2017 (UTC)
 * Or, we can add credits but the ones made by the editors should have the name of "Made by the community" or "Made by FTB Wiki Team" or something. So it's enough to say that it was made for this wiki but not too much sense of ownership. - Indestructible Pharaoh VII 17:51, 16 February 2017 (UTC)
 * It's on the wiki so it's obvious that it's made by the wiki community. --  Satanic Santa 🎅F T B Wiki Admin 22:31, 16 February 2017 (UTC)

April 17 2017 update
I've removed the credits from non-controversial guides (those which credited only people listed in the history for the page, many of which were mine >.>). I have left the credits in the ones in which credited people were not listed in the history, since we did not seem to reach a consensus for that. --  Satanic Santa 🎅F T B Wiki Admin 05:53, 18 April 2017 (UTC)

Category overhaul
Everything related to categories is terrible. To start, we have changed the policy to allow for multiple categories per page. To make this more useful, we will be creating more descriptive categories. The following list of new categories will be updated as we add more:



We are also going to be renaming some categories and reevaluating their usefulness. The following categories need to be renamed and/or reevaluated:


 * Base
 * Resource Page
 * Transformation
 * Other
 * Converters
 * Portable
 * Sorting
 * Pipes
 * Tubes
 * Conduit
 * Modules
 * Attributes
 * Redpower
 * Miscellaneous Automation

The following categories have been replaced:


 * Documentation has been replaced with
 * Electric has been replaced with
 * Attributes has been replaced with

This project is more clearly documented on its project page.

Please discuss stuff. --  Satanic Santa F T B Wiki Admin 22:14, 8 February 2015 (UTC)


 * Okay so I have a few ideas with some of those; namely pipes, conduits and tubes etc..
 * My suggestion is to use categories that are bit more inclusive such as, , which could each respectively classify things like BC pipes, IC2 Cable and Fluiducts. Another group of categories to assist this could be , , and  which would classify items such as IC2 Batteries as well as BC Tanks
 * These could then also be supplemented (only for the energy ones) by the specifics such as or.


 * To recap how this would look
 * A BC Wooden pipe would be categorized as -
 * An IC2 Cable would be --
 * A TE Energy Cell would be --
 * An OpenBlocks Tank would be -
 * Wolfman_123_ ·&#32;✉ F T B  Wiki Staff  04:37, 12 February 2015 (UTC)


 * Small continuation after looking through some more categories; I believe is perfectly fine as it's simply just Steve's Carts modules which would be categorized as -
 * I also believe is fine however it may need a renaming to  or something like that (I think this is the word Forestry uses to describe them, but please don't quote me on that)
 * Wolfman_123_ ·&#32;✉ F T B  Wiki Staff  04:50, 12 February 2015 (UTC)


 * Last one I hope...
 * Can someone please explain what the hell is supposed to be as I don't really see much of a link between all of the content.
 * Wolfman_123_ ·&#32;✉ F T B  Wiki Staff  04:52, 12 February 2015 (UTC)


 * I think is being used for machines that would be part of a large-scale industrial base? I'm not entirely sure though, there's one or two outliers in that.
 * Maybe it's for for pages that act as the base point for some form of industrialization, and are built on from there? Like 'components' but larger scale?
 * You're right though, there is not a lot of consistency across that category. PaladinAHOne  Staff (talk) 07:01, 12 February 2015 (UTC)


 * Oh god then I realized that Forge and FML were in ... What the hell was this category even?? PaladinAHOne  Staff (talk) 19:44, 12 February 2015 (UTC)


 * Base is one of those categories that you just wonder what the hell went wrong. Really, it should either just have base mods like Forge and FML in, or they should go in and I guess  deleted.  Chocohead  Nag • Edits • Staff 19:50, 12 February 2015 (UTC)


 * I'm not quite sure what to do about Forge and FML, but I have an idea for all the generators in that category sticking with the theme above.
 * Wolfman_123_ ·&#32;✉ F T B  Wiki Staff  23:56, 12 February 2015 (UTC)
 * Wolfman_123_ ·&#32;✉ F T B  Wiki Staff  23:56, 12 February 2015 (UTC)
 * Wolfman_123_ ·&#32;✉ F T B  Wiki Staff  23:56, 12 February 2015 (UTC)


 * Base was for energy generators. The problem with Modules is it's too broad. It could mean SC modules, modules of mods, etc. Same goes for Attributes. I agree with your transportation stuff. --  Satanic Santa F T B Wiki Admin 02:51, 13 February 2015 (UTC)

c · ru translator  13:18, 14 March 2015 (UTC)
 * Are you continuing on doing this? — NickTheRed37  ᐸ t · ru.MCW user


 * I've been busy with other stuff, but it will be completed at some point. --  Satanic Santa F T B Wiki Admin 19:10, 14 March 2015 (UTC)

c · ru translator  06:13, 30 March 2015 (UTC)
 * I may later think of an image of what I want to have as a category tree. — NickTheRed37  ᐸ t · ru.MCW user


 * For those interested, I have been working on the categorization stuff. I moved -> . -Xbony2 (talk) 14:48, 4 April 2015 (UTC)


 * So, uh, what is a consumer called? Like, Macerator (IndustrialCraft 2) or Induction Smelter. I'd propose something like:


 * Macerator (IndustrialCraft 2): --- (btw, should we do anything about the Crushing category, or not?)
 * Induction Smelter: ---
 * Remote Thermal Monitor: --- (nuclear may need to be re-evalulated too)

-Xbony2 (talk) 15:11, 4 April 2015 (UTC)


 * Why did you put in ? :P  Chocohead  Nag • Edits • Staff 22:29, 4 April 2015 (UTC)


 * I didn't do it! :P I'm not even listed in the history of the page. -Xbony2 (talk) 22:46, 4 April 2015 (UTC)


 * So you just edited ... Alistaire14820 added Miner to it years ago. :| Our categories are so screwed up.  Chocohead Nag • Edits • Staff 23:22, 4 April 2015 (UTC)


 * btw, can you look over Energy Units? Thanks. -Xbony2 (talk) 23:31, 4 April 2015 (UTC)


 * since nobody loves me, I'm going ahead with my proposition :P -Xbony2 (talk) 13:33, 8 April 2015 (UTC)

I have created a utility that can help us along with phase 1 of the Category Overhaul greatly. It requires Ruby, and the mediawiki_api gem created by wikimedia (be sure to use 0.3.1 as the newer versions are broken). You can find it in the SatanicBot repo. You will need to create your own secure.txt file with the formatting "USERNAME \newline PASSWORD". Alternatively you can just edit your clone of generalutils to use your username and password. --  Satanic Santa F T B Wiki Admin 23:00, 19 August 2015 (UTC)

Templates that may want to be made
(Altars are popular these days) -Xbony2, Master of Feed The Beast Wiki (talk) 01:47, 2 November 2015 (UTC) -Xbony2, Master of Feed The Beast Wiki (talk) 00:31, 3 November 2015 (UTC)
 * Cg/Runic Altar - PaladinAHOne  Staff (talk) 07:36, 6 November 2015 (UTC)
 * Cg/Blood Altar - PaladinAHOne Staff (talk) 07:46, 11 November 2015 (UTC)
 * Cg/SAG Mill
 * Cg/Alloy Smelter/Ender IO
 * Cg/The Vat
 * Cg/Slice'N'Splice


 * Cg/Chemical Decomposer
 * Cg/Chemical Fusion Chamber
 * The Fusion Chamber isn't needed because there are dozens of possible combinations for every element to create it. --LuminousLizard FTB Wiki Staff de-N / "en-2" (talk) 21:31, 18 November 2016 (UTC)


 * Cg/Chemical Fission Chamber

All from MineChem. --  Satanic Santa 🎅F T B Wiki Admin 20:51, 19 December 2015 (UTC)
 * I think over the free days I'll create the template for the Decomposer. --LuminousLizard de-native / "en-B2" (talk) 21:54, 22 December 2015 (UTC)

-Xbony2 (talk) 13:20, 30 December 2015 (UTC) -Xbony2 (talk) 13:22, 30 December 2015 (UTC)
 * Cg/Alloy Smelter/GregTech 4
 * Cg/Extruder

--  Satanic Santa 🎅F T B Wiki Admin 02:14, 29 February 2016 (UTC)
 * Navbox Mariculture
 * I will do that in the next days. Should I create a normal navbox or a module ? --LuminousLizard de-native / "en-2" (talk) 20:16, 3 April 2016 (UTC)
 * From quickly looking at the mod, it looks like it adds a lot of content, so I'd recommend a module if it doesn't make you uncomfortable. -Xbony2 (talk) 20:47, 3 April 2016 (UTC)
 * Done from my side ! Navbox created and tilesheets uploaded. Problem not solved .. should someone else make the rest => Section: Problem with SheetImporter
 * New version is available and the mod has become a lot bigger. I'll update it when I find time. --LuminousLizard FTB Wiki Staff de-N / "en-2" (talk) 20:41, 28 July 2016 (UTC)
 * Navbox updated ! --LuminousLizard FTB Wiki Staff de-N / "en-2" (talk) 21:31, 18 November 2016 (UTC)

All of the GUIs can be found here. Thanks -Xbony2 (talk) 14:04, 30 March 2016 (UTC)
 * Cg/Infusion Altar -Xbony2 (talk) 13:08, 19 March 2016 (UTC)
 * Cg/Animal Trap
 * Cg/Apiary/Pam's HarvestCraft (these are all PHC btw)
 * Cg/Churn
 * Cg/Fish Trap/Pam's HarvestCraft
 * Cg/Oven
 * Cg/Presser
 * Cg/Quern
 * I'll make the last 3 in the list this weekend. Btw your link is broken ... but I can extract the GUIs out of the mod. --LuminousLizard (Wiki Staff and Editor) de-N / "en-2" (talk) 07:26, 16 April 2016 (UTC)
 * Yeah, Pam removed her machines in 1.8. Your link looks broken too :P In your preferences, you can set the "page type" to "Use a standard user wiki page" so User:LuminousLizard is your regular page, and UserProfile:LuminousLizard is the default global one. -Xbony2 (talk) 12:11, 16 April 2016 (UTC)
 * Done ! The link to my page is ok for me. One page is for a brief overview and the other for more, if interested.


 * Cg/Tool Forge
 * Cg/Stencil Table
 * Cg/Part Builder

The working stations from Tinkers' Construct. I will create the Stencil Table this weekend. --LuminousLizard (Wiki Staff and Editor) de-N / "en-2" (talk) 07:26, 16 April 2016 (UTC) Why don't we have this... -Xbony2 (talk) 00:06, 25 May 2016 (UTC)
 * Cg/Brewing Stand


 * Navbox RFTools --LuminousLizard FTB Wiki Staff de-N / "en-2" (talk) 11:14, 2 July 2016 (UTC)
 * I will do that. --LuminousLizard FTB Wiki Staff de-N / "en-2" (talk) 20:20, 29 July 2016 (UTC)


 * Navbox Hbm's Nuclear Tech
 * Done ! I will check for updates in the future. --LuminousLizard FTB Wiki Staff de-N / "en-2" (talk) 21:31, 18 November 2016 (UTC)


 * Navbox Psi
 * I'm already taking on Psi ^^ I'll probably work on Quark, too, but maybe when it's out of beta. -Xbony2 (talk) 20:45, 28 July 2016 (UTC)
 * Done with that \o/
 * Navbox Actually Additions
 * Also working on this. -Xbony2 (talk) 22:01, 28 July 2016 (UTC)
 * Navbox Extra Utilities 2

Some more navboxes ! --LuminousLizard FTB Wiki Staff de-N / "en-2" (talk) 20:41, 28 July 2016 (UTC)
 * Navbox Magicum


 * Cg/Drying Rack from TiCo, since it got a shit ton more recipes added to it in 1.9/1.10. --  Satanic Santa 🎅F T B Wiki Admin 01:26, 11 July 2016 (UTC)
 * Does this require a crafting template though? You just put the to-be food item on the rack and that's it. --SirMoogle (talk) 19:48, 12 March 2017 (UTC)
 * I'm pretty sure there is a JEI thing for it, which is what we'd use. This is pretty common for us to do. For example, Witchery's Witch's Cauldron has no GUI, but it has an NEI thing which we use for Cg/Witch's Cauldron. --  Satanic Santa 🎅F T B Wiki Admin


 * Navbox Mekanism
 * I will do Mekanism in the next time. --LuminousLizard FTB Wiki Staff de-N / "en-2" (talk) 21:31, 18 November 2016 (UTC)


 * Navbox RFTools Controls ... including the mod page (it's an addon mod for RFTools)


 * Navbox TAIGA ... including the mod page (it's an addon mod for Tinkers' Construct)


 * Cg/Resonator
 * For Extra Utilities 2. It's more or less like a furnace without a fuel slot: one input, one output. I think it uses a flat 15 Grid Power to run +1 for each speed upgrade but double check that it's not recipe dependant. Lady Oolong (talk) 19:21, 9 March 2017 (UTC)


 * Navbox Forbidden Magic

With Astral Sorcery adding 4 different crafting tables, we should make these:
 * Cg/Luminous Crafting Table
 * Cg/Starlight Crafting Altar
 * Cg/Celestial Altar
 * Cg/Iridescent Altar

--SirMoogle (talk) 02:17, 16 November 2017 (UTC)

Blocking policy
Feed The Beast Wiki:Blocking policy should be a thing. And while this message sits in this noticeboard, someone at some point will do it. That someone is not me because I worded it badly when I tried and it looked stupid. -Xbony2 (talk) 23:25, 2 February 2016 (UTC)
 * I think the whole principle of a noticeboard is rather undermined if things are done after the requests are removed from it ;)  Chocohead Nag • Edits • Staff 23:31, 2 February 2016 (UTC)

Modpacks reform
I'm proposing a few ideas on how to reform the documentation of modpacks on the wiki. Thoughts? -Xbony2 (talk) 00:15, 14 March 2016 (UTC) --  Satanic Santa F T B Wiki Admin 02:44, 14 March 2016 (UTC)
 * 1) Removing "Mods Included" sections on modpack pages, and linking to its auto-generated list on CurseForge instead (ex). Virtually all mods in modern modpacks are hosted on CurseForge. There may be a case or two where this incorrect, but the stubborn ones that come to mind (IndustrialCraft 2, Twilight Forest, etc) are all up there. GregTech is the only "big" exception, but I wouldn't be surprised if it followed IC2 in the near future.
 * The "Mods Included" section really serves little purpose; it's absolutely tedious to update and create (speaking from experience), thus they often aren't really updated. Lastly, they are pretty much unused- It's not 2014 anymore; if you want to know what mods a modpack includes, you go it's CurseForge page, or go the launcher; the wiki is not the first stop.
 * There should be exceptions to this rule, of course. Historical modpacks not moved over, like the Ampz Modpack, should allow for a mod list. This rule is mainly meant for future modpacks and current ones, like Infinity 1.7.
 * 1) Changing Infobox mod to convert "Modpacks" to a normal argument, instead of a section, and making it link to its auto-generated list of CurseForge instead (ex). The Modpacks section in mods is also not really updated, or even that used.
 * It's a good thing it isn't that updated, or pages like BuildCraft would go on forever with the list of every modpack it's been in. The only downfall to this is that it will be incorrect for historical packs.
 * 1) With the current (unwritten?) policies, "listed packs" are the only allowed modpacks. Technically, all CurseVoice packs are listed, meaning they can all be documented. I think this should be kept as it is.
 * Policy-wise, modpacks should be treated like mods ( Technically, modpacks are mods, just a mod with many components from many people. ). All modpacks should be allowed to be documented here, just like all mods can be documented here. Of course, like mods, FTB Wiki Staff should focus on documenting FTB packs. But, who are we to point away other users' modpacks? That only pushes users to host their documentation elsewhere, on other wikis or their own wikis.
 * One point that has been used to counter against letting other modpacks be documented here is that it would clutter Navbox Modpacks. My solution to this is pretty simple- just keep FTB-created packs on that navigation box. A proper list could created like our mods, but I think keeping Navbox Modpacks FTB-only would be a good thing.
 * 1) Anyway, the point of these changes is to allow modpack documenters to focus their time on useful things, like creating modpack guides and better descriptions. It's to allow information better hosted elsewhere to be better hosted elsewhere, and to bring our modpack documentation and policies from 2014 into 2016.
 * 1) I think the main reason we still have Mods Included is because you can use that to navigate from modpacks -> mods. I know I personally use this all the time, even if it is absurdly outdated. I think some sort of automatic way to do it, or to get the modpack team to update it themselves would be good. I agree it needs to change.
 * 2) I have been thinking about this for a long time. Perhaps that is a good idea, though not all mods utilize that dependency feature (e.g., Flaxbeard's Steam Power).
 * 3) Agree. I think they could be listed as Unlisted Packs in the navbox.
 * k
 * Get the modpack team to update it. Ha. Automatically generating would make the most sense if we want to keep it. -Xbony2 (talk) 11:10, 14 March 2016 (UTC)

Vegan/Vegetarian Categories
So, the Vegan and Vegetarian Food categories are shit. Most of the things in them are not inherently vegan, but have the option to be made with vegan things (e.g., Apricot Glazed Pork can be made with Tofu since it is made with the listAllporkcooked oredict). We need some sort of change to the way these categories are set up. I don't know how though. --  Satanic Santa F T B Wiki Admin 00:11, 17 April 2016 (UTC)
 * How about having the sub-category substitute for them both, and things that can be cheated using Tofu can go in those.  Chocohead Nag • Edits • Staff 00:19, 17 April 2016 (UTC)
 * Proposing the categories of-

To replace the current categories. I don't think we need to have a category that includes cheaty substitutes, since most MC foods can use said cheaty substitutes. -Xbony2 (talk) 23:45, 19 April 2016 (UTC)
 * (anybody have a better name?)
 * (subcat of last cat, for pure meats)
 * And a philosophical question- if I cheat in a Raw Chicken from NEI, does it count as vegan/vegetarian because no chickens were hurt in the process? -Xbony2 (talk) 23:47, 19 April 2016 (UTC)
 * I live with vegans and am friends with a lot of vegans, and I hear "non-vegan" quite a bit when referring to food made with animal. So I think that's a fine name for a category. Otherwise, there's also omni/carnivorous which get used a lot as well. --  Satanic Santa F T B Wiki Admin 00:03, 20 April 2016 (UTC)

Disambiguating things with slightly different names together
Right now, the general standard is that things are not disambiguated on the same page unless they have the same name exactly. I don't think this is very useful. I think that we should be disambiguating things that have close names on the same pages. Right now, from what I know, there are two pages which do do this: Porcelain (disambiguation) and Vinegar. Part of this also has to do with naming. I think that Wikipedia's "(disambiguation)" thing is fine for right now, but eventually if the disambiguation overhaul is a thing, that can be phased out. --  Satanic Santa 🎅F T B Wiki Admin 05:16, 15 April 2017 (UTC)
 * Interesting idea. Only thing I would suggest is that for the more uniquely named items (e.g., Grape Vinegar compared to the other Vinegar entries) shouldn't need a link back to the disambiguation page. --SirMoogle (talk) 05:26, 15 April 2017 (UTC)
 * If the overhaul goes through, it would be far easier, I think a few disambig pages already have a See also section with similarly named pages. These pages don't link back either. I think that for now having the "(disambiguation)" thing would be fine, the current way of disambiguating is a bit annoying at times so I kinda want to see that changed. --  Hubry  (talk) 16:46, 15 April 2017 (UTC)
 * I also agree, as someone searching for porcelain from Ex Nihilo has a very good chance of hitting Ceramics instead which no link telling them the proper name. And in the case of porcelain versus porcelain clay, they might as well be the same name, one just sounded redundant to me. –KnightMiner t/c 22:34, 15 April 2017 (UTC)
 * I've made my position fairly clear- in the case of a page like Vinegar, I'd rather Grape Vinegar be put into a "See also" section. I'm not explicitly against " (disambiguation)" pages, although I'm skeptical of its usefulness in the case of Porcelain (a simple About could be used at the top of Porcelain to link it to Porcelain Clay at most).
 * Also, something that's been brewing (well, more that's been brewed) at the back of my mind for a long time, since we're on the topic- I'm an advocate for disambiguation discrimination. Sounds pretty evil I know, but I think it makes sense. I don't think A) mods should have to disambiguate for items (like Engineer's Toolbox but not like Roots (Mod) or Aether (Mod)) B) Vanilla should have to disambiguate for modded stuff (like Dirt/Dirt (Witchery) but not like Granite) and C) material pages should have to disambiguate for anything else (don't really have any examples, but I'd argue there's not a Diamond material page because of disambiguation confusions). Wikipedia does something similar (ex. China and China (disambiguation)). I think would be logical. -Xbony2 (talk) 12:46, 16 April 2017 (UTC)
 * Most of that made no sense. --  Satanic Santa 🎅F T B Wiki Admin 16:10, 16 April 2017 (UTC)
 * I think what he said is...
 * If there is both a mod an an item that have the same name, currently we do  and   with   being the disambiguation, xbony2 is proposing   to be the mod page and   to be the disambiguation page. Under my overhaul I'd probably have   be the mod,   be the item (regardless of disambiguation), and   be the disambiguation.
 * When a mod has an item with the same name has vanilla, xbony2 is proposing  be the vanilla page   be the page for the modded version and   be the disambiguation. Under my overhaul it would be   and   with   being the disambiguation.
 * When a material has the same name as an item, xbony2 is proposing that  always be the material page with   being the disambiguation. Under my overhaul an alternative would be to have a pseudo mod for materials such as   so that   would always be the disambiguation/redirect.
 * 19:42, 16 April 2017 (UTC)
 * Well then I disagree with xbony and agree with you. --  Satanic Santa 🎅F T B Wiki Admin 23:47, 16 April 2017 (UTC)


 * You do realize a disambiguation page is literally an about for more results? All three of the unfired porcelain, the decorative block, and the Ex Nihilo version are able to be called simply "porcelain", thus that title needs to link back to all four pages. I would have skipped the disambig page if I had fewer items to redirect to, but 4 or more is the Wikipedia standard.
 * It is also why I had porcelain clay listed on Unfired Porcelain, as it is unfired porcelain as you might expect when looking for unfired porcelain had you not known the proper name (or played a pack where my clay came up first then played a pack with just Ex Nihilo). –KnightMiner t/c 01:59, 17 April 2017 (UTC)

Ah, I just remembered. If we as a community are deciding to include similarly named items in the same disambiguation page then Disambig's text will need to be changed as it currently says: "This disambiguation page lists articles associated with the same title."

- Template --SirMoogle (talk) 14:22, 25 April 2017 (UTC)
 * Addendum: Perhaps a new template can be created that resembles About so that instead of "This article is about X from Y. For other uses, see X" it'll state "This article is about X from Y. For similarly named pages, see Z"? --SirMoogle (talk) 14:27, 25 April 2017 (UTC)
 * Eh, I disagree. That is what the Wikipedia disambiguation template says (well, it says "associated with the title ") and I think it still makes sense. The key word is "associated," as "associated with" does not mean "equal to." --  Satanic Santa 🎅F T B Wiki Admin 19:54, 25 April 2017 (UTC)

Semi-merging of GregTech 5 Unofficial and GregTech 5
I propose the "merging" of GregTech 5 Unofficial and GregTech 5 content: moving everything in Navbox GregTech 5 Unofficial to Navbox GregTech 5 and making GT5U stuff be part of the same tilesheet as well. GT5U content should be noted as GT5U-only still, but it should not be segregated completely. GregTech 5 Unofficial has more or less been accepted as the continued iteration of GregTech 5 so I think this would be for the better, but at the same time I think any potential people that only use the official version wouldn't really be hurt by this. -Xbony2 (talk) 00:02, 4 June 2017 (UTC)
 * It may be a continued iteration, but they are still different which merging them doesn't show. If the navboxes were merged in any way, the extra things should be clearly labelled as part of GT5U not GT5, otherwise it doesn't make any sense to point out that it's different in the page. Really, just putting GT5U navboxes at the bottom of GT5 pages is probably sufficient (which could just be the GT5U navbox at the bottom of the GT5 navbox's template). As for tilesheets, keeping them split might be necessary to avoid GT6 style problems of having multiple sheets anyway for blocks/items/other things.  Chocohead Nag • Edits • Staff 01:00, 4 June 2017 (UTC)
 * From my minimal understanding they are still pretty different, so I agree with that they should not be merged. I think it could also be confusing because they are still separate mods and someone who downloads one might expect to see stuff from the other after looking at the wiki. --  Satanic  Santa 🎅F T B Wiki Admin 05:36, 4 June 2017 (UTC)
 * We should have a clear warning at the top of every GT5 page where the given item only exists in one of the two mods, regardless of whatever else we do. I do think both navboxes should be visible on all GT5/GT5U pages though, but it should be clear in the navboxes what stuff is only in GT5U and what stuff is in the original. As for tilesheets, I'm not sure whether I want to give GT5U its own full tilesheet, or just items which aren't in GT5. If any textures were changed in GT5U then that would provide more of a reason to give GT5U its own full tilesheet. 06:57, 4 June 2017 (UTC)
 * GregTech 5 Unofficial doesn't appear to change any textures (except maybe GUI textures but not in any official releases yet according to JohannesGaessler, but that doesn't affect the tilesheet obviously). I see GT5U as being the community-accepted continuation of GregTech 5 (like Nuclear Control 2 or Extreme Reactors), and that we should treat it more like that. Oh, and also it would be good to bring and maybe others into this discussion. -Xbony2 (talk) 15:31, 4 June 2017 (UTC)
 * Both examples you provided were separate updates for mods on new Minecraft versions, not full continuations of the same (if decompiled) code base for the same Minecraft version. Especially as there's scope for items in GT5 to be changed by GT5U, they cannot be considered the same the way you could with Nuclear Control for 1.6 and Nuclear Control 2 for 1.7. The only situation where what you suggest does apply is GT5U for 1.10 (which is another problem in itself), but that's still WIP whilst being slightly rewritten, so it probably isn't a concern right now.  Chocohead Nag • Edits • Staff 16:10, 4 June 2017 (UTC)
 * I don't really see why it has to be on a different Minecraft version as long as it's considered the de facto continuation by the community (which is perhaps debatable if the mod is, but I would argue it is, we could do a poll or something if necessary). -Xbony2 (talk) 23:21, 4 June 2017 (UTC)
 * A different Minecraft version at least separates the original mod out from the clone/continuation a little more, the fact GT5 and GT5U are so close together already means merging much further will make it quite hard to tell what is actually added in what. The difference between them is quite important too, as there are old packs that have GT5 in them (from back when Greg was still developing it), which obviously won't have the content from GT5U. Having the differing Minecraft versions means there is at least no doubt in which one you are running as there's no choice, in GT5's case there very much is.  Chocohead Nag • Edits • Staff 23:38, 4 June 2017 (UTC)
 * We can set it up where the differences are noted but at the same time they are together, where content that GT5U-only is marked as such. I don't think having separate navboxes would be particularly useful; someone looking for something from the original GT wouldn't be bothered that there's some things listed that aren't in their version, they'd just skim over it until they find what they are looking for. -Xbony2 (talk) 19:26, 5 June 2017 (UTC)
 * I would definitely be mildly annoyed having to figure out what things I could do with GT vs. GT5U instead of just going to the specific place for the specific mod I had installed. --  Satanic Santa 🎅F T B Wiki Admin 20:38, 5 June 2017 (UTC)
 * As long as the GT5U exclusives have their own section in the navbox to make it clear they're not part of the base GT5, every page for a GT5U exclusive has a notice at the top indicating its exclusivity to GT5U, and articles clearly document functionality changes between GT5 and GT5U, then that should be fine by me. 21:47, 5 June 2017 (UTC)
 * I think an average page should look like this. I don't think it is mildly annoying to use. -Xbony2 (talk) 00:07, 6 June 2017 (UTC)
 * What exactly does merging the GT5 and GT5U navbar and pages help? As i see it, it would only be more work with no real improvement. That work would be better invested in finishing the missing GT5U pages and GT5U addon stuff.--BloodyAsp (talk) 20:07, 8 June 2017 (UTC)
 * - I don't think it would be a lot of work, wouldn't take very long for us to do so it wouldn't really compromise any GT5U work (currently there's not really any work going on for it that could be compromised x.x having this discussion debatably would take longer than moving navbox content over or merging the tilesheets). As for the improvement, this would treat GT5U more like an updated version of GT5 rather than a one-off fork or an addon. -Xbony2 (talk) 21:35, 8 June 2017 (UTC)

FTB forums wiki section
Currently there is a wiki section on the FTB forums which is quite inactive. Should we keep the wiki section around or should we replace it with a redirect to a discussion page on the wiki (like this one)? Please provide your questions and comments and at midnight UTC at the end of July, a decision will be made based on the consensus of the community.

Comments

 * I personally think the wiki section on the forums serve no purpose anymore and should be replaced with a link to this page. 18:23, 27 June 2017 (UTC)
 * I personally think the public wiki section on the forums serves no purpose anymore. It should be replaced with a link to this page, and all discussions from the section should be archived here on the wiki. I think the secret section can be safely removed entirely. The secret removal should not be archived publicly as that violates the privacy of posters who posted under the assumption the public would never see their comments, regardless of the seriousness of the content. I don't think there's anything remarkably important there, anyway. --  Satanic Santa 🎅F T B Wiki Admin 18:27, 27 June 2017 (UTC)
 * Why is this section organized weirdly? A normal talk page comment would have been sufficient. Anyway... I agree that the two sections on the FTB Forums are basically useless. Everything should be archived. The public stuff could be archived to Feed The Beast:Public forum archive or something (that's a bad name, someone suggest something better). I would like the private stuff to be archived publicly, but I realize this is unrealistic and inappropriate for the reason Santa provided. From what I've seen, ~90% of the stuff I think would be fine if made public but without consent from everyone (which is obviously impossible, since most of the people there have moved on, some of them have disappeared completely, some have been banned from FTB, and for all I know some have literally died) it still would not be appropriate. Perhaps some portions of it could be archived publicly if it was uncontroversial and maybe interesting, like old guides and whatnot; I don't think that it would be a big deal for some certain stuff. Also it should be noted I would like access to the private archive. -Xbony2 (talk) 19:35, 27 June 2017 (UTC)
 * For discussions involving parties we can still contact, we could request consent to archive them publicly. --  Satanic Santa 🎅F T B Wiki Admin 19:48, 27 June 2017 (UTC)
 * Those discussions are few and far between from what I've seen, imo such a goose-hunt would be a meh use of time. It's sad that there's like ten times more retired staff than would-be staff now, although to be fair, as Retep pointed out, you had to be staff in order to edit the wiki in the old days so they were a lot more liberal with it (until a lot of them got kicked out for not doing much, of course). After looking through the private archive, I found only like two things useful, one the enchanting JS stuff which you (Santa) mentioned in IRC, and the other this quote which I just leaked as you can see (really doubt Denkbert would care, if he minds he can sue me and I'll plead guilty). -Xbony2 (talk) 01:17, 28 June 2017 (UTC)
 * End of July, why not at the end of June? -- Indestructible Pharaoh VII  20:46, 27 June 2017 (UTC)
 * Because the forums are so inactive that we need to give people plenty of time to respond. 20:49, 27 June 2017 (UTC)
 * 3 Days are more than enough imo. You can also extend it to July 15th, but not til the end of July for something inactive. - Indestructible Pharaoh VII 20:52, 27 June 2017 (UTC)
 * I don't think anyone from the forums and only the forums will be replying :P -Xbony2 (talk) 01:19, 28 June 2017 (UTC)

Results
Well, with such a huge turnout it was quite difficult to come to consensus. It seems we all pretty much agree: Replace the section with a link here, and archive the pages here. As for the private ones, we can archive some of them here but probably not many. I will get in contact with FTB about this and will begin archiving ASAP. --  Satanic Santa 🎅F T B Wiki Admin 23:12, 3 August 2017 (UTC)
 * The base public section has been archived at Project:Public forum archive. However we never actually discussed the news section. Whoops. --  Satanic Santa 🎅F T B Wiki Admin 00:49, 4 August 2017 (UTC)

List of alias worth creating
(See ) Generally I don't think everything renamed ever needs an alias, just stuff where multiple aliases would be used because of older versions and whatnot. -Xbony2 (talk) 01:42, 5 July 2017 (UTC)
 * Stained Clay/Hardened Clay/Terracotta
 * IC2's Machine Block
 * Probably other stuff

Move proposals for Chisel
Wouldn't it be better to create an infobox that displays all the different decorative blocks instead of creating an entirely new page for them? Most of them don't add any new functions and are purely decorative and I don't think that warrants getting a page created. --SirMoogle (talk) 05:25, 4 August 2017 (UTC)
 * Nah, I think Oak Wooden Planks (Chisel) (or whatever) should have all of the chisel variations instead of hijacking a Vanilla page. We have plenty of pages for decorative variations, it's not a big deal. -Xbony2 (talk) 11:27, 4 August 2017 (UTC)
 * Agree --  Satanic Santa 🎅F T B Wiki Admin 15:45, 4 August 2017 (UTC)

Separation/disambiguation of Chisel
I think that the Chisels should be treated as one mod, or at least not as six. For example, I believe that asie's port has zero difference with the original mod, other than who the mod author is and the Minecraft version. I think separating the mod, in this case, is absurd. KnightMiner and Hubry have advocated different views, but disagrees. We need to discuss how we should treat Chisel with regards to all of its forks. sorry if my grammar/spelling is off, I'm on mobile, wikiing is hard on mobile -Xbony2 (talk) 19:44, 6 August 2017 (UTC)
 * Infoboxes would have been nice How about just making sections for each different Chisel mod on one unified Chisel page for a block? --SirMoogle (talk) 22:11, 6 August 2017 (UTC)
 * I'd probably like that. I think we should do some research on the difference in each Chisel version. Antillar suggested having it Chisel 1 and Chisel 2 (1 for AUTOMATIC_MAIDEN, asie, Pokefenn, 2 for TheCricket26, Delta534, Chisel Team). Going to ask about differences in Chisel forks. -Xbony2 (talk) 23:00, 6 August 2017 (UTC)
 * According to tterrag...

-Xbony2 (talk) 23:28, 6 August 2017 (UTC)
 * My opinion on this is exactly the same as my opinion on putting GT5U and GT5 together. I don't think we should be special casing mods because they are similar. tterrag even listed some changes that some forks made. I think that's plenty of reason to keep them separate. --  Satanic Santa 🎅F T B Wiki Admin 16:18, 7 August 2017 (UTC)
 * "Changes" as in decorative block changes? I think it'd be helpful for readers to see all the decorative blocks of that particular block all the Chisel mods have made on one page instead of browsing through multiple pages trying to compare aesthetics amongst different Chisel versions. If "changes" mean functionality or something else, that should be reflected under the appropriate section heading or on the mod's page if it's a significant change. --SirMoogle (talk) 16:41, 7 August 2017 (UTC)
 * I still think that could be confusing. We don't do this for the Advanced Machines forks so why should we for Chisel? --  Satanic Santa 🎅F T B Wiki Admin 16:47, 7 August 2017 (UTC)
 * They aren't similar mods, they're the same mods. They don't magically become a new mod because someone forks it. The main difference between them is that the newer versions have more content. It should be treated as the same mod, just continued by someone else, because that's exactly what it is. I do not plan to disambiguate The Mists of RioV and my short-lived fork of it simply because I added a Bonyium Ingot to it and fixed a few bugs. One way to document the history is to have a section listing each variation (which would be pretty useful anyway and we should do anyway) that would something like this:

(On Birch Wood (Chisel))

Variatons
For an otherwise empty decorative page I do not think this would have much clutter. -Xbony2 (talk) 00:14, 8 August 2017 (UTC)
 * Smooth (Added in 2.5.0 (asie's fork))
 * Planked (Added in 2.5.1 (Pokefenn's fork))
 * That works, but I was thinking more along these lines:

== Chisel (earlier fork) == list variations == Chisel (later fork) == list variations
 * Such that later forks have their own new blocks added without redundantly putting the old ones into the new section as well. --SirMoogle (talk) 02:00, 8 August 2017 (UTC)
 * That would be a lot of sections and a lot of repeat, though. -Xbony2 (talk) 02:10, 8 August 2017 (UTC)

Isometric renders for mobs
Following the Minecraft Wiki's style guide for entity renders it could be possible to give all mobs a proper isometric render instead of just the Spawn Egg and some screenshots. Example with the Twilight Forest Ur-Ghast.

If you want to try it, install Mineshot (go Releases and pick the correct jar for your version), make a void superflat void (or with Barriers that's easier), spawn the mob with {NoAI:1}, press Numpad 5 to toggle the isometric camera (there are other controls shown in the github page) then take a screenshot, erase background and crop in some image editing software.

We'd probably need to agree on roughly what size to shoot for on the pictures (since monsters have different sizes can't really use the same zoom for everything), and also maybe get some big list of TODO articles if we do agree on doing that for all of the mob articles. Lykrast (talk) 22:42, 2 November 2017 (UTC)
 * I support this as long as the backgrounds are transparent. What if we had the renders for the infobox image (still having the spawn egg as the infobox imageicon) and then proper "natural habitat" images in the article body? That makes sense to me personally. --  Satanic Santa 🎅F T B Wiki Admin 19:17, 3 November 2017 (UTC)
 * My first attempt is rough.
 * [[File:Buffalo experiment.png]]
 * I would like this however. I'd prefer if BlockRenderer added a mob dumping feature but I don't know how easy that would be. -Xbony2 (talk) 20:55, 3 November 2017 (UTC)
 * Worth mentioning that Better Questing can display a list of all registered entities along with a rotating 3 render in its quest making UI (maybe worth mentioning in that GitHub issue ?). Although until then we can still do it manually, would require a precise step by step tutorial for it though to be sure everything is in about the same style (void world (for uniform blue background) + {NoAI:1} + Mineshot's isometric camera + screenshot + delete background with magic wand or something seems like a real good start for it). Lykrast (talk) 21:04, 3 November 2017 (UTC)

Infobox list standards
We all know how much I love standards. So let's standardize lists in infoboxes. I have set up on a subpage of my userspace 5 potential standard formats for all lists in all infoboxes. All infobox lists will be standardized the same way, so the style used in Infobox mod will be the style used in Infobox material, etc. Vote for your preferred style and we'll narrow it down and pick a standard, and then we get to go around updating everything! Fun shit. Alright. Vote by using. If you would prefer we discuss stuff I guess we can do that but I mean really this is pretty trivial so I don't really see the need in that. Let's have a standard by next Monday maybe. --  Satanic Santa 🎅F T B Wiki Admin 02:40, 9 January 2018 (UTC)
 * --  Satanic Santa 🎅F T B Wiki Admin 02:40, 9 January 2018 (UTC)
 * --SirMoogle (talk) 04:11, 9 January 2018 (UTC)
 * 04:19, 9 January 2018 (UTC)
 * -- sokratis 12GR  Staff  09:30, 9 January 2018 (UTC)
 * . I've been treating that as the unwritten standard for years now and changing everything else (which has been pretty much only A) into it. Really don't like A/B/C. -Xbony2 (talk) 12:28, 9 January 2018 (UTC)
 * , it looks best IMHO. -- Hubry  (talk) 20:47, 10 January 2018 (UTC)
 * , Simple is best. Crazierinzane

Results
Wow I suck and did not follow up with this. D won by 3 votes and sokratis, who voted also for C and E, said he preferred D over the other two. I've added the standard to the Manual of Style. --  Satanic Santa 🎅F T B Wiki Admin 22:18, 27 March 2018 (UTC)

Registry and unloc names in infoboxes
As seen on this page, including the entire registry name and unloc name makes infoboxes really wide and kinda ugly. I propose cutting the mod ID prefix from the registry name (it is implied that it is the mod ID) and removal of unlocalized names (since they are basically unusable by users, only by modders, translators and pack creators). -- Hubry  (talk) 04:37, 21 January 2018 (UTC)
 * I am in favor of trying this. -Xbony2 (talk) 16:28, 21 January 2018 (UTC)
 * The unlocalized name I don't care for. The registry name is useful to have and should be kept, but the modid part can be removed since the modid can be inferred from the mod the item is from (and should be documented in the infobox for the mod itself). 20:49, 21 January 2018 (UTC)
 * Not every mod correctly names their stuff, though. Twilight Forest, as I recall, does not include the mod ID in its unlocalized names and instead prefixes everything with "TF". --  Satanic Santa 🎅F T B Wiki Admin 23:50, 21 January 2018 (UTC)
 * Hubry was a bit more specific on Discord and proposed the prefix be included if it was odd. -Xbony2 (talk) 00:08, 22 January 2018 (UTC)
 * I believe Santa is talking about unlocalized names, where there's basically no convention anyway. And unlike registry names, which are used by any command interacting with blocks/items and visible to the user through, the only time you ever see unloc is if you are digging in localization files and mod's source. They are ugly and useless here. -- Hubry  (talk) 00:14, 22 January 2018 (UTC)

The FTB Wiki at Modoff


Me,, and are representing the FTB Wiki at Modoff 2: Reforged! In case you don't know what it is, Modoff is a modding competition where participants are tasked to make a mod in a 9 day period (similar to ModJam). Me, Hubry, and Immortal, and any other interested editors, are sponsoring the event by documenting the top three mods from it (plus perhaps any mods we particularly like). The Modoff server is open right now for modders to display their creations and for viewers to vote on which one(s) they like the the most. We have our own plot as well, as you can see above, and I highly encourage you to visit it. A lot of the mods are real cool, and I spent a good bit of time working on our booth and it actually turned out pretty good so yeah. On February 18th, the results of the competition will be released, and me/Hubry/Immortal/any interested editors will start documenting the top three mods shortly after. Their website has issues so here is a link to a Reddit announcement with a bit more info. -Xbony2 (talk) 22:15, 8 February 2018 (UTC)
 * Modoff is over! The top three winners are Glacidus, Gaspunk and E-Vaporate. Me, Hubry, and ImmortalPharaoh7 intend to split them up somewhat (currently plan is Glacidus is jointly documented by me and Immortal, Gaspunk is documented by Hubry, and E-Vaporate is documented by me). If you are interested, and you might be, in documenting any mods from Modoff, I certainly encourage you to. Most of the mods made were pretty cool imo. Hubry said he's definitely going to document Dazzle, and I see myself documenting End: Reborn. Everything is up for grabs of course if you are interested; just go for it. -Xbony2 (talk) 15:23, 18 February 2018 (UTC)
 * Sorry Hubry I documented Dazzle --  Satanic Santa 🎅F T B Wiki Admin 23:52, 21 February 2018 (UTC)
 * Pressurized Defence is done --  Satanic Santa 🎅F T B Wiki Admin 19:56, 22 February 2018 (UTC)
 * End: Reborn is done --  Satanic Santa 🎅F T B Wiki Admin 22:31, 10 April 2018 (UTC)

Quest Book template
I was thinking having a template that shows a Better Questing page and quests would greatly help pages of quest based modpacks. Each quest on it would have coordinates on its placement and a hover tooltip to show its name, quest requirements and maybe some extra info. Pushing the idea further it could probably be possible to make a script to directly import Better Questing quests from a config (they have coordinates, requirements, name and all, the icons would probably be very problematic though). Lykrast (talk) 15:01, 24 March 2018 (UTC)

"Minecraft versions" infobox mod parameter
I would like to propose we add a new parameter to the mod infobox, "Minecraft versions" which would list every version it has been released for. This would also entail adding new categories automatically like "Mods released for Minecraft 1.7.10" etc. I have already implemented it at User:TheSatanicSanta/Sandbox/Version categories, just needs to be added to the infobox and moved to a proper template. I also would like to propose having a category on each mod page indicating the latest MC version (also automatic from the mcversion parameter), but nobody has responded to this idea really at all so I dunno. Please discuss this so we can come to a collective consensus. One improvement I could see would be wrapping it in a spoiler (maybe do it depending on how many are passed), but I'm not very attached to that. --  Satanic Santa F T B Wiki Admin 21:30, 5 April 2018 (UTC)
 * We should do this. I am against the spoiler idea though.
 * What it’s released for doesn’t seem as useful as what it works with; people looking at a 1.7.10 category would be missing stuff that was released for 1.7.2 even though that would be perfectly valid/working in a 1.7.10 modpack or whatever. Also you need an example on overdrive, like BuildCraft. -Xbony2 (talk) 22:36, 5 April 2018 (UTC)
 * I guess we could do it in the lead section for each mod, saying which version it started off on. A lot of mod navboxes go with the most recent iteration anyway. --SirMoogle (talk) 03:39, 6 April 2018 (UTC)

Infobox tree
I worked on an infobox for trees idea, to concentrate tree related informations a bit like materials. I made the Menril tree from Integrated Dynamics and the Apple Oak from Forestry in my sandbox to test and show them. The idea behind it is that each tree (and it's "mundane" products like planks or logs that don't do anything special) would only have a single page for that, instead of the tree info being in the sapling page and having some blank log, leaves, planks pages. Some stuff like the fruits may still need their own pages I think.

What it gives :
 * Name, image (pretend the ones in the sandbox have actual images) and mod of the tree
 * Forestry genes (for Forestry trees)
 * Natural blocks that form the tree itself (log, leaves and sapling)
 * Drops that aren't natural blocks ("fruit", Forestry pollen and an Other Drops field)
 * Products from its wood (all vanilla ones (planks, slab, stairs, door, fence, fence gate and boat) as well as an Other Products field)

Want to know what the other thinks before rolling it out to actual pages. Lykrast (talk) 17:53, 25 April 2018 (UTC)
 * Sounds really cool. One suggestion I have is to include information on how wide the leaves grow so people can space their saplings apart appropriately. There might also be some other bits of information necessary for at least GT6 trees. I guess one of the first things we should try it on is the GT6 tree articles. 18:35, 25 April 2018 (UTC)
 * I've added trapdoor (Quark and 1.13 adds them), bookshelf (Quark and GT6), beam and panel (for GT6). Luckily GT6 doesn't seem to add much that cares about the tree type. For the demonstration, I've also added other stuff from Quark for the oak (like the bark and carved wood). Lykrast (talk) 19:33, 25 April 2018 (UTC)
 * I like it. I agree with Peter though that the size of the leaves would be useful. --  Satanic Santa 🎅F T B Wiki Admin 21:05, 25 April 2018 (UTC)
 * I've added an "average width" and "average height" field filled with estimates. Most trees don't vary that much so this should be good enough for most of them. Lykrast (talk) 22:43, 25 April 2018 (UTC)