Wikihack:Community Portal

Welcome! Use this page to discuss general topics with WikiHack members.

Another way to contact Wikihack is to send mail to our mailing list, or leave comments on the talk pages of individual users.

Other NetHack communities include:
 * rec.games.roguelike.nethack - the newsgroup, see rgrn
 * #nethack on irc.freenode.net - see Freenode

Archives of this page: 1

[ Post a new section]

Commented / uncommented source code categories
I think the source code pages should be categorized based on whether they are commented or not. When all pages are commented (probably not within this year), the scheme can be completely removed. Until that, it would be a helpful aid in knowing what pages still need comments. Maybe Jayt's bot could do the categorizing? Before the bot uploaded them all, all source code pages that were added were commented pretty much right away. --ZeroOne 10:49, 9 July 2006 (UTC)
 * I don't think any of the source files are fully annotated yet. Artifact.c looks about 20% done; maybe we could add a note to that effect on Source code, like this:


 * allmain.c
 * alloc.c
 * apply.c
 * artifact.c (20% annotated)


 * AFAIK, all the annotations have been by Kernigh. Kernigh, would you like to track your progress on Source code, with notes like the above? :-) --Jayt 00:13, 10 July 2006 (UTC)


 * Kernigh writes: I might start doing something like that in the future. Note that "100%" would probably only mean that every function is documented somehow, but someone might still want to perform cleanup or make corrections or add more thorough documentation. For example, the paragraph under artifact.c, about invoking the Staff of Aesculapius, neglects to mention that is causes a "You feel better" message.


 * Meanwhile, anyone can look through the source and add percentages to the source code page. --Kernigh 02:18, 11 July 2006 (UTC)


 * If we are going to use percentages then I suggest we borrow the 5-stage concept from Wikibooks. Replace the word "text" by the word "comments" and start adding those little images next to those links! 87.5% would round up to 100%.
 * About your second point, it's just that it's a really tedious process, there being hundreds of source files. That's why I suggested a bot could do it. It shouldn't be too difficult, just compare the number of lines that are source code against the number of lines that not source code, right? --ZeroOne 02:33, 11 July 2006 (UTC)
 * I like the 5 stages ("sparse annotations", "developing annotations", "maturing annotations", "developed annotations", "comprehensive annotations"). If we add stage 0 to the beginning ("no annotations"), we can just let an empty space stand for that. Since the great majority of files are not annotated, that means a lot less work. --Jayt 13:59, 11 July 2006 (UTC)
 * I'm planning on automating the addition of monster data to wikiHack. As a stepping stone project I could write a script to parse the source code and display the annotation status of each file next to its name. I see two options


 * Option 1 - put a single line at the top of every code file indicating its annotation status. ie: or, where the letters a,b,c ... correspond to ("sparse annotations", "developing annotations", "maturing annotations" ...). The script would parse each source file biweekly and update the annotation status on the index page.


 * Option 2 - run a one time script on the index page to put a status code next to each file. Whoever annotates the code should update the status.


 * -- PraetorFenix 21:05, 2 August 2006 (UTC)

Dylan O'Donnell spoilers
While these are a great resource, I don't especially like the mass copying of them here. It's redundant. The idea of the wiki, as I understand it, is to do and say things text-based spoilers currently do not. Interface alone doesn't seem like enough of a difference. Lotte 17:33, 20 July 2006 (UTC)
 * A goal of the wiki for me is to make it a "total spoiler", where you can find any piece of information about the game. If all information is going to be added eventually, we may as well add it in a structured way, and I think the DOD spoilers are great in that respect. However, they are not perfect: there are at least two ways we can improve them using this wiki: wikilinks, and commentary/strategy. The text-spoilers are very conservative in offering only facts, with no opinions. I think we can relax that a bit and have a Comments/Strategy section on every page. --Jayt 22:24, 20 July 2006 (UTC)
 * I agree with Lotte in that I hate the spoiler look. They are too abstract and concise. It's impossible to learn anything about playing the game by reading one. They always remind me of the parts catalogues in auto body shops.


 * I also realize that the spoilers contain good information. They are a great reference (once you understand them) because they were written by experts for experts. It's the format and presenatation that sucks. They are a great starting point as long as we reformat them and collate the information in a meaningful way.


 * -- PraetorFenix 21:05, 2 August 2006 (UTC)


 * Is it pages like potion of object detection you don't like? How would you go about changing them? --Jayt 22:40, 2 August 2006 (UTC)


 * Sorry for the delayed response. I wanted to writeup a sample article on potion of acid but did not get the chance. It's not the potion of object detection pages that are bad. It's pages like this one. All the object detection page needs is more commentary and moving the canonical messages into their ouw section. -- PraetorFenix 02:23, 5 August 2006 (UTC)

