User talk:dgelessus

If you want to leave me a message, feel free to do so here. Please create a new section if you aren't answering an existing discussion.

Crafting Grid template

Just wanted to respond to the question from your edit summary: I find the one-parameter-per-line layout much easier to read, so that's how I use the templates. Neither way is really "right"; yours favours resembling the crafting grid, while mine treats it like the wiki template it is, specifying each parameter in a distinct location. To me, your "logical" way is much too jumbled, especially for recipes which don't fill the crafting grid. If we added enough whitespace to distinguish each parameter into consistent columns, it might look alright, but that exchanges file size for code readability, which isn't a great plan. So, there it is. You asked, I answered. Happy editing! --timrem (talk) 23:13, 16 September 2013 (CEST)

Removing redirects

When you delete redirect pages, make sure nothing links to them. There's a "What links here" button in the Toolbox which you can use to check that. RZR0 ( Talk | Contributions) 12:14, 5 October 2013 (CEST)

Whoops, looks like I forgot that. Thanks for fixing the links. :) --dgelessus ^{(talk · contribs)} 12:19, 5 October 2013 (CEST)

Item Name in template

Regarding the template change here, why is forcing a double name in the item template any better than the current setup? In the template/doc description it states, use the "| name = " only when is somehow different from the page name. Why change that? Simone (talk) 20:31, 5 October 2013 (CEST)

Many boxes have the name given anyway even if it is not different from the page title, so I wanted to make it automatic. Also, why not change the box title with the name param and remove the name entry in the box? The original page title is still visible in the article heading, so there's no real need for two names in the box. --dgelessus ^{(talk · contribs)} 20:53, 5 October 2013 (CEST)

I would agree on that. Maybe even having a complete sanity check on the templates altogether, when possible. Simone (talk) 21:51, 6 October 2013 (CEST)

What exactly do you mean with "complete sanity check"? A general template overhaul? By the way, I've started making a modular infobox system. Once I'm done with that I'll move it into template namespace and I'll see about implementing that into the existing templates. --dgelessus ^{(talk · contribs)} 22:20, 6 October 2013 (CEST)

Armor Tab slots

Any particular reason you brought back the "Taira-like" description of the belt slot? I originally wrote the page with no idea what any of the slots were, and just used the closest thing I could think of (in that case, it looked like a tiara). An anonymous editor added "Belt" in the verbage so that it looked like belt was the proper purpose of the slot, and I thought it made sense, so I removed the tiara-like description in favor of simply "Belt". It looks enough like a belt as well. As for the shield slot, interestly enough, I originally wrote it saying it looked like a shield, but User:AQiccl135 replaced it saying it was a Glove. --Kahless61 (talk) 16:40, 11 October 2013 (CEST)

Wait what? Looks like I accidentally edited an old revision of the page, bringing back some old stuff :/ Yeah, it really is a belt. I'll go ahead and fix that. --dgelessus ^{(talk · contribs)} 19:16, 11 October 2013 (CEST)

Tinker Apostrophe

Awe man, you had to point out the apostrophe placement. Now ALL the pages related to it have the wrong apostrophe! Someone's gonna have to go through and fix that up. Might want to get a bot to take care of it. If you don't know how to, talk with some of the other regulars, like RZR0, as they may know or may already have one. If not, I could make one. --Kahless61 (talk) 06:16, 13 October 2013 (CEST)

Well, I left a redirect, so it shouldn't have broken anything. Also I have absolutely no experience with bots... but a link-rename-bot would be nice, for stuff like this and RE Battery -> RE-Battery. --dgelessus ^{(talk · contribs)} 15:40, 13 October 2013 (CEST)

No, you didn't break anything, you just brought it to our attention that all the things have the wrong spelling now. --Kahless61 (talk) 17:33, 13 October 2013 (CEST)

Re: more minor wording changes

I disagree, this was designed for use with the TC4 articles since they are currently just copies of the TC3 articles and I figured a blaring and large banner would get someone's attention to update it. . ƒelinoel_ 13:59, 28 October 2013 (CET)

Wait, that was THAT template I overwrote? I originally updated it to the style of the other hatnote boxes, but didn't notice that it was the one used on the TC pages. I'll go ahead and restore the old message and add the image again. --dgelessus ^{(talk · contribs)} 14:11, 28 October 2013 (CET)

