7 Days to Die Wiki


Crafting Grid Removal[]

Controllish (talk) 22:32, 22 January 2016 (UTC)Hello, Can you please stop removing the outdated section of every page? It links to other search pages that still use the grid to grab the item and show it. When you remove the grid you also removed the recipe from the info that the lists pull. I put them at the bottom of the page to allow the other pages to grab them, but still not be in the way of the new info.

Thanks, CodyControllish (talk) 22:32, 22 January 2016 (UTC)

Controllish, there's no need to use the grid any longer. If other pages link to the grid, those references should also be pulled. The grid is obsolete as of A13.

GrayBeard_Actual Mcwresearch Avatar.png (talk)

12:35, 27 January 2016 (UTC)

General Crafting[]

Hey GrayBeard_Actual. Hope I don't bother you, but the Crafting page is a little bit outdated. I wrote down a suggestion for an updated text on the diskussion page, since the actual page is not editable. I hope you can transfer it to the actual page. Thanks alot. --CrimsonSchizoidMan (talk) 18:07, 23 March 2016 (UTC)

No bother at all! I have applied your proposed changes. Thanks for the help and let me know if you need anything else. GrayBeard_Actual (talk)

A14 Note about shooting arrows[]

Why was this reverted? It was correct and my first edit wasn't. Projectiles *can* be shot trough Iron Bars, but arrows can not as they're classified as rockets now. -- 14:44, 31 March 2016 (UTC)

I assume you are talking about the page Iron Bars, correct? The only change I made to that page was to rename the section previously-titled "A13 Notes" to just "Notes." The comment regarding shooting through them in A14 remains. GrayBeard_Actual (talk) 08:45 April 1, 2016 (GMT+8)

Apologies, I forgot to let you know about the reskinning[]

This new skin is supposed to match a bit better with the new look of the game and the logo. — Game widow (talk) 15:54, 8 April 2016 (UTC)

I like it. GrayBeard_Actual (talk)
I'm relieved :) Let me know if you find anything that still needs a tweak — Game widow (talk) 12:54, 11 April 2016 (UTC)


Is there a list of the new icons for a15? I noticed you uploaded some for new pages I have created. If I create any more new pages I'd like to link them to save more work for someone else. Phoenix830

As I add the images, I will assign them to this category: Category:Alpha_15_icons (I'm going back and doing that to previously added icons now). There is also a list of icons and page titles here: Community Portal: Alpha 15 Icons. From there you can simply click the red link to create the page.
If you create a page that needs an icon that I haven't yet uploaded, drop a link in a message here. I have some time over the next few days to spend on the wiki so I hope to be more active in the near future.
Thanks for your help!
GrayBeard_Actual (talk) October 7, 2016


Can you block IP addresses temporarily? This address keeps spamming:

Exitwound 45 (talk) 16:46, 16 October 2016 (UTC)

I just placed a two-week block for Thanks for cleaning up after him!
GrayBeard_Actual (talk) October 29, 2016

Looks like we might be chasing this one for a while. I just added another block for

GrayBeard_Actual (talk) November 1, 2016


Today I temporarily blocked

GrayBeard_Actual (talk) 23:31, 5 December 2016 (UTC)

Infobox fields upgrade.[]

I would like to propose the creation of a number of new fields for working out if an item has been updated, or and when it was created.

  1. added_version: This would be the version of the game that this item was created.
  2. removed_version: This would be the version of the game that this item was removed from the game. Has the same function as the removed field, but include the version that the item was removed.
  3. updated_version: Contains the version of the game that the item was last changed.
  4. confirmed_version: This contain the version of the game that the item was last check for compliance. So on creation, it would be the same as addedversion (or blank). If a new version of the game is created then this field could be updated to show that it has been checked against the that game version.

I would actually suggest that these type of fields are needed for all the Infobox types. — Tilleen (talk) 05:05, 11 November 2016 (UTC)

I think that's a great idea. Are you comfortable making that change? GrayBeard_Actual (talk) November 12, 2016
I can make it to the Infoboxes with out any problem I expect. I don't however know all the information for filling them in. — Tilleen (talk) 06:22, 12 November 2016 (UTC)
May be worth auto-categorizing things as well. — Tilleen (talk) 06:40, 12 November 2016 (UTC)
I have changed these to be of the style added_version to align with the rest of the parameters. I have noticed that there is already a removed parameter and template so not sure if I should add the removed_version parameter. — Tilleen (talk) 20:19, 13 November 2016 (UTC)

One option may be to replace the removed parameter with the more specific removed_version parameter—basically a name change. If you make that change, you'll also have to go through and change every item that uses the old removed parameter, unless you add extra code to the infobox to accommodate both versions of the parameter.

It looks like you are getting the auto-cat'ing set up.

GrayBeard_Actual (talk) 06:31, 14 November 2016 (UTC)

I expect that what should happen is new items get created with the removed_version field but the code still understands the removed field.
I have added these fields to the Locations and NPCs infobox types, and have added appropriate code, changed ones I could find etc. Have a look around and tell me how this is looking.
Is there any way to treat a field as a list? So that for the updated_version field it can have multiple values, that can then be used scaned through? The only thing close I have found is the #titleparts which allows a field to be processed based on the / character?
Tilleen (talk) 22:37, 15 November 2016 (UTC)

I haven't done that before. I just tested the updated_version parameter and see that it is lumping all the different versions into one auto-category. Is that what you are working to fix? If so, check out the explode function. Maybe you can explode the value given for the updated_version parameter based on some sort of field separator (could be whitespace), which is what I think you are referring to when you mentioned the slash "/" of the #titleparts (I'm not really sure what that is).

