Feed The Beast Wiki

Follow the Feed The Beast Wiki on Discord or Mastodon!

READ MORE

Feed The Beast Wiki
Register
m (new BlockRenderer)
No edit summary
(43 intermediate revisions by 14 users not shown)
Line 1: Line 1:
 
{{Ambox|type=notice|text='''This page is for posting information and issues that can affect anyone'''.<br />Discussion of any issues that affect the community in general are appropriate for this page.}}
 
{{Ambox|type=notice|text='''This page is for posting information and issues that can affect anyone'''.<br />Discussion of any issues that affect the community in general are appropriate for this page.}}
  +
{{Ambox|text='''Please put each new request in a new section'''.}}
 
{{Ambox|type=notice|text=Old notices will be moved to the archive:<br />
 
{{Ambox|type=notice|text=Old notices will be moved to the archive:<br />
[[/Archive/2015|2015]]{{,}}[[/Archive/2016|2016]]{{,}}[[/Archive/2017|2017]]{{,}}[[/Archive/2018|2018]]{{,}}[[/Archive/2019|2019]]<br />Dates are by archival time, not necessarily by discussion time.}}
+
[[/Archive/2015|2015]]{{,}}[[/Archive/2016|2016]]{{,}}[[/Archive/2017|2017]]{{,}}[[/Archive/2018|2018]]{{,}}[[/Archive/2019|2019]]{{,}}[[/Archive/2020|2020]]{{,}}[[/Archive/2021|2021]]<br />Dates are by archival time, not necessarily by discussion time.}}
   
 
__TOC__
 
__TOC__
 
==Modpacks reform==
 
I'm proposing a few ideas on how to reform the documentation of modpacks on the wiki.
 
# '''Removing "Mods Included" sections on modpack pages, and linking to its auto-generated list on CurseForge instead''' ([http://www.feed-the-beast.com/projects/ftb-infinity-evolved/files/2283980 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]].
 
# '''Changing {{Tl|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''' ([http://minecraft.curseforge.com/projects/nuclear-control-2/relations/dependents?filter-related-dependents=6 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.
 
# 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 (<small>Technically, modpacks are mods, just a mod with many components from many people.</small>). 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 {{Tl|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 {{Tl|Navbox Modpacks}} FTB-only would be a good thing.
 
# 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.
 
Thoughts? [[User:Xbony2|-Xbony2]] ([[User talk:Xbony2|talk]]) 00:15, 14 March 2016 (UTC)
 
# 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.
 
# 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).
 
# Agree. I think they could be listed as Unlisted Packs in the navbox.
 
# k
 
-- '''[[User:TheSatanicSanta|<span style="color:red">Satanic</span>]][[User talk:TheSatanicSanta|<span style="color:green">Santa</span>]]'''🎅''<sup><span style="color:#1868A5">F</span><span style="color:#13A425">T</span><span style="color:#A12122">B</span> '''Wiki Admin'''</sup>'' 02:44, 14 March 2016 (UTC)
 
: Get the modpack team to update it. Ha. Automatically generating would make the most sense if we want to keep it. [[User:Xbony2|-Xbony2]] ([[User talk:Xbony2|talk]]) 11:10, 14 March 2016 (UTC)
 
 
: Well, it currently seems like the way to do this is to use the Ruby script written by {{U|Xbony2}}. Any other ideas as to how to quickly grab the mods list? --<span style="color:#BC9900">Sir</span><span style="color:#8A2BE2">Moogle</span> ([[User:SirMoogle|🐥]] • [[User talk:SirMoogle|💬]] • [[Special:Contributions/SirMoogle|🌟]]) 17:30, 24 June 2019 (UTC)
 
   
 
== Isometric renders for mobs ==
 
== Isometric renders for mobs ==
Line 38: Line 18:
 
:I would like this however. I'd prefer if [[BlockRenderer]] [https://github.com/elytra/BlockRenderer/issues/12 added a mob dumping feature] but I don't know how easy that would be. [[User:Xbony2|-Xbony2]] ([[User talk:Xbony2|talk]]) 20:55, 3 November 2017 (UTC)
 
:I would like this however. I'd prefer if [[BlockRenderer]] [https://github.com/elytra/BlockRenderer/issues/12 added a mob dumping feature] but I don't know how easy that would be. [[User:Xbony2|-Xbony2]] ([[User talk:Xbony2|talk]]) 20:55, 3 November 2017 (UTC)
 