PS: Done.

{{outdated|logo.png}}

--dgelessus ^{(talk · contribs)} 14:18, 28 October 2013 (CET)

Well it can be used for other things, but I made it specifically for TC4 articles. . ƒelinoel_ 22:48, 28 October 2013 (CET)

Legacy

I dunno, I think the 1.5 modpacks shouldn't be considered legacy just yet... ƒelinoel ~ (Talk) 23:19, 7 November 2013 (CET)

They are officially "locked", as stated in this thread, so I went ahead and moved them over. Assuming you're talking about 152wgt/ngt, those were also betas for the new 1.5 modpacks, which are now out, so the betas are of course not active modpacks anymore. --dgelessus ^{(talk · contribs)} 08:21, 8 November 2013 (CET)

Going by what is not being updated ever again? I see. ƒelinoel ~ (Talk) 08:47, 8 November 2013 (CET)

Nav template

Any thoughts on expanding this into a nav template? ƒelinoel ~ (Talk) 05:17, 10 November 2013 (CET)

You mean like {{IC2-nav}} and such? That would prevent it from being sortable by mod or category, which was the main reason I made it a wikitable. --dgelessus (talk · contribs) 13:48, 10 November 2013 (CET)

Not if you build it like b-nav. If you put the sorting code on a separate template and then link the template in the navbox it keeps the sortability.

Also speaking of b-nav, I didn't use the Outdated template itself but copypasted the code so that the outdated category wouldn't be added just in case someone goes around looking at the articles in that category for things to clean up. I figure my b-nav doesn't need cleaned up because it will always be outdated no matter what since bees get changed every version and it would just be better in the long run if people couldn't find it based on that category. . ƒelinoel_ 15:37, 10 November 2013 (CET)

Re: Going to create separate articles for spam and vandalism soon.

Wanna make some for concepts and mobs too? :b . ƒelinoel_ 03:15, 1 December 2013 (CET)

Sure :D Just want to get the existing rules cleaned up first so we have an up-to-date base to work with. --dgelessus (talk · contribs) 13:03, 1 December 2013 (CET)

lol kay then . ƒelinoel_ 01:34, 3 December 2013 (CET)

Hi! I looked at the vandalism page that you made. It's really good. It seems to to have a small grammatical error that I thought I should point out. Repeated acts vandalism will lead to longer or permanent blocking. I'm pretty sure that should be Repeated acts OF vandalism will lead to longer or permanent blocking. I would have fixed that myself, but it was protected so I thought that you could probably do that. JonathanHopeThisIsUnique (talk) 00:00, 26 February 2014 (CET)

Fixed, thanks for pointing that out! :) --dgelessus (talk · contribs) 11:25, 26 February 2014 (CET)

PAGENAME

Does {{PAGENAME}} really bother you that much? :p Celestial Oblivion (talk) 23:36, 6 December 2013 (CET)

Yeah, it does... to me it's just a thing for dynamic templates and doesn't directly belong into articles. It just looks out of place. Actually the server has to substitute it with the page name every time the article is edited, so it does cause a minimal increase in server load ;) though I'm not sure if it does it separately for each PAGENAME, or if it checks once and uses that value for all PAGENAMEs. --dgelessus (talk · contribs) 14:26, 7 December 2013 (CET)

Well, articles aren't usually edited THAT often. And doesn't the item template have to use it anyways? If it is the the second case there wouldn't really be any difference at all.Celestial Oblivion (talk) 03:29, 8 December 2013 (CET)

I agree dgelessus, the opening of the article should not use the PAGENAME keyword, it should have the page's name spelt out. --timrem (talk) 04:35, 8 December 2013 (CET)