GrayBeard_Actual (talk) 06:05, 16 November 2016 (UTC)

Alright the #explode is exactly what I was looking for. I have set up in Template:Infobox_npc/Sandbox my function for autocreating version Categories based on a comma separated list of version in either the updated_version or confirmed_version.
I was initially only going to have them have a single version string, but it did not seem that was a good idea, or very useful. A test Zombie is here: Zombie_Test/Sandbox.
It may be worth considering if the Infobox_items template needs to have this for its categorization of things like "Tool, Weapon".
I am not sure how much extra strain this puts on the webserver/wiki generator.
I will roll the changes into the main Infobox_npc and Infobox_locations if you think they are stable.
Note: it will fail (stop processing) if someone puts in a number of commas in a row e.g: Version,,,Version2 I could remove duplicate commas but there are too many options too make it very worthwhile.
Tilleen (talk) 08:35, 16 November 2016 (UTC)

It looks good! Well done. I don't see any reason why you can't roll it out immediately. The documentation looks good as well.

I'll be away from the Internet for the next two days, just so you are aware, but I don't think you'll have any problems deploying this infobox to existing pages. One test you might try, if you want to be extra-cautious is to copy all of the information from a live zombie article into a sandbox to see how the infobox is laid out with all other information and also you can plug in "live" parameters into your sandbox infobox and then compare the layout of the live zombie page and your sandboxed page with the new infobox. If it all looks good to you, you can deploy it.

And remember; no changes made here can not be undone. =)

GrayBeard_Actual (talk) 00:14, 18 November 2016 (UTC)

These fields have been added to all infobox types. Take a look around and make sure I have not overstepped.
I or someone will need to update the Help:Removed_Items documentation to match the new system.
I have put in a suggestion to upgrade the Recipe template to include the used tool (Workbench, Campfire, etc....) and a used feature of that tool (I am having trouble naming it). It may be worth having the number of items that are produced as well, for instance, Mushroom spores produce 2.
Anything else that I can help with?
Tilleen (talk) 02:44, 23 November 2016 (UTC)

I took a look at a few pages and so far the new fields in the infoboxes look good! Nice job.

If you are looking for something else to do...one of the things I had on my list was to normalize all the groups and categories to match the XMLs. It will take some planning and will take some time and it certainly isn't "sexy" but it may help with organization of pages and will certainly make DPL searches more effective (DPL searches power many of the list pages).

If that doesn't strike your fancy, feel free to pick anything from my messy to-do list. =)

Thanks again for your help!

GrayBeard_Actual (talk) 08:13, 24 November 2016 (UTC)

