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)

Official wiki renaming proposal
I propose for the renaming of this wiki from the "Feed The Beast Wiki" to the "Feed The Beast and Modded Minecraft Wiki" (FTB&MM Wiki for short). Originally when this wiki was created, it was purely an FTB Wiki. This is no longer the case. This wiki has been open for all of Modded Minecraft for a very long time, and I think it's appropriate our name reflects that.

Our rival wiki, ftbwiki.org, did something similar to this almost two years when they turned their wiki into an FTB/ATL Wiki rather just an FTB Wiki. However, I think adding other specific modpack names for us would be too exclusive, as there are many more modpacks and mods outside of Feed The Beast and ATLauncher and other popular mod ecosystems, hence why I'm proposing it be "and Modded Minecraft" rather than "and ATLauncher" or "and Technic" or other options.

According to my survey, 44% of our users don't use the FTB Launcher, 75% don't use Curse, and 30% don't use either. For the amount of users who don't use FTB, you can round that number up a fair amount if you consider that Curse (and also the FTB Launcher) don't exclusively host FTB packs. This wiki is marketed as a "Feed The Beast Wiki", even though it's more of a general Modded Minecraft wiki. Like I've said, we've been very welcome to the documentation of mods outside of FTB for a long time, and I think it's important we reflect that to potential editors and viewers that may not think of us as that.

Lastly, this allow us to do a proper "merge" with Modpedia, which is something that has been discussed in IRC and the Gamepedia Slack for a while but hasn't been done yet.