It's mostly a personal thing, it really disrupts the text flow IMO. I've also seen some pages with PAGENAME used in-line with other text, that really makes the text look strange (sorry if I'm offending anyone who does that). --dgelessus (talk · contribs) 12:55, 8 December 2013 (CET)

I've used it in the past on a lot of articles that have almost the exact same content (Railcraft Decorative Blocks), in which case it saves me a bit of extra time since I don't think the wiki editor has a built in find/replace feature. Sometimes I'll also use it on pages that have really long names or on articles that do not have an official name or otherwise might be at risk for a name change. Celestial Oblivion (talk) 18:19, 8 December 2013 (CET)

There's a find/replace tool that you can turn on in your editing preferences. Also, lemme test this... Dgelessus --dgelessus (talk · contribs) 18:21, 8 December 2013 (CET)

Yes! If you type {{subst:PAGENAME}} it is automatically replaced by static text once you save the page. --dgelessus (talk · contribs) 18:22, 8 December 2013 (CET)

Nice! I will start using that then. Also I did find the Find/Replace feature, I didn't notice it under advanced settings before because it was all the way on the left. x_x Celestial Oblivion (talk) 23:50, 8 December 2013 (CET)

Coal Coke

While I don't deny that article needed major cleanup due to being repetitive and now somewhat out of date, I'm surprised your big problem with it was "too specific information". I see nothing in the style guide that says we should limit an article to the basics, and it seems quite appropriate to me that an article on a power source should discuss the pros and cons of using that method. Celestial Oblivion (talk) 20:58, 24 December 2013 (CET)

Stuff like this can be included in articles, sure. BUT we should probably finish discussing that here because the style guide is SEVERELY out of date and can't be referenced like that due to that. . ƒelinoel_ 21:58, 24 December 2013 (CET)

What I meant with "specific" was that the article seemed to explain every possible application in great detail, which really belongs in some tutorial rather than that article. I tried to put all necessary information into the first few paragraphs while leaving out info that applies to any fuel (being burnable for EU and MJ) and the very detailed boiler setup. Maybe I removed too much information, but most of it just didn't belong there IMO. --dgelessus (talk · contribs) 22:47, 24 December 2013 (CET)

I feel a tutorial would be overkill for just a fuel source. To me a tutorial would be for how to run an automated Coke Oven setup or how to make the most efficient steam boiler, since those things would involve many items and machines and wouldn't fit under the scope a single item. Detailing the best ways and the limitations of using a particular fuel source should go in an article IMO. Celestial Oblivion (talk) 23:16, 24 December 2013 (CET)

Which is why I said that if we update the Style Guide to explain how to handle such things as "specific"-ness then that would resolve this issue. . ƒelinoel_ 07:24, 25 December 2013 (CET)

Coolant cell names

Hey, just checking that you're sure that those names for the coolant cells are correct. I named them like that because they had those names in 1.6.2 builds of GT. RZR0 ( Talk | Contributions) 14:56, 8 January 2014 (CET)

Are they? Will have to double-check that... but I thought that the strange spellings were fixed in newer versions. The Helium equivalents have the correct spelling as well, so it just seemed logical that the NaK ones have the same spelling. --dgelessus (talk · contribs) 16:19, 8 January 2014 (CET)

At the time I checked it, they were different, which is why I made it a point to name them that. But maybe it's updated in the latest build, I'm not sure. RZR0 ( Talk | Contributions) 16:49, 8 January 2014 (CET)

No clue

No clue what is going on but just redirecting doesn't fix it, I tried to see if it was just a cache thing but am not sure if I did it right, thoughts? ƒelinoel ~ (Talk) 19:02, 17 January 2014 (CET)

Nope, a redirect won't affect categorization, AND it is a caching issue. By the way, I'm using AWB on User:dgelBot to fix the TiC apostrophe, so it should be fixed soon. --dgelessus (talk · contribs) 19:05, 17 January 2014 (CET)

I looked though, they aren't having the TiC apostrophe issue, that is what I meant when I said I had no clue what was wrong with it. ƒelinoel ~ (Talk) 19:09, 17 January 2014 (CET)

What I'm saying is that I'm removing manual incorrect cats, and editing the pages should also update the automatic cat. --dgelessus (talk · contribs) 19:10, 17 January 2014 (CET)

Ohhh editing each page should update it? Ok. . ƒelinoel_ 19:56, 18 January 2014 (CET)

You don't even have to change anything, just hitting Save should be enough. --dgelessus (talk · contribs) 20:42, 18 January 2014 (CET)

tim linked me directly. ƒelinoel ~ (Talk) 20:47, 18 January 2014 (CET)

What is that? ƒelinoel ~ (Talk) 23:03, 18 January 2014 (CET)

Thermal Expansion

Thermal Expansion has undergone major changes in the past few months. I would like to keep the original Thermal Expansion page as far intact for legacy users as possible. All of the Content past the major changes in 1.6 I believe should be moved to the Thermal Expansion 3 page. —Preceding unsigned comment added by TehRawrz (talk · contribs)

Please remember to sign your posts. ƒelinoel ~ (Talk) 19:50, 31 January 2014 (CET)

Splitting up the page into version 3 and 4 really is a good idea, will do that now. The reason why I moved the 1.6 section up was so it is easily visible (and I fixed some small formatting things). By the way, you should sign your posts by typing four tildes (~~~~) or using the "signature" button in the toolbar. --dgelessus (talk · contribs) 21:03, 31 January 2014 (CET)

Umm... TE2 is the old version, TE3 is the new version. There is no TE4. --timrem (talk) 23:41, 31 January 2014 (CET)

Oh dangit. Now I also fell for it -.- --dgelessus (talk · contribs) 23:57, 31 January 2014 (CET)

Ars magica 2

It would be useful if you could send me all of the Ars Magica 2 textures. I do not know how to pull them from the mod file.--Nitroxko (talk) 18:26, 5 February 2014 (CET)

Looks like User:RZR0 is uploading them right now ;) He has some kind of program that can generate block and item images, so if you should need such images uploaded you can contact him. --dgelessus (talk · contribs)