WikiHack upload bot
I would like to upload a set of images and articles to WikiHack and would like a bot to automate the process.

Please point me to open source bots. My first preference is for bots written in C++, with Perl a close second. I am willing to learn Python if bots in the aforementioned languages are not available.

Also, I am new to wikis in general. Please point me to resources about writing and managing bots on wikis. I have a great deal of programming experience, so I am not looking for a coding tut, rather I want an explanation of how bots and wikis communicate with each other.

Thanks in advance -- PraetorFenix 19:40, 27 July 2006 (UTC)
 * There is lots of info for you to digest about Pywikipediabot, a set of python scripts designed to do pretty much exactly what you want, by the sounds of it (one of them is upload.py). This wiki is powered by Mediawiki, the same software that wikipedia uses, so pywikipediabot fits in nicely.


 * The most important thing about running a bot is not to let it run rampant! Do a few test runs first, and discuss it here, on this page - there is a chance that you have something crazy planned which the rest of the community would like the chance to dispute :-). So what do you have planned? --Jayt 21:42, 27 July 2006 (UTC)


 * I have some time this weekend and I was planning on uploading all the x16 graphic tiles. There are 764 tiles in all and I have managed to split them into images correspondence to their NetHack names. See Wikihack:NetHack Tiles for the index. When I do run the bot, do I need a delay between each upload? -- PraetorFenix 19:59, 28 July 2006 (UTC)


 * You should probably upload as User:PraetorFenixBot and write on that user page what the bot is doing. 764 uploads will flood Recentchanges whether you wait 2 minutes between uploads or not; I suggest a minimal delay, as then it will be flooded only for a few hours.
 * The page should be simply Tiles, since it's about NetHack, not Wikihack. I also think it will look nice when it's done! --Jayt 21:23, 28 July 2006 (UTC)


 * I moved the page to List of vanilla NetHack tiles. I think tiles could be a separate article discussing them, listing alternatives etc. The list is a reference-like article. --ZeroOne 22:02, 28 July 2006 (UTC)


 * Well, ran into some delays. Who would've guessed that the python scripts needed additional configuration before they would run :). Anyway, it's late so i'll turn in for today. The images will be uploaded tomorrow. I've created a new category for them 'NetHack Tiles x16'. In the meantime I wrote this article on running wikihack:wikiBots, enjoy ;)


 * The image 'Image:Horse.PNG' has to be deleted or renamed.

Ideas for improving monster?
The monster template, in use on soldier ant and hopefully soon to be in use on owlbear, is big and ugly. It's unabashedly based on the Monster Manual, but not completely. It doesn't include the line of supplementary information, like "A wererat has no hands. It can regenerate itself. etc." It does include near-useless information like Frequency and Difficulty. Finally, its length makes it interfere with section titles below

I suggest a shorter infobox for the top of the article:

This gives a quick appraisal of the major things you need to worry about (how tough it is, how easily you can hit it, how fast it can hit you, and how hard it can hit you).

Then, at the end of the article, we can have a ==Detailed stats== section which contains the full Monster Manual table, and all info about what kind of hands it has and all that.