To clarify, this is a request to change the website name and how we refer to it. This does include this namespace (we'll probably make "Feed The Beast Wiki:" redirect to "Feed The Beast and Modded Minecraft Wiki:") and how the name will display in certain places (like the "wikis" section of the Gamepedia main page) However, I do not want to change the url of this wiki and the location of the main page (although I would like to update as well as improve the main page). -Xbony2 (talk) 13:53, 5 November 2016 (UTC)


 * I don't like to change the name since it is too long (that is my first opinion without thinking much about that subject). - Indestructible Pharaoh VII 14:07, 5 November 2016 (UTC)
 * I noticed that too, but it's not like "Feed The Beast Wiki" is already pretty long. You can still call it the FTB Wiki, or the FTB&MM Wiki, or the Modded Minecraft Wiki, or whatnot, it's just that we'd refer as the Feed The Beast and Modded Minecraft Wiki formally. -Xbony2 (talk) 14:23, 5 November 2016 (UTC)
 * I have no problem with changing the wiki name, however I'd strongly prefer something that isn't too long. Also, we'd need to have it approved by FTB to make sure they're okay with it. 15:37, 5 November 2016 (UTC)
 * We should be either FTB/Feed The Beast Wiki or MM/Modded Minecraft Wiki, not both. Also what Peter said about talking to FTB (mainly Slow, Quetzi, and Tfox). --  Satanic Santa 🎅F T B Wiki Admin 04:32, 6 November 2016 (UTC)
 * Combing them both allows us to still have a focus on FTB while at the same time not being exclusive. I don't see why it has to be either or :P I do get that it's rather long, there's not many wikis that we can compare with. It's worth investigating if we can use something smaller, like "Feed The Beast Wiki and Modpedia", but I don't really like the sound of that. -Xbony2 (talk) 10:17, 6 November 2016 (UTC)
 * Probably more like Feed The Beast and MineModPedia Wiki? (I know I am good with coming out with names :P). Indestructible Pharaoh VII  07:10, 8 November 2016 (UTC)
 * That sounds rather silly :P -Xbony2 (talk) 12:00, 8 November 2016 (UTC)


 * I'm just curious about why do we even consider a merge on a wiki that has ~200 articles (compared with the 13k articles on here), and the last edit was made about two weeks ago. On the other hand, I don't agree that the wiki should cover all the mods for minecraft, as there's problems even covering the ones that already are available on FTB alone, such as forestry or Thermal Foundation are kind of outdated, with no mention on popular but not so complex mods such as Extra-utils or decocraft, that integrate most of the official Modpacks of FTB, but yet we don't have pages for their mechanics or items that come with them. Frenchiveruti (talk) 01:56, 13 November 2016 (UTC)
 * We already DO aim to cover all mods for minecraft. That's kind of a pillar of this wiki, although FTB is somewhat of a focus (or it should be, ultimately people document what they want to). We're never going back to the dark ages of being only FTB :P Anyway, the reason I want to merge the Minecraft Modpedia with here now, even though it's tiny, is because it would very much easier to do now, while it is easy to do and small, instead of when it has a large content base, since it would be very complicated to do so then, which could potentially happen if we don't do this now. -Xbony2 (talk) 02:22, 13 November 2016 (UTC)
 * It's worth noting "merging" at this point basically means making the entire wiki redirect to this wiki, since there's no content worth moving over :P -Xbony2 (talk) 02:24, 13 November 2016 (UTC)
 * I see, well, what about if instead of naming "and modded minecraft" FTB, like separating the terms, we integrate the fact that the modded minecraft experience it's intrinsic to FTB, as Modded minecraft probably wont be able to distribute its mods in other platform that it isn't curse. Just to be clear on what I mean, FTB IS modded minecraft, but modded minecraft isn't necessarily FTB as there are mods that don't form part of FTB official packs. Frenchiveruti (talk) 02:41, 13 November 2016 (UTC)
 * Not entirely sure what you mean :c -Xbony2 (talk) 12:57, 13 November 2016 (UTC)
 * For the record both DecoCraft and Extra Utilities have some very basic documentation here. I started DecoCraft a while ago, but it was really redundant and boring so I stopped. ExU was being documented by someone who I can't remember off the top of my head. --  Satanic Santa 🎅F T B Wiki Admin 18:08, 13 November 2016 (UTC)
 * It was Warlordjones, although other users have contributed a bit here and there. Currently nobody caries that torch, although I might aim to document Extra Utilities 2 since it's very different. -Xbony2 (talk) 20:42, 13 November 2016 (UTC)

Wiki renaming proposal 2
Yes, I'm going to revive this proposal. Most of you guys opposed the original on the account of it being too long. Although, I have another opposition to add of my own- being FTB-focused. If we were, say, going to collaborate with another major modpack, they might not want to be under that banner. Not saying I have something planned, but who knows what is in store for the future? Anyway, that's why I propose this wiki be renamed to the "Modded Minecraft Wiki". It's short. It's direct. And it doesn't hurt that it might be the first thing that comes up when you google "modded minecraft wiki" :P certainly is pretty marketable.

Anyway, just to extend this a little bit, I'd like to propose a little something more. To keep the FTBness of this wiki, I'd like to suggest the addition of a "Portal:" namespace. The main page we currently use would be moved to "Portal:Feed The Beast". Potentially there will be other portals too- I definitely have "Portal:ATLauncher" and "Portal:Technic" in mind, but there's also potential for portals for specific mods or maybe other future concepts. The regular main page would include a blurb about modded minecraft, a few links to the main portals, and an expanded mod list. I'll try to make a conceptual version in my userspace I suppose. -Xbony2 (talk) 22:36, 21 January 2017 (UTC)
 * I don't know if I have any say in this but here are my two cents anyway. I discovered this wiki (well, I discovered the unofficial one first) not because I was playing an FTB pack (it was an unofficial technic pack), but because I was playing with a mod that I wanted to learn more about. What was the first thing I found when searching for that mod or item in the mod? These FTB wikis. They generally seem to come up as the only wikis pertaining to Modded Minecraft unless the mod itself has a wiki of its own. I feel like this renaming would take that extra step to place the wiki in the spotlight of the Modded Minecraft community forever. Crazierinzane (talk) 23:52, 21 January 2017 (UTC)
 * I am personally fine with the name "Modded Minecraft Wiki". I really do not want to name it "Modpedia" (Benjamin mentioned that in a private convo I had recently; that name sucks). We have to talk with the Gamepedia people (really we should just talk to Benjamin about it). Benjamin said he would "put out some feelers and try and get some info from within Curse" and the Curse people that work with the core FTB team. We also have to discuss this with Slow though I doubt he'll care one way or the other. I can do that if you don't want to. --  Satanic Santa 🎅F T B Wiki Admin 00:54, 22 January 2017 (UTC)
 * I really have no idea what to expect from slowpoke or the FTB team. It would be good to do it as a team (multiple people arguing can create a very good persuasive effect), but if you don't think he'll get in the way you can take care of it. -Xbony2 (talk) 01:48, 22 January 2017 (UTC)
 * It's hardly like they're very attached to the wiki, we're very infrequently mentioned (if at all by FTB itself). It's not even like we even focus on documenting the mods that are in FTB packs anyway.  Chocohead Nag • Edits • Staff 02:03, 22 January 2017 (UTC)
 * I probably would document their mods if they ever gave a shit about us. We've never been mentioned in their news (even when I explicitly told them every time we had newsworthy shit happen), and none of the important things I've requested (giving us easy access to up to date MineTweaker scripts without having to download their entire modpacks, attempting to get editors, etc.) have ever been done. --  Satanic Santa 🎅F T B Wiki Admin 02:07, 22 January 2017 (UTC)
 * We'll still serve as the Official FTB Wiki, it's just that we'll be more :P -Xbony2 (talk) 02:09, 22 January 2017 (UTC)

A new main page might looks like this, btw. Obviously I'm not a web designer, but you can at least get the idea. I'd like it if the links at the top were images instead of just text, but maybe that can be done later. The main portals put forth are "ATLauncher", "Feed The Beast" and "Technic", the most biggest modpack groupings. I wouldn't add any more, unless something else becomes especially popular in the future or if we partner with someone. -Xbony2 (talk) 04:02, 22 January 2017 (UTC)

Logo
If we're going to rename and remarket our wiki, we're going to need a new logo. If anybody wants to play around and design something, go ahead and throw it here :P -Xbony2 (talk) 01:08, 30 January 2017 (UTC)
 * Give me a general theme/concept and an idea of what sort of color scheme you'd like to see, and I'll see if I can cook something up. Do need at least some starting point for an idea from the rest of you. DSquirrelGM &#120035;&#120031;&#120018; 02:48, 14 February 2017 (UTC)
 * Well, since I can't seem to get any suggestions on the logo, let's try a different approach... Which of the following ideas would you prefer to see?


 * 1) Design based on an anvil with text stamped or chiseled into it
 * 2) A representation of various production machines stacked side to side or staggered like stairs
 * 3) Command block as a background with various tools and weapons in the foreground
 * Or suggest some alternative based on these suggestions. DSquirrelGM &#120035;&#120031;&#120018; 03:49, 16 February 2017 (UTC)
 * All my ideas involve rabbits. 03:46, 16 February 2017 (UTC)