Re: check yo caps

http://ftbwiki.org/Infusion_altar

No redirect? What if someone looking for the Infusion Altar searches for Infusion altar instead? Wouldn't it be better to leave the redirect? . ƒelinoel_ 19:20, 22 March 2014 (CET)

Unlike with misplaced punctuation the search function will actually fix caps when necessary. For example, if you search for "infusion altar" all lowercased it will automatically redirect to Infusion Altar. This will obviously not work with wikilinks, but I don't think that correct caps is too much to ask. --dgelessus (talk · contribs) 19:26, 22 March 2014 (CET)

Don't we have a standard for this? --Kahless61 (talk) 17:20, 23 March 2014 (CET)

Well, we have the standard of always using the in-game caps for titles. Apart from that, not really. Somehow I doubt though that any of us want to create all-lowercase redirects just to allow slightly easier linking. --dgelessus (talk · contribs) 17:28, 23 March 2014 (CET)

That's precisely why we have the standard, to prevent doubling up the pages on every article just to have redirects for proper capitalization. --Kahless61 (talk) 18:32, 23 March 2014 (CET)

Hives

I don't understand why the Hives page was removed. I had been trying to look up information on the nether wasp hives and was unable to find any on this wiki and I had wanted to create one for other to use. What might I be able to do to create such a page that wont be deleted?

When you created the Hive article, you copied it directly from another site. You're not allowed to do that because of copyright issues, so dgelessus deleted the page. If you write an article about hives in your own words based on your observations, it will be kept. --timrem (talk) 01:15, 10 April 2014 (CEST)

Usage vs Uses

Project:Style Guide/Blocks and Items says the section is called Usage, not Uses. Just wanted to let you know ;) -- OstPavel (talk • contributions) 22:30, 25 April 2014 (CEST)

Of course we can always propose changes at any time. . ƒelinoel_ 20:59, 8 May 2014 (CEST)

Of course then we'd have to change all of the pages that already follow the guidelines ^_^ ~~ RZR0 (Talk | Contributions) 22:24, 8 May 2014 (CEST)

Of course. ƒelinoel ~ (Talk) 08:10, 12 May 2014 (CEST)

Re: anons spamming articles with links to outside websites getting only a three month ban

I'm particularly biased against anons and would have banned him for quite a bit more than three months, any particular reason why you chose the three? This is a legitimate question of which I actually am wondering your thoughts and am in no way being sarcastic or demeaning by intent. ƒelinoel ~ (Talk) 21:44, 26 September 2014 (CEST)