I have noticed that (specificly with the group field) some fields use the Validate list field, however if we follow the definitions in the xml, then that field can have multiple values. I was wondering what is the best way of dealing with this?
  1. Have multilple versions eg, group1, group2..., however that will make it difficult to search consistently for any field. (Unless it is possible to have multiple fields with the same name eg., |group=xxxxx, |group=yyyyyy.
  2. Change the Validate to handle multiple values, (ie check the list as a comma separated list, rather than a single value). Would fix the validation and autocat, but may cause issue else where, list the issue with the type field.
  3. Have individual boolean fields for all the legal possible values.
Tilleen (talk) 03:52, 22 December 2016 (UTC)


How do I delete spam: https://7daystodie.gamepedia.com/AduPoker88_Games_Judi_Texas_Holdem_Poker_Online_IndonesiaTilleen (talk) 21:06, 15 November 2016 (UTC)

Unless you are an admin, you can only delete the pages you create, I believe. To delete pages, use the "More" button.
I have deleted the page above. Thanks for the heads-up!

GrayBeard_Actual (talk) 05:50, 16 November 2016 (UTC)

sub block variant redirects[]

Do you think this is spammy or just a decent stop gap solution to the different block types for one block? For example Metal Sign and Adobe White Block

It feels like spam to make 26 redirect pages for Metal Signs, but I feel like the individual blocks need their own address, but not a whole new page.

I think the pages look perfect. I agree with you; we don't need a separate page for each letter of the alphabet nor for each different block of adobe white.
GrayBeard_Actual (talk) 08:06, 24 November 2016 (UTC)
I would suggest that as long as the stats are the same for all the different sub blocks then they can be grouped.
I personally would suggest that the wood railings should have their own as they have different crafting requirements from the cat walks, although they are an extension.
Tilleen (talk) 08:13, 24 November 2016 (UTC)
That's a good point; I didn't consider differences in recipes. GrayBeard_Actual (talk) 04:02, 4 December 2016 (UTC)

Looking to help, need info[]

I needed to take a look at the Craftable Building Material page and found that it was incomplete and in no order that makes sense. I thought I'd reorder it and add what I found was missing, but it's using a template that pulls data from elsewhere. I did a bit on the DayZ wiki and learned quite a bit of syntax and whatnot there, but I've never had to work with something like this. Could you point me in the direction I need to go to learn what I need to to fix it? I've been skimming through the help sections, but haven't seen what I need to to work on this page.

Thanks for your time. Scur827 (talk) 14:24, 1 December 2016 (UTC)

That page uses DPL, or Dynamic Page List. All of our Category:List-Pages use them and they are quite useful.

For a quick-and-dirty breakdown of how DPL is working on Craftable Building Material:

|category = Building Material Searches for all pages in Category:Building Material
|uses = Template:Recipe that utilize the recipe template
|include = {infobox item}:image, {infobox item}:category, {Recipe} dpl, {infobox item}:unlocked and extracts certain values from the recipe to include in the list

The rest of the code in that particular DPL is formatting, which I usually just ripped from other DPL searches.

To get you started on fixing the list, I would suggest verifying that missing materials have the following:

  1. Are categorized as Category:Building Material (can have other categories assigned)
  2. Use the Template:Recipe

By simply adding those two items to a page, it should get populated in the DPL.

As I worked through learning DPL I tried to keep notes and DPL searches that I built. Feel free to take a look at those notes here.

Let me know if you run into major snags and I'll try to help.

One tip: when you are working with DPLs, previewing and saving your changes will update the DPL so the data in the DPL is fresh. However, DPL searches can be taxing on the server so you want to make sure that once your DPL is done and dusted, it includes |allowcachedresults=true in order to "play nice" with the server.

Lastly; I never had any luck figuring out how sorting worked. It was never predictable or consistent and I never had a real need to figure out what I was doing wrong.

Thanks for taking this one on and helping to clean up the list!

GrayBeard_Actual (talk) 03:45, 4 December 2016 (UTC)


Wow, I was just hoping for a link to a help page or something, excellent info, thank you.

Ok, that clears up a ton, even without hitting your notes yet. I'd be surprised to find there was no way for a DPL to display according to the order of certain fields, there's probably a way to order even further using multiple fields, seems like a very logical command/operator/something to include in any db tool. I'll do some hunting.

--Scur827 (talk) 15:03, 4 December 2016 (UTC)

Update: Well, that was easy...

|category = Building Material
|namespace =
|uses = Template:Recipe
|include = {infobox item}:image, {infobox item}:category, {Recipe} dpl, {infobox item}:unlocked
|secseparators = ¶¦ 30px %PAGE%,¶¦,,¶¦,¶¦,
|multisecseparators = ,,
|format={¦ class="wikitable sortable"¶!Item!!Category!! class="unsortable" ¦ Required Materials!!Unlocked Through,¶¦-,,¶¦}

All I added was the ordermethod parameter, that's it. And I can put as many secondaries in as I wish. This parameter really needs to be spread around a bit.

As for missing items, seems like a good time killer to dive into here and there.

And again, thanks for the headstart.

--Scur827 (talk) 16:14, 4 December 2016 (UTC)

With DPL that uses the table and tablerow parameters you can use tablesortcol=.
I am a little confused, which is the column that |ordermethod = title refers to?
Tilleen (talk) 21:13, 4 December 2016 (UTC)
When I sort by title, it makes the default sorting by article title, which is named after Item var. The ordermethod parameter uses article information, not item information. So it isn't sorting by the actual column info it's pulling, only the article (page) name, which is fine as long as folks stick to naming the article pages after the items, as they always should. :)
--Scur827 (talk) 21:38, 4 December 2016 (UTC)
I feel like I should add that this only affects the initial listing order. Without this parameter, the default list order is in the order that the pages were parsed.
--Scur827 (talk) 21:45, 4 December 2016 (UTC)
(Sorry I'm abusing your page here, GrayBeard)
After reading up on tablesortcol, it seems to me that it there are a couple of good reasons to use ordermethod before tablesortcol. Ordermethod simply changes the order of the output of the parse, while tablesortcol must search through all the output and then reorder it. So ordermethod reorganizes, tablesort has to perform a search and then reorganize. Tablesortcol will also take hidden characters into account. While that probably wouldn't ever be an issue, and a minor one at that, well, I'm a fan of neat and tidy pages.
--Scur827 (talk) 22:00, 4 December 2016 (UTC)

"Sorry I'm abusing your page here, GrayBeard"

Not at all!! This is a great conversation—I'm learning loads and the wiki is getting much-needed attention! You guys rock—and not just those involved in this discussion, but everyone (like JonPardon to name one) taking the time to make the tedious, boring, but necessary adjustments to pages.

GrayBeard_Actual (talk) 23:02, 5 December 2016 (UTC)

Changes to recipe template/sandbox[]

I have made a few changes to the recipe template Sandbox to see if including the workplace, implement and schematic to them could be made to look any good. See here:Template:Recipe/TestcasesTilleen (talk) 22:56, 8 December 2016 (UTC)

That looks good and conveys information in a useful manner! Nice! GrayBeard_Actual (talk) 02:10, 9 December 2016 (UTC)

Regular page corruptions.[]

I have twice fixed the doc page for the Template:Recipe in the past 24 hours.
Why do we allow random people to update pages?
Tilleen (talk) 23:39, 8 January 2017 (UTC)

Thank you for cleaning up the vandalism and you have a good point; hi-impact templates should probably be restricted to signed-in users only. I've locked down a few of the templates, but it'll still be a game of whack-a-mole. GrayBeard_Actual (talk) 06:24, 8 February 2017 (UTC)

Hello, Have you seen a way of adding 2 header lines to a dpl table? (not format and secseparators)

Tilleen (talk) 04:31, 28 January 2017 (UTC)

I'm not sure on this one... GrayBeard_Actual (talk) 06:24, 8 February 2017 (UTC)
I'm not sure what you mean by 2 header lines. do you mean two rows at the top of a table that are both header rows? or 1 header row at the top, then another somewhere farther down the table? — Game widow (talk) 13:21, 22 March 2017 (UTC)

Rename reversion[]

I've been told that if you log out and back in, things should sort themselves out. Let me know how that goes (there was apparently an instance of your old username - Mcwresearch - listed in a nickname field on our authentication system which was overriding your namechange. This has been blanked) — Game widow (talk) 21:38, 20 March 2017 (UTC)

That did the trick. Thanks again!
GrayBeard_Actual (talk) 02:30, 21 March 2017 (UTC)
Glad to hear it! — Game widow (talk) 13:20, 22 March 2017 (UTC)

Updating wiki information to current information regarding A16[]

Hey there, I've posted this on a couple other admin's pages so far but you seem to be the most active, so I'll just post it here too-

Hello, I was recently looking through some pages of this wiki and have found that not a lot has been updated to the latest version (Alpha 16), and have tried to edit the pages accordingly. When trying to edit out misinformation for the new update, a message pops up saying I do not have sufficient privileges to remove sections that are no longer valid the the current info regarding the game. Any change you could get in contact please? If you are worried I might spread misinformation myself, I have been playing this game for an extremely long time and have racked up numerous hours in it (600+ hours) and know exactly what I'm talking about.

In order to help, I'll need to know what pages and sections you are trying to edit. — GrayBeard Actual (talk) 23:33, 7 August 2017 (UTC)

Updating the wiki[]

Hello! I'm having the same problem as the guy above me. I'd like to update pages but it says I don't have privileges to do that. I'm also not sure if it would help sending every page and section I'd like to edit to you as I usually edit them as soon as I see them. Thanks already!

If you are a brand new editor, the filters are a little restrictive, but after having made 3 edits, things loosen up considerably. Try making 3 very small edits and saving after each and see if the issue persists. If so, please paste the exact error message you get here — Game widow (talk) 13:30, 3 March 2018 (UTC)

Introducing myself as the new Wiki Manager[]

Hi, this is just to let you know that I am taking over Game_widow as your Wiki Manager. Feel free to contact me if you need anything.


Addition to server hosts page

URL: https://7d2d.net/ Minimum Price Per Slot/mo: $0.37/slot Minimum Slots: 8 Control Panel Type: Custom

Features: - 7 Day Money Back Guarantee - DDoS Protection - Instant Setup - Locations: France and Canada - No Branding - Live Support - E5 Processors with 64GB RAM