Feed The Beast Wiki
Advertisement
Feed The Beast Wiki

AE2 Color Applicator

I saw that you moved something. I was wondering if I had done something wrong. DiamondKnight19 (talk) 01:56, 4 January 2019 (UTC)

DiamondKnight19: nah, not really. The AE2 navbox disambiguated some stuff that doesn't need to be disambiguated. -Xbony2 (talk) 04:56, 4 January 2019 (UTC)

Quark/de

Please deal with Quark/de. Thanks. -- SatanicSanta🎅FTB Wiki Admin 23:45, 1 August 2019 (UTC)

(not really taken care of but this was added to the list a while ago) -Xbony2 (talk) 02:27, 2 September 2019 (UTC)

Easy pages to transfer

These ones shouldn't require much work:

- User-12316399 (talk) 08:35, 24 October 2019 (UTC)

link: Feed The Beast Wiki:Minecraft Wiki exportation project -Xbony2 (talk) 02:27, 19 December 2019 (UTC)

Old mods to search for

As requested by User-12316399:

-Xbony2 (talk) 04:38, 6 April 2020 (UTC)

maybe look at https://archive.org/details/Minecraft_Archive_Project_Midnight_Mod_Collection_2016 -Xbony2 (talk) 14:09, 6 April 2020 (UTC)

page to protect

Hello, can you semiprotect (edit only autoconfirmed) Energy Core (Draconic Evolution)‎‎? Almost every second edit is vandalism. Qwertxquartx (talk) 18:37, 29 July 2020 (UTC)

Yeah, that's a bit odd. Protected. -Xbony2 (talk) 02:41, 30 July 2020 (UTC)

Better standart-deletereasons?

Hello, I would like to see the default deletion reasons (currently stored at MediaWiki:Deletereason-dropdown) being "polished up" a bit, following the Wikipedia pattern. I have created a draft for this: (see source code for complete thing)

  • General
    • Other reason
    • G1: Nonsense, vandalism or spam
    • G2: Test page
    • G3: Unambiguous copyright infringement or plagiarism
    • G4: Insufficient content
    • G5: Duplicated article
    • G6: Non-controversial cleanup
    • G7: One author who has requested deletion or blanked the page
    • G8: Page depending on a nonexistent or deleted page
  • User pages
    • U1: User request to delete page in own userspace
    • U2: Userpage or subpage of a nonexistent user
  • Redirects
    • R1: Redirect to a deleted or nonexistent page
    • R2: Recently created, implausible redirect/typo

Of course this still looks quite chaotic, e.g. the pure section links should be replaced by redirects like "FTB:DP#1", or the links to wikipedia. Besides, I have to say that I can't judge now whether the whole thing really makes sense, the idea just came to my head. Strangely enough, I get Wikipedia reasons when deleting files, but nowhere else? Qwertxquartx (talk) 16:54, 1 August 2020 (UTC)

The original was ripped directly from Wikipedia. Jinbobo, one of the original admins, copied a lot of things from Wikipedia, and to be honest I think it was a pretty bad idea to do much of what he did, since the scale of this wiki is entirely different from Wikipedia's and we have very different issues. Not hating on him, there weren't a lot of other wikis to copy from and Gamepedia wasn't a thing like it is today, but his solutions weren't great for the long term. I think it's better here to have a simplified set of reasons and a simplified deletion policy and not link to Wikipedia (their policies are not ours). We should probably finish a deletion policy before linking to it also. -Xbony2 (talk) 20:53, 1 August 2020 (UTC)
Okay. Thank you for your fast reply! Qwertxquartx (talk) 14:15, 2 August 2020 (UTC)
gamepedia notifications helped :P -Xbony2 (talk) 23:50, 2 August 2020 (UTC)

Updating Tilesheet

" Xbony2, me (and probably Qwertxquartx) would like you to update the Thermal Foundation tilesheet." - AstroFlux (talk) (contributions) 11:36, 18 August 2020 (UTC)