Back when I was promoted to admin I had no idea what would be a good ban time, and someone else (don't remember who, probably ost) was always using 3 months, so that's what I kept using for link spammers. Most of them never come back, if they do I usually ban them forever. --dgelessus (talk · contribs) 23:53, 26 September 2014 (CEST)

Changes to pages I've edited

I am quite confused why you would limit the information templates I created on several Traincraft pages. I was trying to get the community to not only provide basic information, but also information on crafting and usage of the items in question, please change them back. —Preceding unsigned comment added by DJHonore (talk · contribs) at 16:51, 2 December 2014

As far as I can tell the sections I removed were empty or had only placeholder content. I wasn't trying to limit your edits in any way, but having three practically empty sections on a page is not very useful and makes it look more cluttered than otherwise. There's nothing wrong with adding information such as the item's recipe (we even have templates for blocks like the Train Workbench) but please don't just add placeholder sections with no useful content. --dgelessus (talk · contribs) 18:15, 2 December 2014 (CET)

Stackable in infobox

So I finally am getting around to starting the concepts article type for things like aura and vis and Witchery spells and just about anything else that wouldn't fit in other infobox types and I can't seem to remove the stackable output, can you take a look for me? I have to wonder if it is caused by that invoke at the beginning?
http://atlwiki.net/Template:Infobox/Concept
ƒelinoel ~ (Talk) 18:43, 19 January 2015 (CET)

Maybe you should inherit from {{Infobox}}. {{Infobox/InvItem}} is intended as a base for things that are actual items that you have in your inventory (hence the name). I was going to add a few more always visible parameters to that infobox, mainly the internal/unlocalized name (e. g. minecraft:stone), but I can't test that very well without the code editor working. --dgelessus (talk · contribs) 19:01, 19 January 2015 (CET)

I wasn't sure if there was something else that would be more applicable but thanks for your edits to it. ƒelinoel ~ (Talk) 22:10, 19 January 2015 (CET)

Norton antivirus spam.

Can we have a mass deletion of the pages made this afternoon-ish, Ive gotten through about 8 of them but there are still about 25 left. ex:Tips_Of_Antivirus_On_Line_Protection_Unveiled_2021Imanton1 (talk) 05:35, 18 February 2015 (CET)

User:RZR0 seems to have done the rest of the work. Thanks for helping out though. :) --dgelessus (talk · contribs) 18:28, 18 February 2015 (CET)

I've also implemented a system that should prevent any more spam from being posted. ~~ RZR0 (Talk | Contributions) 23:11, 18 February 2015 (CET)

About my Seared Faucet page edit

Hi! I am simply informing other players that this might occur, is there some kind of policy about not posting bugs here? if so that's a bit weird because you should give the user relevant info, witch this is. If you want i can just remove the "Report to mod author" part if you want. —Preceding unsigned comment added by Valle641 (talk · contribs) at 09:16, 8 April 2015‎

Bugs can be listed on the wiki, but only if they are known to happen for most people and are relatively major. Getting stuck in a block happens all the time, even in vanilla Minecraft. Regarding the redstone problem, that sounds more like strange but correct redstone mechanics than a bug. It would be better to first of all ask on some forum whether the setup is correct, and then if you're sure that it doesn't work like it should, report the bug to the mod author. --dgelessus (talk · contribs) 14:34, 8 April 2015 (CEST)

Template:Infobox/InvItem

Why are the extra fields labeled as "Deprecated" when things like the Module template can use those without having to make an entirely new template? . ƒelinoel_ 17:17, 23 April 2015 (CEST)

Oh I see it says rows should be used instead, how do you use rows? Can you see how I use it on Biting Belt and adjust it to use rows? . ƒelinoel_ 17:18, 23 April 2015 (CEST)

It's very simple. For every row you add a {{Infobox/Row|<title>|<value>}} to rows. For example:

Best Item Ever
Name	Best Item Ever
Tooltip	Some witty text
Durability	42

{{Infobox
|name = Best Item Ever
|rows = 
{{Infobox/Row|Tooltip|Some witty text}}
{{Infobox/Row|Durability|42}}
}}

This works with all Lua-based infoboxes. Though I might just add "tooltip" as an optional parameter to InvItem. --dgelessus (talk · contribs) 18:55, 23 April 2015 (CEST)

Done, there's now a tooltip parameter that you can use. (Along with a few others, check the doc page history.) --dgelessus (talk · contribs) 02:38, 26 April 2015 (CEST)

Hmm, this looks broken, just when I needed it. =P ~~ RZR0 (Talk | Contributions) 01:29, 8 May 2015 (CEST)

No idea what's going on there. All I know now is that calling next on frame.args always returns nil for some reason, even though the table is clearly not empty. Think I need to sleep :P --dgelessus (talk · contribs) 02:19, 8 May 2015 (CEST)