Does anybody have any better ideas? --Jayt 18:08, 30 July 2006 (UTC)
 * Looks good. Could the 16x16 tiles go there? In a lot of articles there just isn't a good place to put it and in my opinion at least they look awkward just slapped randomly into the text. Lotte 23:47, 30 July 2006 (UTC)
 * Kernigh writes: When I check monster spoilers, I usually want to know whether to eat its corpse. I like Jayt's short, simple version of monster, and I agree with Lotte that we should include tiles, but I suggest fitting in one more line, something like this: --Kernigh 16:58, 31 July 2006 (UTC)


 * {|class="wikitable"

! Corpse
 * Poisonous, gives poison resistance
 * }


 * OK, I added a corpse line. The new template is monsterbasics. I've updated owlbear to use it. monster still exists for the full infobox, but I see PraetorFenix has plans to auto-wikify this data, which I greatly encourage, as there are 250+ monsters. --Jayt 21:25, 31 July 2006 (UTC)


 * One piece of information I have failed to find from anywhere is, whether polymorphing into a certain kind of monster breaks your armor. The size obviously isn't the only criteria as, for example, winged gargoyles are human-sized but their wings break the armor anyway. Two other pieces of information of some interest to me are the food the monster eats (can it eat metal/rocks) and what special abilities other than attacks does the monster have - dragons fly, xorns have the phasing ability, etc. Although I'm not sure if any of these would merit their place in this template. Maybe they just need to be mentioned in the article. --ZeroOne 02:40, 1 August 2006 (UTC)
 * I am strongly in favor of the short info box as I think the ant template is too clunky. Once everyone decides on the templates and information therin I am planning on writing a script to parse the code and automatically place the template the monster page.


 * Now the top of the page should have a mini template, but this does not mean that there should only be one template. We can include several templates in a page. I'm thinking in terms of three templates. A small one at the top that lists critical information that's frequently checked. A medium one with corpse data and other releveant info about the monster. And a canonical one listing all the other monster data at the bottom of the page.


 * I would like everyone to be happy with the end result and have the information they need represented in the templates. So before we proceed we should find out what information players are looking for.


 * Here's my suggestions
 * {|class="wikitable"

!width="10%"| !width="80%" colspan="2"|Bug Bear !width="10%"| !colspan="2"|Base level !colspan="2"|Base AC !colspan="2"|Speed !colspan="2"|Attacks !colspan="2"|Attack Resistances
 * colspan="2"|5
 * colspan="2"|5
 * colspan="2"|12
 * colspan="2"|Claw: 1d6 Claw: 1d6 Bearhug: 2d8
 * colspan="2"|None.
 * }


 * Now I would like the glyph and tile to be at the extreme ends of the table but could not figure out the html.


 * {|class="wikitable"

!colspan="2"|Corpse !Nutrition !Effects !Conveyances !colspan="2"|Attributes
 * 50
 * Is Poisonous
 * poison resistance
 * colspan="2"|
 * has humanoid head/arms/torso
 * omnivorous
 * strong (or big) monster
 * picks up weapons and food
 * visible by infravision
 * has infravision
 * }
 * }
 * }


 * -- PraetorFenix 21:05, 2 August 2006 (UTC)
 * Where would you put the Corpse infobox? Somewhere in the middle of the page?
 * In your example, the Attributes are really those of the monster rather than its corpse, and surely belong in the Full Info box.
 * Are a monster's attack resistances really Important? I'm not sure. I think the Important infobox should be about what the monster can do to you, not what you can do to it. Hence the AC line probably doesn't belong there either. I would much rather strip this box down to the basics than have all possible relevant info creep in. A well-designed Full Info box should make it easy enough to find out any additional information, especially if we place it at the end of every monster page - then the procedure for finding out corpse info is: 1) type in monster name, 2) scroll to bottom, 3) voila. --Jayt 22:40, 2 August 2006 (UTC)
 * I've also changed the code in your suggestion - something about having a table within a table was breaking the whole page layout. I'm afraid it doesn't look quite right, but I'm no HTML/CSS expert either. FWIW, I think having the name of the monster here is redundant since this box is going right at the top of the page, just under the page title, which is the monster's name. --Jayt 22:56, 2 August 2006 (UTC)


 * I changed the html of the table even further - I believe it looks now like it is supposed to.
 * Here's just an idea: we could use only one template, if we had a way to hide the lesser-used information. See Wikipedia:AutoWikiBrowser for an example of such a behaviour. Scroll to Version history: it says "Select show to expand". If we could reverse-engineer how that works, well, wouldn't it be cool?
 * Jayt: I think it is not redundant to put the name of the monster in the box in case there are several monsters on the same article, such as piercer or mummies. --ZeroOne 23:24, 2 August 2006 (UTC)


 * I followed the instructions here for a showhide template, and have it working with my user CSS/JS. It's going to need a lot more tweaking to get it working nicely, but it looks good! What a great idea! :-) Yes, you are right about the infobox needing the monster name. --Jayt 00:48, 3 August 2006 (UTC)
 * Update: I give up. I'm not a CSS coder by trade. If anyone wants to try making something neat, copy User:Jayt/common.css, User:Jayt/monobook.css, and User:Jayt/monobook.js to the same locations under your user page and edit Template:Showhide. I think what we really want is the ability to toggle between displaying two different divs rather than showing or hiding one. --Jayt 19:02, 4 August 2006 (UTC)
 * Hey, this is a neat idea ZeroOne. Thanks for finding the code Jayt. I'll give it a shot, but I'm no web guru, so we'll see. -- PraetorFenix 02:26, 5 August 2006 (UTC)

Community Portal pruning
I made an archive page containing all the old topics. Please don't delete old conversations without putting them elsewhere! --Jayt 22:40, 2 August 2006 (UTC)