Renaming the wiki to the "Modded Minecraft Wiki" vote
I think everybody agrees with it (or doesn't care), but because it is a big change, I'd like to do this the formal way. This vote is on renaming and remarketing the wiki from the "Feed The Beast Wiki" to the "Modded Minecraft Wiki". Keep in mind this not a change in policy- this wiki has long been more of a general modded Minecraft, and it's allowed for non-FTB mods for years now. A large amount of our users don't play FTB modpacks at all, and I'd say most of our editors don't either. This change should allow us to be more marketable to potential editors and partners who don't want to be under the FTB banner. For a bit more on that, go through the discussion and  discussion. This vote will end in one week. If passed, we'll send a message to Gamepedia to proceed.

Support

 * 1) . -Xbony2 (talk) 10:06, 4 February 2017 (UTC)
 * 2) . Then no problem with that :P - Indestructible Pharaoh VII  10:36, 4 February 2017 (UTC)
 * 3) . -- sokratis 12GR   Staff  10:48, 4 February 2017 (UTC)
 * 4) . - Moritz 30 German translator 18:52, 5 February 2017 (UTC)
 * 5)  I spoke with Benjamin from Gamepedia a while ago and he says the Gamepedia folks support the change. It would require a complete overhaul of the main page, which Benjamin briefly described in private with me. Slowpoke also supports it, basically as long as we don't document the Jadedpacks– fortunately those were never intended to be documented here, but instead to just link straight to Jaded's wiki. It should be stated somewhere on the main page that we are still the official source of information on FTB content, though. I propose we change the name of the wiki to "Modded Minecraft Wiki" and the URL to "moddedmc.gamepedia". Once this is all done (as in, the wiki is renamed and the main page is redesigned), we can begin working with Lordofediting and the rest of Gamepedia to transfer any content from modpedia that was not copied from here over here, and then deprecate/delete that wiki to prevent segregation. --  Satanic  Santa 🎅F T B Wiki Admin 19:13, 6 February 2017 (UTC)
 * *cough* sample-ish main page here.
 * I want to argue against the subdomain "moddedmc.gamepedia". "MC" just seems like a shitty partial abbreviation. Maybe "moddedminecraft.gamepedia" (15) is long, but it wouldn't be the longest subdomain- pillarsofeternity.gamepedia.com (17), totalwarwarhammer.gamepedia.com (17), strongholdkingdoms.gamepedia.com (18), orcsmustdieunchained.gamepedia.com (20), civilizationbeyondearth.gamepedia.com (23), everybodysgonetotherapture.gamepedia.com (26), legostarwarstheforceawakens.gamepedia.com (27), loversinadangerousspacetime.gamepedia.com (27) to name a few. Other alternatives could include "mm.gamepedia.com" if we wanted to go short, maybe "modminecraft.gamepedia.com"? (I really don't like that one tho) -Xbony2 (talk) 22:29, 6 February 2017 (UTC)
 * I think all of those URLs you proposed are ew. Perhaps we should see what Gamepedia people think? --  Satanic Santa 🎅F T B Wiki Admin 02:54, 7 February 2017 (UTC)
 * Aye, and/or if anybody else has any ideas. I'm learning towards "mm" myself, although I will admit I am not 100% satisfied with that option either -Xbony2 (talk) 11:54, 7 February 2017 (UTC)
 * I'd lean towards moddedminecraft.gamepedia.com. CrsBenjamin (talk) 17:24, 17 February 2017 (UTC)
 * 1) . Slowpoke is okay with it, Gamepedia is okay with it, therefore I am okay with it.  21:53, 6 February 2017 (UTC)
 * 2)  I'd lean more towards "minecraftmods.gamepedia.com" for domain name. DSquirrelGM (talk) 17:35, 7 February 2017 (UTC)
 * I don't think "minecraftmods" is all that accurate because we document, and plan to document, quite a bit more than just mods. --  Satanic Santa 🎅F T B Wiki Admin 18:00, 7 February 2017 (UTC)
 * True. I thought about that name myself, although I didn't suggest it because it doesn't match the name of the wiki as a whole (Modded Minecraft Wiki), which I think is important. -Xbony2 (talk) 21:07, 7 February 2017 (UTC)
 * 1)  T3==ThaumicTechTinker, Urey.S.Knowledge Welcome back, commander 23:00, 7 February 2017 (UTC)
 * 2) . Good idea ! --LuminousLizard FTB Wiki Staff de-N / "en-2" (talk) 18:15, 24 February 2017 (UTC)
 * 3)  Why the hell not?  LordofEditing  =( Talk )= ''' 21:20, 5 March 2017 (UTC)

Neutral

 * I'd rather we confirm whether FTB peeps are okay with this before making a decision here. 21:08, 4 February 2017 (UTC)

Discussion
Would we still be the Official FTB Wiki? Meaning that we are still FTB's official wiki? - Indestructible Pharaoh VII 10:32, 4 February 2017 (UTC)
 * Yes (unless they change their mind, but I doubt that they will be dicks about it). -Xbony2 (talk) 10:34, 4 February 2017 (UTC)
 * I still have not talked with slow or tfox or anyone high up in the FTB bureaucracy about it. Bony did you or are you just assuming they'll be fine with this? --  Satanic Santa 🎅F T B Wiki Admin 21:03, 4 February 2017 (UTC)
 * I am saying if they do not agree that it will not be their call. Nowadays, they don't host us or manage us any more than Microsoft does the Minecraft Wiki. Now, I don't want to be a jerk to them, but we will be jerks if necessary. But I don't think we'll have to. -Xbony2 (talk) 21:36, 4 February 2017 (UTC)
 * And an update on this- slowpoke has stated he is okay with this, as long as we generally focus on FTB modpacks (which I generally plan to do), and also that we don't include modpacks that contain mods without consent from the mod author(s) (with a few exceptions for the historical Technic packs), which I think is reasonable. -Xbony2 (talk) 23:10, 4 February 2017 (UTC)
 * What about creating a new wiki as modded Minecraft wiki? - Moritz 30 German translator 18:54, 5 February 2017 (UTC)
 * Sure, take all the years of hard work and start over at a new wiki. - Indestructible Pharaoh VII 18:57, 5 February 2017 (UTC)
 * Maybe one could copy articles over but I think this wiki should still be focused on FTB modpacks and not small mods. Documenting small mods is good, however I don't think it should take place in a large scale here. This wiki is optimized for FTB modpacks and large mods but not really for small ones. - Moritz 30 German translator 19:07, 5 February 2017 (UTC)
 * Creating a new wiki just segregates the community even more, makes it a royal pain in the ass for users to find documentation, and doesn't even make sense because we've already been documenting non-FTB mods for at least a year. The wiki isn't "optimized" for any specific set of mods; it works fine for any number of mods. --  Satanic Santa 🎅F T B Wiki Admin 20:01, 5 February 2017 (UTC)
 * It's optimized for all the mods \o/ -Xbony2 (talk) 02:33, 6 February 2017 (UTC)
 * BTW what will happen with the old existing links and pages that linked to this site ? will the other URL redirect them here ? -- sokratis 12GR  Staff  12:11, 7 February 2017 (UTC)
 * If the url is changed, the old url will redirect to the new url. Links will not be broken. 12:20, 7 February 2017 (UTC)

Final Decision
This has been supported unanimously. It'll take a while to fully update everything, and for Gamepedia to do their part. In the meantime, we can probably work on making some base documentation on other modpacks or making new portals or whatnot. Also above this, we need to decide on a logo (I really don't like Modpedia's logo, no way we're going to be using that) and other stuff. -Xbony2 (talk) 17:12, 11 February 2017 (UTC)


 * Here's a list of things that need to happen:
 * Decide on Wiki Name
 * This seems to have consensus as "Modded Minecraft Wiki"
 * Decide on URL
 * There seems to be some discussion, but best practice would be to use the wiki name, so moddedminecraft.gamepedia.com
 * Create a logo
 * I can get assistance from Curse's design team if its necessary, with about 1 week lead time. But there would need to be a fairly clear idea of what was wanted.
 * Mock up new main page
 * I think someone had started on this, but happy to get some help from our wiki team as well if its desired.


 * Once all of these things are ready, then we can set a date to make the changes, which we'd be happy to support via social media, etc. We're excited about this. Even though the wiki has covered mods of all varieties for some time, I think this change will be a great move towards making it really clear what the project's mission is. We get not infrequent requests for wikis for minor mods, and its been a little confusing to people sometimes for us to send them to "FTB Wiki". CrsBenjamin (talk) 17:31, 17 February 2017 (UTC)
 * - I'd rather not set a date currently so we don't have to rush. I'd like to work a bit more on making a few pages to bind everything together before calling one. By the end of the month is entirely possible, though. -Xbony2 (talk) 22:38, 18 February 2017 (UTC)
 * Sorry for the late reply. But yeah, definitely no rush, I just mean once everything is ready we'll want to coordinate. CrsBenjamin (talk) 17:04, 24 February 2017 (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)

When two items are merged in one
Ender IO in 1.10 has removed Redstone Conduit and given what used to be Insulated Redstone Conduit (the version that handles bundled redstone channels) that name. What's the correct way to handle the pages? Lady Oolong (talk) 17:05, 26 February 2017 (UTC)
 * Sorry for the late reply. described the solution in the Gamepedia Slack

"Different sections for different versions most likely

The page would describe the latest logic then have a section below it describing legacy"

-Xbony2 (talk) 22:11, 26 February 2017 (UTC)

Giving editors translators markup rights
Hello, it's me ImmortalPharaoh7, and I have something that has been bothering me and I want to change it; markup rights for editors translators. Benefits:
 * 1) Allows editors translators to be able to markup pages and not wait for an admin to mark it up after adding tags.
 * 2) For lua navboxes, marking it up will allow editors translators to see their changes without having an admin to be around and pushing that one button.

I don't see any inconveniences with not giving it to editors translators since they are basically like delete and move rights, you need to be responsible to use them; which editors translators are. - Indestructible Pharaoh VII 20:43, 3 March 2017 (UTC)

Support

 * 1) x 100^100. - Indestructible Pharaoh VII  20:43, 3 March 2017 (UTC)
 * 2) . People can already add translation markup and do it wrong, it hardly happens, but it's not like it's making the situation worse if it does. I suspect most editors won't use it at all if they don't know how to, similar to tilesheets and ore dict and all that rubbish. The main reason why this has been brought to attention is to alleviate the issues with Lua navboxes. I recognize it's not a perfect solution, but I really don't see how it hurts. If we give editors (this vote is for editors, not translators btw, that's a not a group) that right and it turns out the entire wiki blows up, we can take it away and all make fun of me later for being wrong, but I really don't think that's going to happen. -Xbony2 (talk) 01:27, 4 March 2017 (UTC)
 * How are we defining blowing up?  Chocohead Nag • Edits • Staff 01:41, 4 March 2017 (UTC)
 * Causes a mess and everybody says "damn we shouldn't have done this". -Xbony2 (talk) 01:52, 4 March 2017 (UTC)
 * 1) . Translation markup isn't really that hard, and would be helpful for more efficient work. Also if some things aren't done correctly they can always be fixed, but like Xbony2 stated it happens in rare cases. -- sokratis 12GR  Staff  19:27, 4 March 2017 (UTC)
 * 2) for Kyth. Here's the proof -  Indestructible Pharaoh VII  14:14, 5 March 2017 (UTC)
 * Can confirm I support it. While it adds scope for breakage, the current system means that regular users basically can't edit translated pages at all without admin help (need to be a translator to translate, and the english translation comes from the source page). Kythyria (talk) 14:24, 5 March 2017 (UTC)
 * 1) Sure. I think that would not be a bad change. - Moritz 30 German translator 17:31, 11 March 2017 (UTC)

Against

 * 1)  Translation markup is confusing. I don't even do it right usually when I get sucked into doing it. I'd rather not have translation managers/admins have to spend time fixing messed up translation markup. Also if a page is not ready to be marked for translation, but it gets marked, then admins have to deal with un-marking it, which is annoying. I'd rather this be left entirely in the hands of translators and translation administrators. --  Satanic  Santa 🎅F T B Wiki Admin 20:47, 3 March 2017 (UTC)
 * Ok, so if the editors get changed to "translators" you would support? - Indestructible Pharaoh VII 20:52, 3 March 2017 (UTC)
 * Not necessarily. It seems like the coordination between translators and translation admins works fine enough. The only time it doesn't work is for Lua modules. I'd rather we fix that issue instead of adding a band-aid solution. --  Satanic Santa 🎅F T B Wiki Admin 20:56, 3 March 2017 (UTC)
 * You know that xbony2, the translation admin, lives on the other side of the planet for me, meaning that we don't really talk to each other that much.
 * I mean the difference between our timezones (mine and yours) is even greater. Also User talk:Xbony2 is a thing :P --  Satanic Santa 🎅F T B Wiki Admin 21:06, 3 March 2017 (UTC)
 * And we have been talking like 2 messages everyday using LittleHelper and that affects the communication between the translation admin, you, and myself. - Indestructible Pharaoh VII 21:11, 3 March 2017 (UTC)
 * 1) I'd much rather see a proper solution to making the translation system easier, especially when it comes to lua modules. Simply giving editors the ability to mark up pages for translation isn't going to help, because translation markup is hard to get right. If an editor is skilled enough to markup various articles templates and modules correctly, then they're likely skilled enough to be an admin. Move and delete rights, on the other hand, are not particularly difficult to use correctly, you just need to understand the basic guidelines of what articles should be named and have a minimum level of responsibility.  21:05, 3 March 2017 (UTC)
 * I'm somewhat skilled enough to add translation markups, even ask xbony2, yet you keep telling me that you highly doubt of supporting me if I apply for one. - Indestructible Pharaoh VII 21:11, 3 March 2017 (UTC)
 * 1)  All this is doing is perpetuating the current translation system which is definitely not what we want. If you want to be useful, keep pestering  to actually do T3, so that translation is generally much better than what we've got now (especially for modules).  Chocohead  Nag • Edits • Staff 14:16, 5 March 2017 (UTC)
 * Don't you think that what is xbony2 doing is a large project and requires some time and effort while just giving editors (and translators) the right to work without the need of an admin to be needed is better and easier and a temporary solution till he finishes T3? - Indestructible Pharaoh VII 14:23, 5 March 2017 (UTC)
 * If all we do is keep using the old system, there's no incentive to actually work on a new one (which he hasn't been doing anyway, so even more reasons not to is definitely not good). Especially if the new one is not particularly compatible format wise with the current system, the more it's used the more that needs to be replaced. We don't even know if that's the case since T3 doesn't exist yet.  Chocohead Nag • Edits • Staff 15:08, 5 March 2017 (UTC)
 * T3 isn't still ready or in place of being ready, so it's a long wait till it's ready. Xbony2 can work on T3 meanwhile you give us markup rights, so the translation isn't stopped until xbony2 makes a better system. I trust xbony2 with making T3 after you give us the rights since you aren't affected in any way and he is the translation admin. - Indestructible Pharaoh VII 15:59, 5 March 2017 (UTC)
 * It's only a long wait because he's not started it, translation isn't stopped from this not happening either, forcing him to keep marking pages up himself is a good way of getting him to make T3. It's the current system being stupid that means letting the world be able to translate is a bad idea, not because editors are particularly reckless. Spam doesn't affect us in anyway but it's still something that we don't want, broken translation markings are the same. I don't trust xbony with T3 at all because it's taken so long to get nowhere, he'd had plenty of opportunities to start it yet we're still waiting on something else that wasn't a problem months ago despite T3 not changing plan wise. You need to see where the priority should be.  Chocohead Nag • Edits • Staff 16:48, 5 March 2017 (UTC)
 * Alleviating the old system a little bit will not slow down T3, that's silly. The reason why T3 has not been worked on is because of other projects being prioritized, once the Modded Minecraft Wiki rename/remarketing is out of the way I should be able to focus on that. Thanks for all the help on that btw guys. Oh wait. (눈_눈). I've had to do most of it myself. If ya'll could help me out with branching out that would be really awesome. -Xbony2 (talk) 15:39, 5 March 2017 (UTC)
 * It's not slowing down T3 being made, but slowing down the implementation of T3 to get all the translated pages into the new format. Other (apparently more important) projects have been kicking around undefined for months, yet you still insist how important translation is meant to be, as well as how much better it will be. Renaming shouldn't be taking priority as T3 isn't dependent on it, it's not reliant on the brand so doesn't have to wait for it. Renaming will happen when we actually get a logo and decide on a main page layout, but the lack of any solid proposal means it's hard to make suggestions on nothing.  Chocohead Nag • Edits • Staff 16:48, 5 March 2017 (UTC)
 * It's not about T3 depending on it, it's about it being prioritized over it at the moment. I can't work on twenty projects at once. If I did, T3 will look like the removal of staff so far- half-assed and incomplete because Santa and Retep are too busy to work on it. That wouldn't be better than now. It's more than renaming, it's remarketing and redefining the wiki, which is what I am currently trying to work on. -Xbony2 (talk) 17:01, 5 March 2017 (UTC)
 * What exactly are you doing to remarket the wiki?
 * Okay, I'm really gonna need you to stop complaining vaguely and indirectly about whatever it is I'm not doing at the time. When I'm developing extensions or libs or doing bureaucratic shit, you complain I don't write content. Now I'm writing content, so you're complaining I'm not doing bureaucratic shit. If you want me to do something, which you clearly do, just fucking tell me instead of vaguely complaining about my lack of doing Unknown Thing (TM) to Chocohead. --  Satanic Santa 🎅F T B Wiki Admin 17:31, 5 March 2017 (UTC)
 * Okay, this is getting out of context, the vote is on giving markup rights to editors. That will make admins like xbony2 free for other crap like T3 or anything else instead of marking stuff up. My proposal would free some work out of xbony2 (since he is doing most if not all of the markups) and put more responsibility on translators / editors to translate while xbony2 has the time to do other stuff like working on T3 (I'm also willing to help if I know how to) and renaming / remarketting the wiki.
 * In conclusion, if my proposal passes, it will free time to admins and others who have markup rights to do other stuff.- Indestructible Pharaoh VII 17:44, 5 March 2017 (UTC)
 * This very much is the context, you're talking about the translation system and that's what's being discussed. You're not going to be saving any time with this change though, as it's going from admins marking things up right (or at least you better hope they do) to people marking things up then the admins having to fix it if they do it wrong. The admins still have to check the marking up of translations so they're no better off. You've got to remember it's not just you who is getting the ability to mark things up if this passes, and if other people start doing it wrong the right will just get revoked and then you're no better off from it.  Chocohead Nag • Edits • Staff 17:56, 5 March 2017 (UTC)
 * This proposal is only gonna add a right, and if editors don't know markup, they don't. Easy. On the other hand, people who know how to markup will not waste admins time since they will only check if they missed anything and thus taking less time. - Indestructible Pharaoh VII 18:00, 5 March 2017 (UTC)
 * Editor is the most basic permission people can gain, just because they don't know something doesn't mean they won't try use it. Easy is an incredibly naive approach to take when there's plenty on examples of translated pages for people to try having a go. Admins still have to check the translated pages which isn't really much faster than just doing it themselves, you still have to check everything which you'd have written yourself otherwise. Admin's time isn't heavily invested in marking up translations anyway, so there's little benefit to be gained at all.  Chocohead Nag • Edits • Staff 18:23, 5 March 2017 (UTC)
 * This is not how it works. Editors aren't beginners, users are. Since it takes voting in order to become one and thus they have a responsibility, as well as we can tell them don't do stuff they don't know how to use. Easy. Plus, you are the people who voted on removing the staff, so there is a gap between editors and admins. - Indestructible Pharaoh VII 20:37, 5 March 2017 (UTC)
 * You've not read what I wrote properly. Editor is the most basic permission people can gain, not have. Voting them in, as proven a few days ago, is a hollow procedure as one or two people actually bother voting then it automatically passes so there's hardly much investment responsibility wise. This shouldn't chance though as there's no benefit from restricting new enthusiastic people by having a long process to make them editors. Telling them not to use things they don't understand isn't productive though, at best you're just scare them from experimenting, at worse you'll scare them from editing at all. We have complicated templates for example, telling people to not use them because they don't understand is not going to make them better contributors. Removing staff doesn't change much in this situation anyway, having a separate translators permission is the only way of handling this, not just trusting people to be able to use the mess of the translation system because they can edit normally or just trusting them to not touch it.  Chocohead Nag • Edits • Staff 21:27, 5 March 2017 (UTC)
 * I trust current editors for not doing anything irresponsible. Also, you could just write a proposal to create a translators group instead of completely going against this one. - Indestructible Pharaoh VII 06:46, 6 March 2017 (UTC)
 * Current editors are not the same as the future, unless of course we never get anyone else new again, which is probably much worse. Either way though, If you want it passing so badly you can make your translation group suggestion yourself because I definitely don't support this one.  Chocohead Nag • Edits • Staff 16:01, 6 March 2017 (UTC)

Neutral

 * 1) I'd like to see some sort of automatical solution... (my browser will crash if i press "delete" button so i cannot correct my typo) T3==ThaumicTechTinker, Urey.S.Knowledge Welcome back, commander 00:22, 6 March 2017 (UTC)
 * Gee, you should probably get that fixed. -Xbony2 (talk) 00:33, 6 March 2017 (UTC)

Creation of a translators group
Seen as in the proposal above, those who are against, mainly Chocohead, see that giving it to editors is too "broad" (from what I understood) as they are the first thing that gets voted for as well as translators actually needing it to markup pages and all that and I'm too lazy to write everything but since they said in IRC making it for the translators group is better. - Indestructible Pharaoh VII 18:35, 6 March 2017 (UTC)

Support

 * 1)  100^100^100 - Indestructible Pharaoh VII  18:35, 6 March 2017 (UTC)

Against

 * 1) . This should just be part of the editor group. I haven't really been able to vent my views on the subject because Immortal has done most of the arguing (some of his points I may agree with, some I may not) and as a result there's a messy wall of text. I have little to no doubt that giving editors the translation marking right will not cause greater harm than help, nor slow T3, nor produce anything that I am incapable with dealing with. -Xbony2 (talk) 00:04, 7 March 2017 (UTC)
 * I know, but Choco and people who opposed said around the words of "Editors are not going to use it and it's hard and all that". So that is just for these people to support. - Indestructible Pharaoh VII 17:43, 7 March 2017 (UTC)
 * I'm not voting for the last resort if the better option is still in. If it closes I'll consider updating it. -Xbony2 (talk) 00:53, 8 March 2017 (UTC)
 * 1)  because your other proposal passed so this is 100% pointless --  Satanic  Santa 🎅F T B Wiki Admin 23:23, 12 March 2017 (UTC)

Neutral

 * 1)  Note that translators in general wouldn't need this group. Anyone can translate pages already. This group would only be needed for people that need to be able to mark pages up for translation. If the proposal clarified this and didn't call the group "Translators" but something more fitting, then I would support it.  18:40, 6 March 2017 (UTC)
 * What about "Markup Allowed" or "TransMarkAllowed" or "TransMarkPerms" ? just ideas -- sokratis 12GR  Staff  19:21, 6 March 2017 (UTC)
 * You do note that there is a group you like called editors even though anyone can edit (thnx to Santa who said that in the discussion). So should I change the name of the editors group since everyone can edit? - Indestructible Pharaoh VII 19:39, 6 March 2017 (UTC)
 * 1)  Until I could determine its necessity. T3==ThaumicTechTinker, Urey.S.Knowledge Welcome back, commander 01:23, 7 March 2017 (UTC)
 * 2)  I'm not sure why more groups but well... -- sokratis 12GR   Staff  22:43, 12 March 2017 (UTC)

Discussion

 * I do not really understand the purpose of this. Are you asking for a translation administrator group (as was removed in the group overhaul) or a "translator" group that actually has the permissions which would be expected for a translation administrator? Anyone can translate so I don't really see the point in this. I guess we have a group called "editor" even though anyone can edit. I don't know. --  Satanic Santa 🎅F T B Wiki Admin 19:05, 6 March 2017 (UTC)
 * Just a group who has markup rights since anyone can translate maybe a name suggestion or anything but that is basically what my proposal wants to create. - Indestructible Pharaoh VII 19:31, 6 March 2017 (UTC)
 * I guess we need to deal with those untranslated articles first? T3==ThaumicTechTinker, Urey.S.Knowledge Welcome back, commander 01:23, 7 March 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)


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


 * 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)


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


 * 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

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)

Clarifying sentence casing for disambiguations
I propose that the sentence case style that is already established for articles be extended to disambiguations. Here is a set of examples to show how this would affect things:
 * Thing (GregTech) -> Thing (GregTech) (unchanged)
 * Concept that is not referenced in the game as a proper noun (Esteemed Innovation) -> Concept that is not referenced in the game as a proper noun (Esteemed Innovation) (unchanged)
 * Thing (GregTech) (Item) -> Thing (GregTech) (item) (Item -> item)
 * Not a proper noun (Concept) -> Not a proper noun (concept) (Concept -> concept)

Basically, this will just require a slight modification to Project:MoS to clarify that the sentence casing is extended to the parenthetical disambiguation of article titles. --  Satanic Santa 🎅F T B Wiki Admin 18:55, 13 March 2017 (UTC)
 * The Minecraft Wiki does something similar (see mcw:Clay (block) and mcw:Melon (block)). It makes sense. -Xbony2 (talk) 22:45, 13 March 2017 (UTC)
 * I never liked that, the fact it was extra in the title rather than the item/block's name made titlecase make more sense IMO.  Chocohead Nag • Edits • Staff 22:51, 13 March 2017 (UTC)