PS: RTFMing is also quite helpful. frame.args is an empty table with special metamethods to get its real contents. This means that next doesn't work as I imagined. Now to figure out how to use pairs instead. --dgelessus (talk · contribs) 02:31, 8 May 2015 (CEST)

Modpack infobox

The modpack infoboxes no longer seem to work, I saw you moved all of the infobox code to lua yesterday, could that have something to do with it? ~~ RZR0 (Talk | Contributions) 17:11, 24 April 2015 (CEST)

Indeed it does. Totally forgot that the mod/pack infoboxes still use the old functions, I'll quickly fix that now. At least the infobox templates produced nothing at all instead of ugly broken wiki markup. --dgelessus (talk · contribs) 18:20, 24 April 2015 (CEST)

Yeah, I liked that, though it was a bit disorienting :p ~~ RZR0 (Talk | Contributions) 18:29, 24 April 2015 (CEST)

Removing the note at the hardened glass page

Hello, I hope this is the right place to ask! I saw you removed my note about putting the obsidian block in the casting basin yourself, and I was wondering why or how should I word it better the next time so it won't get removed? I added it because I spent an hour figuring out why I can't make hardened glass, and it was because I didn't put the obsidian in there myself but rather made one with molten obsidian. Which causes the recipe for hardened glass NOT to work. I thought it would be important to add. —Preceding unsigned comment added by 178.85.127.93 (talk · contribs)

There was nothing wrong with how you worded the note - I just thought the template shows the difference already. The obsidian block is shown as an item, and the lead as a fluid. The smeltery doesn't output blocks, just fluids, so the block must already be on the casting table. This is also how casting recipes are shown on other pages, for example Iron Ingot. --dgelessus (talk · contribs) 17:23, 27 April 2015 (CEST)

If it is made in a casting basin (as described) rather than a casting table (as pictured), then you can get a block of obsidian in the casting basin by first pouring in molten obsidian. And because of the way tinkers' works, that obsidian would be in the output 'slot' of the casting basin rather than the input 'slot' (as you get when placed by hand), which would cause the recipe to fail. That the two 'slots' are visually indistinguishable makes it a bit confusing, but you can tell they're different because of cases such as this, and by how the basin interacts with pipes. --timrem (talk) 17:48, 27 April 2015 (CEST)

Well that's basically why I asked, because my reason for adding the recipe was because of the note: I had to spend quite some time figuring out you had to put the block there yourself :( and I wanted others to prevent that from happening. —Preceding unsigned comment added by 178.85.127.93 (talk · contribs)

OK, that makes sense, I didn't know about that. I've readded the note (slightly reworded) and changed the template to the Casting Basin one. --dgelessus (talk · contribs) 13:01, 28 April 2015 (CEST)

Thank you very much!!! —Preceding unsigned comment added by 178.85.127.93 (talk · contribs)

No problem. FYI, to sign your post on a talk page, you can type --~~~~ after your message. The wiki software will replace that with your signature and a timestamp. The {{unsigned}} template is meant for posts of other people who forgot to sign themselves, not for your own posts. ;) --dgelessus (talk · contribs) 19:36, 29 April 2015 (CEST)

Ore dictionary

I saw you removed the Iron Gravel Ore recipes from the Iron Ingot page. Is there any way we (currently/can) display these ore dictionary mappings? ~~ RZR0 (Talk | Contributions) 17:48, 11 May 2015 (CEST)

Ore dict names are (theoretically) tracked using {{Infobox/InvItem}}'s oredict parameter, though as you can see that feature isn't used very widely. ;) In general I don't think it's very useful to list all ore dict alternatives in recipe grids though. If the "main" item for that ore dict name (e. g. Iron Ore for oreIron) is used consistently, it should be clear that ore dict alternatives can be used as well. There are of course recipes that don't use the ore dict (for example when it comes to components that you wouldn't necessarily expect to be oredicted, like gears or circuits) but those aren't very common. I'm not a big fan of displaying all the ore dict alternatives in an animation like NEI does either - it's annoying enough that half of all gold nuggets show as gold oreberries if you have Tinkers' Construct installed. On a wiki that covers lots of mods the situation would be even worse. --dgelessus (talk · contribs) 22:00, 11 May 2015 (CEST)

So I assume the goal is eventually to link to an SMW page listing all of the alternatives from an ore dictionary enabled page then? ~~ RZR0 (Talk | Contributions) 23:42, 11 May 2015 (CEST)