" Astroflux put it on my talk page." -Xbony2 (talk) 11:59, 18 August 2020 (UTC)

I did this, but forgot that Gamepedia is updating their back-end. I can upload these files once the back-end migration is over. --SizableShrimp🦐 (talk · contribs) 21:27, 18 August 2020 (UTC)
Welp, guess I have an other person to bother now :P - AstroFlux (talk) (contributions) 02:05, 19 August 2020 (UTC)
Hopefully can some time next week. Need to return home. -Xbony2 (talk) 05:07, 21 August 2020 (UTC)
nvm its done by the shrimp. I'm tired sorry. future request should probably be on FTBW:Tilesheet requests. -Xbony2 (talk) 05:20, 21 August 2020 (UTC)

Module:Language cleanup

Currently, the Language module does not support passing in parameters directly from {{#invoke}}. I have added this to support, along with cleaning up the modlink function to my fork of the module at Module:SizableShrimp/Language. This adds support for parameters when using #invoke and also fixs a bug that was present in the modlink function. It also adds comments for each function detailing which template uses it. If this could be copied over, that would be great; yes, I did test it. -- SizableShrimp🦐 (talk · contribs) 19:36, 9 September 2020 (UTC)

updated -Xbony2 (talk) 04:29, 12 September 2020 (UTC)

L error.png

reversed changes. This made most things wrapped in {{L}} completely disappear like this ->. So yeah. -Xbony2 (talk) 04:58, 12 September 2020 (UTC)
That was a mistake on my end trying to use fromParent which would not work well in the existing framework. So, I've modified {{ProcessArgs}} in a backwards-compatible way to support using the parent frame arguments if they exist but the current frame arguments as a backup, or the direct args table given (by another module using the module). I can confirm that {{ML}} and {{L}} will work with the changes according to my testing using {{#invoke:}}. It seems it will work with everything else, too. This should be good to go (and then immediately test after it is released). The templates in question to test are {{PageLanguage}}, {{Language}}, {{L}}, and {{ML}}, along with any other templates/modules that use these 4 templates or {{Language}}. I kinda forgot I made these changes but finally remembered today, so here I am fixing it now. -- SizableShrimp🦐 (talk · contribs) 11:12, 28 November 2020 (UTC)

Discussion of the Effect template

Right now, the {{Effect}} template does not support translation. This is not hard to fix, but there is discussion needed on how we should require translators to translate the effect names. There are two approaches that could be taken to solve this.

  1. Have translations be made for the tile in the EFFECT tilesheet.
    • A con of this is that tiles must be translated one at a time, since the Extension:Tilesheets extension does not support translating entire tilesheets or more than one tile at a time.
      • This problem with the Tilesheets extension may be solved with a future update. However, because of the current status of UCP, I do not see this being possible at this time.
  2. Have a page similar to Template:Vanilla/types located at Template:Effects/types.
    • This has the added benefit of putting all the translations in one place and on one page; however, tiles added to the EFFECT tilesheet must be manually appended to this page.
    • I believe this option is better at this time because of the problems with tile translations listed above.

Honestly, this section would probably be better suited on the Centralized discussion page, but I thought I might as well list it here since I have changes requested for Module:Language above. Also, it's not like anyone responds on the Centralized discussion page either (see ftbw:Centralized discussion#1.14 Vanilla renamed items). Anyways, that's all. Thanks. -- SizableShrimp🦐 (talk · contribs) 19:36, 9 September 2020 (UTC)

Yeah in the future I would put it on the CD but just link me here. And yeah I would go with the tile translation, even if it's a bit annoying, it's the absolute standard for translations of tiles. EFFECT is just another tilesheet. The template is not too commonly used that this is a major issue. Editors (the group) can translate tiles manually, and there's not a lot of tiles. Might ask Qwertxquartx and Qunynawy‎ to translate them for some of the stuff that exists rn. -Xbony2 (talk) 04:48, 12 September 2020 (UTC)

Main page

Hey there! Are you still active? We really need to talk about the main page for this wiki — Game widow ( talk ) 13:20, 12 February 2021 (UTC)

Briefly, a giant wall of text / links is virtually unusable on mobile devices. Nearly a quarter of your visitors are coming from mobile devices, which is admittedly fewer than our average, but still considerable. I would suggest using some sort of "drill-down" / "breadcrumbs" approach, where the main page would have a much abbreviated version of the the "What is FTB" section, with a "read more" link to a separate page with the full text. And, i would suggest that you come up with some broad classification of the mods (say 10 or fewer round up categories displayed as links or icons) and create links from those to actual categories containing the mods. This would make for a much cleaner main page and allow people to just click through to more specific areas of interest — Game widow ( talk ) 14:11, 12 February 2021 (UTC)
I'm semi-active (busy with college, not checking the wiki every day). I agree that the main page sucks, especially the mod list; it's been on our radar for a while now. It was fine when there weren't that many mods documented, but now, the 500 listed is too much, and there's ~400 not listed (because of DPL) which is a source of confusion to some. I think we will replace the list with a few "featured" (the most popular) mods and a link to a page that is larger list of mods, separated by ABC order. There is no meaningful way to create general categories of mods imo (CurseForge has their own categories but they're pretty arbitrary). Feel free to recommend any main pages you think we should aspire towards. -Xbony2 (talk) 20:15, 13 February 2021 (UTC)


Replys

Thank you for doing my first Talk page, all that resource will help me a lot thank you so much, I hope to do much more then I am doing right now, thanks again lets hope I can do this stuff right.MissLexyShadows (talk) 20:27, 13 February 2021 (UTC)

np! Feel free to join our Discord which was linked. -Xbony2 (talk) 22:22, 13 February 2021 (UTC)

Fixing errors on your community

Hello! I'm DDElephant, and I represent Fandom's Vanguard volunteer team. We help communities adopt to new technologies and features and to improve their technical performance. We have spotted some code issues on this wiki that I’d like to make fixes to, which should not break anything further nor affect the wiki content. Fixing some of the issues will require me to introduce some new code that will perform better and should appear the same as it does now. Maintaining the fixes if you want to make changes should be very simple. We'd really like to get working on your community, and we would appreciate your go-ahead. Once I am finished, I will leave you another message to follow up. Please expect that Vanguard will deploy these fixes on or after Next Mon unless you note that we should not. If you have any questions, please let me know. Thank you for your consideration, and I hope we can produce a result that works for everyone.DDElephant (talk) 23:45, 23 July 2021 (UTC)

There are 4 pages in Category:Scribunto_modules_with_errors because that the Translation extension thinks they are lua code while they actually docs (incorrect content model). Can you help to fix them? DDElephant (talk) 00:12, 24 July 2021 (UTC)
Seems I could only change the content model of one; the others seems to be fully protected. Sorry. But it is not of great concern, since they are not real errors, although it looks like translation of module docs is broken in general. I hope I can fix this at some point in the future. Anyway, {{Welcome}} to the wiki though, there's a lot to clean up. -Xbony2 (talk) 03:31, 24 July 2021 (UTC)
Just picked up your reply. Thanks for your cooperation. DDElephant (talk) 06:16, 27 July 2021 (UTC)
Hi, I have fixed the size-exceeding problem on Getting Started (Forestry - Beekeeping) with Template:Cg/Crafting Table/hp‎. I would not say that it is a good solution but I guess this is our only choice. As I don't know how to add its Russian translation, it is appreciated if you can add it, which can be used to fix Getting Started (Forestry - Beekeeping)/ru.
  • The principle behind the fix is that there is an extra cost for every layer of templates. By eliminating a frequently-called template, I saved about 40% of the size of the whole template.
BTW I created some sandbox pages for the fixing and I'm sorry for wasting your time deleting them. DDElephant (talk) 09:00, 28 July 2021 (UTC)
Advertisement