::Worth mentioning that [https://minecraft.curseforge.com/projects/better-questing 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). [[User:Lykrast|Lykrast]] ([[User talk:Lykrast|talk]]) 21:04, 3 November 2017 (UTC)
 
::Worth mentioning that [https://minecraft.curseforge.com/projects/better-questing 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). [[User:Lykrast|Lykrast]] ([[User talk:Lykrast|talk]]) 21:04, 3 November 2017 (UTC)
 
== Registry and unloc names in infoboxes ==
 
As seen on [https://ftb.gamepedia.com/index.php?title=Petrified_Fuel_Generator&oldid=670012 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). --'''[[User:Hubry|<span>Hubry</span>]]''' <sup>([[User talk:Hubry|talk]])</sup> 04:37, 21 January 2018 (UTC)
 
:I am in favor of trying this. [[User:Xbony2|-Xbony2]] ([[User talk: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). {{User:Retep998/Signature}} 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". -- '''[[User:TheSatanicSanta|<span style="color:red">Satanic</span>]][[User talk:TheSatanicSanta|<span style="color:green">Santa</span>]]'''🎅''<sup><span style="color:#1868A5">F</span><span style="color:#13A425">T</span><span style="color:#A12122">B</span> '''Wiki Admin'''</sup>'' 23:50, 21 January 2018 (UTC)
 
::Hubry was a bit more specific on Discord and proposed the prefix be included if it was odd. [[User:Xbony2|-Xbony2]] ([[User talk: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 <code>F3+H</code>, 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. --'''[[User:Hubry|<span>Hubry</span>]]''' <sup>([[User talk:Hubry|talk]])</sup> 00:14, 22 January 2018 (UTC)
 
   
 
==Quest Book template==
 
==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). [[User:Lykrast|Lykrast]] ([[User talk:Lykrast|talk]]) 15:01, 24 March 2018 (UTC)
 
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). [[User:Lykrast|Lykrast]] ([[User talk:Lykrast|talk]]) 15:01, 24 March 2018 (UTC)
 
== Interwiki mess ==
 
So, Pcj recently mass deleted likely-unused interwiki prefixes from all the wikis on Gamepedia. This has brought our interwiki stuff to my attention. There are a few issues:
 
# The "wikt" prefix was deleted. Bony thinks this prefix was used and I also think that, however if it was it was a duplicate because there is already a "wiktionary" prefix. We need to ensure only ''one'' is used, and decide on which one. I prefer "wikt" because it's shorter.
 
# There are two Wikipedia prefixes, "wp" and "wikipedia." Likewise we should pick one and correct everything on the wiki to only use this one. I personally like "wp," also because it's shorter.
 
# Likewise with "mw" and "mediawikiwiki"
 
# The "raw" prefix is incorrect. Is this actually used? Those URLs (hydra-media whatever) are no longer used. We need to check all of this thing's usages and hopefully delete it; I don't know why we would ever need this for an interwiki prefix.
 
# The following seem likely to be unused. We should assess these all:
 
## "commons"
 
## "ddgo"
 
## "google"
 
## "wikia"
 
## "wikimedia"
 
## "wow"
 
# [[Project:Administrators' noticeboard#Curseforge Interwiki link|Squirrel wants a CurseForge interwiki. Discuss that on the according discussion post.]]
 
 
Let us deliberate.
 
-- '''[[User:TheSatanicSanta|<span style="color:red">Satanic</span>]][[User talk:TheSatanicSanta|<span style="color:green">Santa</span>]]'''🎅''<sup><span style="color:#1868A5">F</span><span style="color:#13A425">T</span><span style="color:#A12122">B</span> '''Wiki Admin'''</sup>'' 17:43, 26 July 2018 (UTC)
 
 
: My opinions:
 
:* raw was added by Xbony for [[Augmented Interactions]] because he wanted to embed gifs - honestly these should be converted to videos and embedded in the gallery instead (see [[wp:WP:Extended image syntax#Video files]]).
 
:* Wow is used on [[Thundercaller]].<!--did anyone say [thunderfury, the blessed blade of the windseeker]?--> I think you added it just for that page :P - I didn't think it was necessary and I think it can be removed.
 
:* I dont think we have any use for Commons or Wikimedia, though Commons could potentially be useful at some point I guess?
 
:* google/ddgo - do we really need an interwiki for search queries?
 
:* IIRC the main Wikia site has interwikis for all the wikis, so that's basically one interwiki for everything there - though I think we just link to Wikia pages directly when we link there, so we could remove it.
 
: I'm fine with cutting the six interwiki prefixes you mentioned. As for wp/wikipedia, wikt/wiktionary and mw/mediawikiwiki the shorter ones for sure. (mediawikiwiki sounds stupid, too.) --'''[[User:Hubry|<span>Hubry</span>]]''' <sup>([[User talk:Hubry|talk]])</sup> 19:09, 26 July 2018 (UTC)
 
: ''wikt'' is used, particularly through {{Tl|Wikt}}. [https://ftb.gamepedia.com/Special:WhatLinksHere/Template:Wikt A few pages] are broken now, but whateves >.> I prefer shorter prefixes, but also prefer them to be recognizable, so I am opposed to using "wp" which looks odd to me. [[User:Xbony2|-Xbony2]] ([[User talk:Xbony2|talk]]) 01:18, 27 July 2018 (UTC)
 
::In the meantime, I've adjusted the template to use the other prefix. [[User:DSquirrelGM|DSquirrelGM]]<span style="font-size:50%; vertical-align:middle; text-align:center;">[[User talk:DSquirrelGM|&#120035;]][[UserProfile:DSquirrelGM|&#120031;]][[Special:Contributions/DSquirrelGM|&#120018;]]&nbsp;[[gphelp:GRASP|&#128504;]]</span> 03:22, 27 July 2018 (UTC)
 
 
== PneumaticCraft and PneumaticCraft:Repressurized ==
 
The current PNC pages are quite empty and outdated : since his port to 1.12 by desht and MineMaarten, Plants Seeds, associated Plastics and Electron Tubes were removed, for example.
 
As there is almost no content for PNC, is it better to rename the PNC categorie to PNC:Re or make a brand new PNC:Re categorie? [[User:Sewef13|-Sewef13]] 14:11, 13 August 2018 (UTC)
 
:If there's a title change from PneumaticCraft to PneumaticCraft: Repressurized, I'd create a new category. --[[User:SirMoogle|SirMoogle]] ([[User talk:SirMoogle|talk]]) 14:32, 13 August 2018 (UTC)
 
   
 
==Status Effects==
 
==Status Effects==
Line 93: Line 32:
 
:: For enchantments we got [[:Category:Enchantments]] for actual enchantments [[:Category:Enchanting]] for stuff that apply them. For status effects we got [[:Category:Status effects]] were we both have actual status effects and stuff that apply them (currently just the various [[Totem]] pages). So the idea was to also split that so they aren't mixed up in the same category. [[User:Lykrast|Lykrast]] ([[User talk:Lykrast|talk]]) 21:05, 17 August 2018 (UTC)
 
:: For enchantments we got [[:Category:Enchantments]] for actual enchantments [[:Category:Enchanting]] for stuff that apply them. For status effects we got [[:Category:Status effects]] were we both have actual status effects and stuff that apply them (currently just the various [[Totem]] pages). So the idea was to also split that so they aren't mixed up in the same category. [[User:Lykrast|Lykrast]] ([[User talk:Lykrast|talk]]) 21:05, 17 August 2018 (UTC)
   
  +
== 1.14 Vanilla renamed items ==
==FTB One access for documenting modpacks==
 
  +
There are many items and blocks that were renamed in the 1.14 [[mcw:Village & Pillage|Village & Pillage]] update. We need to discuss how we should go about representing and displaying the differences between these renamed items on the wiki. Some things to consider are:
  +
# How would the newer names affect the user experience on mods made for older versions? E.g. using JEI to search for a block
  +
# What should we display to users on Vanilla pages for renamed items?
  +
# Should we display the older item names on pages using a specific pre-1.14 Minecraft version?
  +
# How should we handle renamed items for mods that span between pre-1.14 and 1.14?
  +
Feel free to add to this list, or refer to a question by its number in the discussion below. All of this is up for debate. --&nbsp;[[User:SizableShrimp|<span style="color:orange">SizableShrimp🦐</span>]]&nbsp;([[User talk:SizableShrimp|talk]]&nbsp;'''·'''&#32;[[Special:Contributions/SizableShrimp|contribs]]) 07:26, 1 September 2020 (UTC)
  +
  +
== V template ==
  +
I just used my bot account, {{U|ShrimpBot}}, to standardize Vanilla pages to all end in <code>(Vanilla)</code> for consistency and the fact that many articles link to disambiguation pages of Vanilla items that have alternate articles from mods that have the same name as the Vanilla item. This is obvious for me to see and catch since I have a [[User:SizableShrimp/common/disambiguations.js|user script]] that highlights any disambiguation pages in orange since the extension that does this, [[mw:Extension:Disambiguator|Extension:Disambiguator]], is not currently approved on Gamepedia. Now that all Vanilla items are formatted the same, it makes sense to have a simple template, <code>{{V}}</code>, that simply contains <code><nowiki>{{ML|{{{1}}}|V}}</nowiki></code>. It would make it easier to determine which pages reference Vanilla items and simplify the bloat of having to type <code>{{ML</code> and <code>|V}}</code> each time for referencing Vanilla items. This also seems cleaner than doing <code><nowiki>[[Dirt (Vanilla)|Dirt]]</nowiki></code> or <code><nowiki>{{L|Dirt (Vanilla)|Dirt}}</nowiki></code>, especially if we decide to change the naming convention for disambiguated mod pages. Not sure what the community thinks about "shortcut templates", which I believe this might fall under.
  +
:Honestly I'm not a fan of "shortcut templates" like ML that save a few characters but give newer editors more confusion. More to keep track of, and if you know your tricks then it ends making less of a difference anyway (for example, you can just <code><nowiki>[[Dirt (Vanilla)|]]</nowiki></code> and [[wikipedia:Help:Pipe trick|it will just fill]] in the display). Or perhaps I'm just an old dog who doesn't like new tricks. [[User:Xbony2|-Xbony2]] ([[User talk:Xbony2|talk]]) 04:46, 29 November 2020 (UTC)
  +
:::I like "shortcut templates" in certain circumstances because it abstracts the process and allows the process to change. If we use the pipe trick or {{Tl|ML}} or something else and then wanted to change the format of Vanilla pages (see Retep's [[User:Retep998/DisProposal|disambiguation proposal]]) to something more relevant, we would have to update any and all pages that use a hardcoded format. I agree that it can be harder to keep up with, but I think it might help in the long run, especially if this V template becomes used on a wide array of articles, allowing new and veteran editors to pick up on it. Also, the use of a dedicated Vanilla template makes it easy to identify when editing what items are vanilla items with either a page search or skimming an article. Along with the added benefit of being able to tell what pages transclude the V template and the ability to change how it functions at any given time, of course. These are my thoughts on the issue. --&nbsp;[[User:SizableShrimp|<span style="color:orange">SizableShrimp🦐</span>]]&nbsp;([[User talk:SizableShrimp|talk]]&nbsp;'''·'''&#32;[[Special:Contributions/SizableShrimp|contribs]]) 05:00, 29 November 2020 (UTC)
  +
::::I don't think there's a need to put '(Vanilla)' to all pages, most of the one that have the disambiguation page are blocks that can be [[Chisel (AUTOMATIC MAIDEN)|chiseled]], which I plan to remove the disambiguation and include all the chiseled blocks in the page when I have the time - [[User:Astroflux|<span style="color:lightgray">'''Astro'''</span><span style="color:red">'''Flux'''</span>]] ([[User talk:Astroflux|talk]]) ([[Special:Contributions/Astroflux|contributions]]) 08:39, 13 December 2020 (UTC)
  +
  +
==Proposed MoS addition: ambox before hatnotes or visa versa==
  +
There's been a lot of discussion and debate about whether or not amboxes (like {{Tl|Stub}}) should be above or below hatnotes (mainly {{Tl|About}}). This has been discussed for a long time but it seems a consensus was never created. I'm impartial to either, although I will think more about it. I'm making this a vote but if there aren't strong feelings on it, it will be somewhat informal. The results will be appended to the [[ftbw:MOS|MOS]]. [[User:Xbony2|-Xbony2]] ([[User talk:Xbony2|talk]]) 07:10, 14 December 2020 (UTC)
 
* {{Neutral}}. [[User:Xbony2|-Xbony2]] ([[User talk:Xbony2|talk]]) 07:10, 14 December 2020 (UTC)
  +
* Hatnotes should have higher priority placements (above, on page) since presumably they're intended for long-term content placement of some importance. [[User:DSquirrelGM|DSquirrelGM]] ([[User talk:DSquirrelGM|talk]]) 07:28, 14 December 2020 (UTC)
  +
* I lean towards placing hatnotes ''after'' amboxes, because an ambox refers to the page (which is arguably more important), whereas a hatnote refers to the content. Though I might be biased because it’s the way this is done on the Russian Minecraft Wiki, meanwhile English MCW’s style guide has hatnotes above message boxes. —&nbsp;<b style="line-height:19px;letter-spacing:1px">[[user:BabylonAS|<span style="color:#0E56C9">Babylon</span>]][[user talk:BabylonAS|<span style="color:#C9A00E">A</span><span style="color:#C90E10">S</span>]]</b> 08:06, 14 December 2020 (UTC)
  +
* I'm more biased towards '''amboxes before hatnotes''', as amboxes are generally placed when a page requires some sort of maintenance, which should be fixed as soon as possible. Hatnotes are intended to be in the article, and sandwiching something that is undesired (amboxes) between hatboxes and the rest of the content looks strange. [[User:SirMoogle|SirMoogle]] ([[User talk:SirMoogle|talk]]) 17:28, 14 December 2020 (UTC)
  +
* Personally, I prefer the order to be ambox/amboxes first and then hatnotes. However, as I searched a bit, I was surprised that [[wikipedia:MOS:ORDER|Wikipedia's MOS]] states the opposite. It is even made strictly clear [[wikipedia:WP:HATNOTEPLACE|in this page]]. But for me, amboxes first is my go-to way. — <span style="font-size:20px">🍕</span><span style="font-family:'Comic Sans MS';">[[User:Yivan000|<span style="color:#FFC83D">Yivan</span><span style="color:#F7894A">000</span>]] <small><sup>[[User_talk:Yivan000|talk]]</sup><sub>[[Special:Contributions/Yivan000|contribs]]</sub></small></span> <span style="font-size:20px">🍕</span> 07:14, 17 December 2020 (UTC)
  +
* I prefer having '''hatnotes before amboxes''' because it makes more sense to have content links at the top of the page for users to easily navigate to other, more applicable pages if they have traveled to the wrong one (e.g. an {{Tl|About}} hatnote). I also think having hatnotes before amboxes looks better graphically, since amboxes are indented further compared to hatnotes, which makes them look ugly and out of place when placed above hatnotes. This would also be in line with Wikipedia's MOS, which states, as I quote: {{Quote|If a reader has reached the wrong page, they should find that out first.|[[wp:WP:HATNOTEPLACE|WP:HATNOTEPLACE]]}} --&nbsp;[[User:SizableShrimp|<span style="color:orange">SizableShrimp🦐</span>]]&nbsp;([[User talk:SizableShrimp|talk]]&nbsp;'''·'''&#32;[[Special:Contributions/SizableShrimp|contribs]]) 06:13, 27 December 2020 (UTC)
  +
  +
==How to fix an error in item list on uploaded tilesheet==
  +
* Or how to fix blank item when available on the uploaded tile-sheet?
  +
Hi! my name is Al_Cool I would like to update Misty World's wiki, but lack some knowledge. Today I've learned how to use template NI and the Tile-sheet system.
  +
When I try to preview a line in the Item viewer, the result is a pink square, like if there was a mistake. When I look at the uploaded tile-sheet and at the item's name, Mod name, x,y,z position are accurate. So when I ask to preview tile-list item 341130 named (View 341130 Glass Container MW 11 21 0 16px,32px.) When I search the item's icon on the tile-sheet*, it actually is at column 11 and row 21. So how to fix this?
  +
<span style="border:#009a00 solid 1px; border-radius:1em; -webkit-border-radius:1em; -moz-border-radius:1em; padding:1px; margin:1px;"> <span>[http://therunefactory.wikia.com/wiki/User:Alcool007 <span style="color:blue;">Alcool007</span>] </span> <span style="color:green;"><abbr title="alcool007@hotmail.com">Contact</abbr> </span> <span>Help us build a nice and friendly community on wikia :)</span> </span> 23:50, 18 May 2021 (UTC)
  +
* https://static.wikia.nocookie.net/ftb_gamepedia/images/9/9f/Tilesheet_MW_16_0.png/revision/latest?cb=20200611045247
  +
  +
I think I got the start of a pierce through! By following and reading the source code of many template's link with or around the way tilesheet image are printed, I've ended up with two hypothesis.
  +
* A) Retry. Every template using the tile-sheet system link to the [[https://ftb.fandom.com/wiki/Template:Renames]] rename template. If you read the warning on the document page, it say something about how this template should not be used when a languagefile.txt is left blank. [[https://ftb.fandom.com/wiki/Module:Renames]] By default return a "empty" as a result witch is very similar to the pink square who replace missing tile image. So far I don't know how rename.txt work or if there is any way to edit it once the tile-sheet is uploaded. So something I would like to try is to Re-upload the Tile sheet while taking care about any warning message to make sure every steps is filled and not empty.
  +
* B) Delete. The only missing image in the template are from an advanced version of the game, like if the additional content was not correctly included. Most mods only list one tile-sheet. So I guess when updated or re-uploaded some user ratter like to delete the previous version. So its a long shot but, maybe deleting the previous tile-sheet file's version could solve the problem as only the newest content does not print.
  +
  +
So far since my 2 hypothesis require deleting a file or re uploading one by using a software that I'm not familiar with, I would ratter wait for someone more experienced that me to try to fix the problem. <span style="border:#009a00 solid 1px; border-radius:1em; -webkit-border-radius:1em; -moz-border-radius:1em; padding:1px; margin:1px;"> <span>[http://therunefactory.wikia.com/wiki/User:Alcool007 <span style="color:blue;">Alcool007</span>] </span> <span style="color:green;"><abbr title="alcool007@hotmail.com">Contact</abbr> </span> <span>Help us build a nice and friendly community on wikia :)</span> </span> 10:41, 19 May 2021 (UTC)
  +
:{{U|Alcool007}}: Sorry, which tiles are broken? I can switch some names around, or maybe just delete and remake the tilesheet (sometimes that's easier although Retep's software is better than it used to be). [[User:Xbony2|-Xbony2]] ([[User talk:Xbony2|talk]]) 04:04, 19 June 2021 (UTC)
  +
  +
== Merge proposal among Immersive Engineering's LV, MV, HV pages, and creating a new infobox template ==
  +
{{Infobox
  +
|name=Wire Coil
  +
|imageicon={{Gc|mod=IE|link=none|LV Wire Coil}}{{Gc|mod=IE|link=none|MV Wire Coil}}{{Gc|mod=IE|link=none|HV Wire Coil}}
  +
|mod=Immersive Engineering
  +
|type=cable
  +
|rftraversing=2048, 8192, 32768
  +
}}
  +
I propose the following sets of pages be merged:
  +
* [[LV Capacitor]] + [[MV Capacitor]] + [[HV Capacitor]]
  +
* [[LV Wire Connector]] + [[MV Wire Connector]] + [[HV Wire Connector]]
  +
* [[LV Wire Coil]] + [[MV Wire Coil]] + [[HV Wire Coil]]
  +
* [[LV Wire Relay]] + [[MV Wire Relay]] + [[HV Wire Relay]]
  +
This is on the basis that each set's items are functionally identical. The only thing different is their ratings (coil length, power capacity, etc.), which can be given in tables and/or the infobox. We can create an "Infobox Immersive Engineering" template so the pages' information can be tailored to Immersive Engineering's system.
  +
  +
I can carry out these changes. What say ye on this matter?
  +
  +
——[[User:JavaRogers|JavaRogers]] ([[User talk:JavaRogers|talk]]) 01:18, 18 June 2021 (UTC)
  +
  +
:A special infobox for IE is a bit unorthodox and seems unnecessary, but if you wanted to merge the pages that would be okay. Good work on updating/improving IE info btw, that's something I've neglected for years (among other things). [[User:Xbony2|-Xbony2]] ([[User talk:Xbony2|talk]]) 03:53, 19 June 2021 (UTC)
   
  +
:: Haha yeah. Hey I appreciate the validation! About the infobox idea, I'm just playing off the fact that we have [[Feed_The_Beast_Wiki:All_templates#Infobox_templates|special infoboxes]] for a number of other mods. In lieu of creating a new template, would it be better to add some IE fields directly to {{Tl|Infobox}} (<code>lvtraversing, mvtraversing, hvtraversing</code>, etc.), or just use formatting tricks to make it work? ——[[User:JavaRogers|JavaRogers]] ([[User talk:JavaRogers|talk]]) 22:43, 25 June 2021 (UTC)
FTB is offering to give FTB One access to wiki editors who are willing to document modpacks. You would have early access to modpacks and the testing servers so that the documentation would be ready by the time the modpack is finally released. Please let me or {{U|TheSatanicSanta}} know and we will get you in touch with the appropriate people to grant you access. {{User:Retep998/Signature}} 23:23, 17 August 2018 (UTC)
 
  +
:::The regular infobox has some magic that comes with it, like <code>{{{1inputtitle}}}</code>/<code>{{{1usetitle}}}</code>, so you can add some custom fields without changing it. I can add to {{Tl|Infobox}} later if needed. [[User:Xbony2|-Xbony2]] ([[User talk:Xbony2|talk]]) 18:17, 27 June 2021 (UTC)
:{{U|Retep998}}, has this offer been rescinded yet? --<span style="color:#BC9900">Sir</span><span style="color:#8A2BE2">Moogle</span> ([[User:SirMoogle|🐥]] • [[User talk:SirMoogle|💬]] • [[Special:Contributions/SirMoogle|🌟]]) 22:54, 30 October 2018 (UTC)
 
::Not that I am aware of. {{User:Retep998/Signature}} 15:47, 31 October 2018 (UTC)
 
   
  +
==CANT ACTIVATE COMPACT CLAUSTROPHOBIA==
== BlockRenderer ==
 
  +
PLEASE HELP I NEED AN ANSWER WHY WONT IT WORK THE PAGE DOESNT MAKE SENSE {{Unsigned|NeverStopWinning}}
For all editors, I found a new BlockRender mod for 1.14: https://www.curseforge.com/minecraft/mc-mods/item-texture-exporter
 
   
Because [[BlockRenderer]] is currently only available until 1.12.2. I haven't tried the new mod yet. --<b>[[User:LuminousLizard|LuminousLizard]] <sup>FTB Wiki Staff</sup> <sub><span style="background-color:yellow; color:black">de-N / "en-2"</span></sub></b> ([[User_talk:LuminousLizard|talk]]) 15:26, 12 October 2019 (UTC)
 
   
<!-- do not edit below this line -->
+
<!-- Do not edit below this line -->
   
 
{{Navbox portals}}
 
{{Navbox portals}}

Revision as of 12:17, 15 January 2022

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. -- SatanicSanta🎅FTB Wiki Admin 19:17, 3 November 2017 (UTC)
My first attempt is rough.
Buffalo experiment
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)

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)

Status Effects

To make Status Effects page at least a little bit prettier, I suggest adding a type to the infobox to say "Status Effect" (instead of using "Mechanic"), having a separate category for things that apply Status Effects (just like we have Enchatments and Enchanting), and renaming the current status effect images to something a lil more structured like "Potion XXX", "Status XXX" or something similar. That last one may not be necessary if we find a way to get Status Effects tilesheets for mods (or anything similar that would make individual images for the pages not required). Lykrast (talk) 08:43, 15 August 2018 (UTC)

I'd personally be okay with simply adding status effects from all the mods to the EFFECT tilesheet. 🐇Retep998🐇🐰Bunny Overlord🐰 08:47, 15 August 2018 (UTC)
There would be just the problem of disabigs, as for example both Astral Sorcery and Defiled Lands add a Bleeding effect. Lykrast (talk) 09:30, 15 August 2018 (UTC)
Because the status effect tiles are 36x36, we can't put them on the normal tilesheeets. Either they'd all go on the EFFECT tilesheet with a bit of manual disambig, or we'd have to have a whole set of new EFFECT abbreviations and tilesheets. 🐇Retep998🐇🐰Bunny Overlord🐰 17:20, 15 August 2018 (UTC)
I support the infobox change. I also agree with Peter on the tilesheets. I'm not quite sure what you mean about the categories. -- SatanicSanta🎅FTB Wiki Admin 21:00, 17 August 2018 (UTC)
For enchantments we got Category:Enchantments for actual enchantments Category:Enchanting for stuff that apply them. For status effects we got Category:Status effects were we both have actual status effects and stuff that apply them (currently just the various Totem pages). So the idea was to also split that so they aren't mixed up in the same category. Lykrast (talk) 21:05, 17 August 2018 (UTC)

1.14 Vanilla renamed items

There are many items and blocks that were renamed in the 1.14 Village & Pillage update. We need to discuss how we should go about representing and displaying the differences between these renamed items on the wiki. Some things to consider are:

  1. How would the newer names affect the user experience on mods made for older versions? E.g. using JEI to search for a block
  2. What should we display to users on Vanilla pages for renamed items?
  3. Should we display the older item names on pages using a specific pre-1.14 Minecraft version?
  4. How should we handle renamed items for mods that span between pre-1.14 and 1.14?

Feel free to add to this list, or refer to a question by its number in the discussion below. All of this is up for debate. -- SizableShrimp🦐 (talk · contribs) 07:26, 1 September 2020 (UTC)

V template

I just used my bot account, ShrimpBot, to standardize Vanilla pages to all end in (Vanilla) for consistency and the fact that many articles link to disambiguation pages of Vanilla items that have alternate articles from mods that have the same name as the Vanilla item. This is obvious for me to see and catch since I have a user script that highlights any disambiguation pages in orange since the extension that does this, Extension:Disambiguator, is not currently approved on Gamepedia. Now that all Vanilla items are formatted the same, it makes sense to have a simple template, Template:V, that simply contains {{ML|{{{1}}}|V}}. It would make it easier to determine which pages reference Vanilla items and simplify the bloat of having to type {{ML and |V}} each time for referencing Vanilla items. This also seems cleaner than doing [[Dirt (Vanilla)|Dirt]] or {{L|Dirt (Vanilla)|Dirt}}, especially if we decide to change the naming convention for disambiguated mod pages. Not sure what the community thinks about "shortcut templates", which I believe this might fall under.

Honestly I'm not a fan of "shortcut templates" like ML that save a few characters but give newer editors more confusion. More to keep track of, and if you know your tricks then it ends making less of a difference anyway (for example, you can just [[Dirt (Vanilla)|]] and it will just fill in the display). Or perhaps I'm just an old dog who doesn't like new tricks. -Xbony2 (talk) 04:46, 29 November 2020 (UTC)
I like "shortcut templates" in certain circumstances because it abstracts the process and allows the process to change. If we use the pipe trick or {{ML}} or something else and then wanted to change the format of Vanilla pages (see Retep's disambiguation proposal) to something more relevant, we would have to update any and all pages that use a hardcoded format. I agree that it can be harder to keep up with, but I think it might help in the long run, especially if this V template becomes used on a wide array of articles, allowing new and veteran editors to pick up on it. Also, the use of a dedicated Vanilla template makes it easy to identify when editing what items are vanilla items with either a page search or skimming an article. Along with the added benefit of being able to tell what pages transclude the V template and the ability to change how it functions at any given time, of course. These are my thoughts on the issue. -- SizableShrimp🦐 (talk · contribs) 05:00, 29 November 2020 (UTC)
I don't think there's a need to put '(Vanilla)' to all pages, most of the one that have the disambiguation page are blocks that can be chiseled, which I plan to remove the disambiguation and include all the chiseled blocks in the page when I have the time - AstroFlux (talk) (contributions) 08:39, 13 December 2020 (UTC)

Proposed MoS addition: ambox before hatnotes or visa versa

There's been a lot of discussion and debate about whether or not amboxes (like {{Stub}}) should be above or below hatnotes (mainly {{About}}). This has been discussed for a long time but it seems a consensus was never created. I'm impartial to either, although I will think more about it. I'm making this a vote but if there aren't strong feelings on it, it will be somewhat informal. The results will be appended to the MOS. -Xbony2 (talk) 07:10, 14 December 2020 (UTC)

  • Pictogram voting neutralNeutral. -Xbony2 (talk) 07:10, 14 December 2020 (UTC)
  • Hatnotes should have higher priority placements (above, on page) since presumably they're intended for long-term content placement of some importance. DSquirrelGM (talk) 07:28, 14 December 2020 (UTC)
  • I lean towards placing hatnotes after amboxes, because an ambox refers to the page (which is arguably more important), whereas a hatnote refers to the content. Though I might be biased because it’s the way this is done on the Russian Minecraft Wiki, meanwhile English MCW’s style guide has hatnotes above message boxes. — BabylonAS 08:06, 14 December 2020 (UTC)
  • I'm more biased towards amboxes before hatnotes, as amboxes are generally placed when a page requires some sort of maintenance, which should be fixed as soon as possible. Hatnotes are intended to be in the article, and sandwiching something that is undesired (amboxes) between hatboxes and the rest of the content looks strange. SirMoogle (talk) 17:28, 14 December 2020 (UTC)
  • Personally, I prefer the order to be ambox/amboxes first and then hatnotes. However, as I searched a bit, I was surprised that Wikipedia's MOS states the opposite. It is even made strictly clear in this page. But for me, amboxes first is my go-to way. — 🍕Yivan000 talkcontribs 🍕 07:14, 17 December 2020 (UTC)
  • I prefer having hatnotes before amboxes because it makes more sense to have content links at the top of the page for users to easily navigate to other, more applicable pages if they have traveled to the wrong one (e.g. an {{About}} hatnote). I also think having hatnotes before amboxes looks better graphically, since amboxes are indented further compared to hatnotes, which makes them look ugly and out of place when placed above hatnotes. This would also be in line with Wikipedia's MOS, which states, as I quote:
If a reader has reached the wrong page, they should find that out first.
WP:HATNOTEPLACE

-- SizableShrimp🦐 (talk · contribs) 06:13, 27 December 2020 (UTC)

How to fix an error in item list on uploaded tilesheet

  • Or how to fix blank item when available on the uploaded tile-sheet?

Hi! my name is Al_Cool I would like to update Misty World's wiki, but lack some knowledge. Today I've learned how to use template NI and the Tile-sheet system. When I try to preview a line in the Item viewer, the result is a pink square, like if there was a mistake. When I look at the uploaded tile-sheet and at the item's name, Mod name, x,y,z position are accurate. So when I ask to preview tile-list item 341130 named (View 341130 Glass Container MW 11 21 0 16px,32px.) When I search the item's icon on the tile-sheet*, it actually is at column 11 and row 21. So how to fix this? Alcool007 Contact Help us build a nice and friendly community on wikia :) 23:50, 18 May 2021 (UTC)

  • latest?cb=20200611045247

I think I got the start of a pierce through! By following and reading the source code of many template's link with or around the way tilesheet image are printed, I've ended up with two hypothesis.

  • A) Retry. Every template using the tile-sheet system link to the [[1]] rename template. If you read the warning on the document page, it say something about how this template should not be used when a languagefile.txt is left blank. [[2]] By default return a "empty" as a result witch is very similar to the pink square who replace missing tile image. So far I don't know how rename.txt work or if there is any way to edit it once the tile-sheet is uploaded. So something I would like to try is to Re-upload the Tile sheet while taking care about any warning message to make sure every steps is filled and not empty.
  • B) Delete. The only missing image in the template are from an advanced version of the game, like if the additional content was not correctly included. Most mods only list one tile-sheet. So I guess when updated or re-uploaded some user ratter like to delete the previous version. So its a long shot but, maybe deleting the previous tile-sheet file's version could solve the problem as only the newest content does not print.

So far since my 2 hypothesis require deleting a file or re uploading one by using a software that I'm not familiar with, I would ratter wait for someone more experienced that me to try to fix the problem. Alcool007 Contact Help us build a nice and friendly community on wikia :) 10:41, 19 May 2021 (UTC)

Alcool007: Sorry, which tiles are broken? I can switch some names around, or maybe just delete and remake the tilesheet (sometimes that's easier although Retep's software is better than it used to be). -Xbony2 (talk) 04:04, 19 June 2021 (UTC)

Merge proposal among Immersive Engineering's LV, MV, HV pages, and creating a new infobox template

Wire Coil



ModImmersive Engineering
TypeCable
Energy
RF traversing2048, 8192, 32768 RF/t

I propose the following sets of pages be merged:

This is on the basis that each set's items are functionally identical. The only thing different is their ratings (coil length, power capacity, etc.), which can be given in tables and/or the infobox. We can create an "Infobox Immersive Engineering" template so the pages' information can be tailored to Immersive Engineering's system.

I can carry out these changes. What say ye on this matter?

——JavaRogers (talk) 01:18, 18 June 2021 (UTC)

A special infobox for IE is a bit unorthodox and seems unnecessary, but if you wanted to merge the pages that would be okay. Good work on updating/improving IE info btw, that's something I've neglected for years (among other things). -Xbony2 (talk) 03:53, 19 June 2021 (UTC)
Haha yeah. Hey I appreciate the validation! About the infobox idea, I'm just playing off the fact that we have special infoboxes for a number of other mods. In lieu of creating a new template, would it be better to add some IE fields directly to {{Infobox}} (lvtraversing, mvtraversing, hvtraversing, etc.), or just use formatting tricks to make it work? ——JavaRogers (talk) 22:43, 25 June 2021 (UTC)
The regular infobox has some magic that comes with it, like {{{1inputtitle}}}/{{{1usetitle}}}, so you can add some custom fields without changing it. I can add to {{Infobox}} later if needed. -Xbony2 (talk) 18:17, 27 June 2021 (UTC)

CANT ACTIVATE COMPACT CLAUSTROPHOBIA

PLEASE HELP I NEED AN ANSWER WHY WONT IT WORK THE PAGE DOESNT MAKE SENSE -- Preceding unsigned comment was added by NeverStopWinning (talkcontribs)