I'm not sure what would be a good way to display ore dict mappings. I've been thinking of making extra pages for ore dict names, but there's little info that could go on there rather than the item articles. For names with a clear "main item" it would be logical to have an "Ore Dictionary" section with a {{Usage}}-style list showing all other items with that ore dict name. --dgelessus (talk · contribs) 00:04, 12 May 2015 (CEST)

Is {{Usage}} tied into it? For example, if I have the Usage template on the Iron Gravel Ore page, will it list the recipes that take Iron Ore as well? ~~ RZR0 (Talk | Contributions) 12:41, 12 May 2015 (CEST)

Not at the moment, I'll need to see if that would be possible. Though for the moment you can use {{Usage|Iron Ore}}. --dgelessus (talk · contribs) 13:04, 12 May 2015 (CEST)

Meanwhile the oredict parameter use situation is slowly improving. ;) ~~ RZR0 (Talk | Contributions) 19:56, 26 May 2015 (CEST)

Mods navboxes

I think it might be a good idea for mods navigation templates to use the Module:ModNames same way as {{ModLink}} do. If it possible to do that? So for example {{ModNav|te}} will insert {{Navbox/Thermal Expansion}} into the page. --Ginpachi987 (talk) 11:50, 14 May 2015 (CEST)

Done. It is possible to use #invoke inside a template call, which made this easier than I thought and didn't require any additional Lua code at all. --dgelessus (talk · contribs) 20:37, 14 May 2015 (CEST)

Cool. Thanks. --Ginpachi987 (talk) 22:36, 14 May 2015 (CEST)

Smeltery Recipes

I created a grid template for the Smeltery the other day and implemented it on the Molten Iron page. There's some discussion about whether or not we should be listing so many recipes, but they're not ore dictionary recipes, so I think we should. ostPavel and gxam want to replace (part of it) with a table, I'd be interested in hearing your opinion. My main concern is having the recipes tied in with SMW. This might be messy if we use a table? ~~ RZR0 (Talk | Contributions) 13:12, 14 May 2015 (CEST)

I guess this might be a solution... Template:Substitute ~~ RZR0 (Talk | Contributions) 19:05, 14 May 2015 (CEST)

Iron is the only metal with that many recipes though. Items like hoppers, iron bars, cauldrons, minecarts, etc. only exist in iron form and won't have extra smelting recipes for the other metals. Most metals can't be used to make tools and armor either, so for those there would only be smelting recipes for the corresponding ore, nugget, ingot and block. That's four recipes per page in most cases, which I think is okay. --dgelessus (talk · contribs) 20:48, 14 May 2015 (CEST)

ID Names

Some items have rather long ID names, like the Cobblestone Structure Pipe. Looks kind of messy... Got any ideas? ~~ RZR0 (Talk | Contributions) 04:51, 15 May 2015 (CEST)

Module:Infobox/InvItem now inserts zero-width spaces before punctuation characters in ID names, this should encourage browsers to wrap them there. My only concern is that the zwspaces are real characters and will persist if you copy the text, making the name unusable when pasted in-game as part of a command. If that is too problematic the CSS property word-break: break-all; could be used, though that would result in some ugly line wrapping behavior. --dgelessus (talk · contribs) 17:12, 15 May 2015 (CEST)

The space characters do indeed persist after pasting in-game. ~~ RZR0 (Talk | Contributions) 17:19, 15 May 2015 (CEST)

Do you think it's okay to use zwspaces then? The more I think about it I don't like how it causes problems when copy-pasting... Should we use the "wrap all the things" CSS option then? Any idea if there is a way to allow wrapping at a tag break? For example <span>foo</span><span>bar</span> won't wrap because it is a single word, do you know if there is a CSS property to allow that? --dgelessus (talk · contribs) 00:26, 16 May 2015 (CEST)

I haven't got a clue, CSS isn't my thing. But I'll try to look into it. ~~ RZR0 (Talk | Contributions) 01:08, 16 May 2015 (CEST)

Machine recipes

I was thinking, what if we register all outputs for a Grid template to the block for which the template list the recipe. Then we could, like {{Usage}} does for inputs, also list what items can be crafted with a particular machine. Think that's a good idea? ~~ RZR0 (Talk | Contributions) 21:34, 24 May 2015 (CEST)

Sounds reasonable. Of course it doesn't make sense to list all recipes for e. g. the macerator, but for machines with only a few possible recipes this would be useful. I'd say we add an extra named machine parameter to {{RecipeSubobjects}}, we can't make it an unnamed one as that would break everything. --dgelessus (talk · contribs) 21:44, 24 May 2015 (CEST)

Well, I was thinking that either we actually display the items on the page (with a limit like Usage), or we make a template to insert a link to the list for the machine. ~~ RZR0 (Talk | Contributions) 21:55, 24 May 2015 (CEST)

Yes, the recipe list template for the machine pages should be like {{Usage}}, with a limit and only showing the output items. With the current tracking system it's not possible to reconstruct the actual recipes from the SMW subobjects alone, for example the recipe for an iron pickaxe only creates the subobjects "Iron Ingot -> Iron Pickaxe" and "Stick -> Iron Pickaxe".

Another question, how should the section be named? "Recipes" would be logical, but that is very similar to "Recipe". Any other ideas? --dgelessus (talk · contribs) 02:11, 25 May 2015 (CEST)

We can register the outputs in the Grid templates, maybe by adding a new template to do that. As for the name... Recipes does indeed make sense. But maybe something like "Creates"? ~~ RZR0 (Talk | Contributions) 19:58, 26 May 2015 (CEST)

Lua named params

Hey, I'm working on Module:TConMaterial to place on pages such as Wood Planks, to specify the TiC properties for materials, but I'm having a hard time getting named params working. I've tried using getFrameAndArgs(), but I didn't have much luck. Could you help me out or explain how to work with that function? ~~ RZR0 (Talk | Contributions) 01:16, 31 May 2015 (CEST)

getFrameAndArgs isn't necessary to use named arguments. It's just a convenience function that allows passing in args in various ways, which makes testing *much* easier. Generally it's used like this: local frame, args = g.getFrameAndArgs(). This makes frame a frame object on which you can call methods like expandTemplate, and args a normal Lua table containing all arguments. Positional/numeric arguments are accessible as args[n], and named arguments as args["name"] or args.name.

(The args returned here is a table with real elements. The default frame.args gets the arguments on-demand for performance reasons, but that makes it impossible to use most basic functions like next or unpack.) --dgelessus (talk · contribs) 14:31, 31 May 2015 (CEST)

Hmm, well, why don't my params get passed to Module:TConMaterial when I call Template:TConMaterial? ~~ RZR0 (Talk | Contributions) 17:52, 31 May 2015 (CEST)

I can't see any different with the Item template and Module:Infobox/Item... ~~ RZR0 (Talk | Contributions) 19:17, 31 May 2015 (CEST)

Huh, works for me. The property assignments are invisible, so you won't see anything when invoking the template. The wiki markup is produced correctly though - try running this code in the interactive Lua terminal:

=mw.getCurrentFrame():expandTemplate{title="TConMaterial", args={name="<arg for name>", durability="<arg for durability>", miningspeed="<arg for miningspeed>"}}

--dgelessus (talk · contribs) 20:00, 31 May 2015 (CEST)

Strange, it throws an error for me, the name property should be assigned before passing it to the method in there... User:RZR0/Test ~~ RZR0 (Talk | Contributions) 20:07, 31 May 2015 (CEST)

That's referring to the parameter name of the p.getSMW function, not args.name. When you call the template, p.getSMW is run three times. The first time it is called with args.name as the name parameter and runs without problems. The second time it uses args.durability as the name parameter, which is nil (because you omitted that argument in the template call). Now it tries to concat a string with args.durability, known to the p.getSMW function as name, and errors because you cannot concat string and nil. Long story short: if you want to allow parameters to be left out, you need to check whether they are nil (and provide some default value or replacement) before using them anywhere else. --dgelessus (talk · contribs) 23:29, 31 May 2015 (CEST)

I feel so stupid right now >_< ~~ RZR0 (Talk | Contributions) 23:50, 31 May 2015 (CEST)

OreDict spacing

Is the spacing between OreDict items intend? ~~ RZR0 (Talk | Contributions) 20:05, 20 June 2015 (CEST)

Not that much of course. It seems that divs already go on separate lines on their own, so the br makes the spacing unnecessarily large. --dgelessus (talk · contribs) 01:29, 21 June 2015 (CEST)