Oh, I'm loving the new wiki. I've always thought mediawikis were much more cleaner.

I'll help as much as I can to transfer existing material over to the new wiki.

Oh, the wiki refers to the editor as 'Voxode' because I spelled it wrong. Sorry about that. :P I'll take a look at the new wiki shortly.

EDIT:
I've added a bunch of links to non-existent pages on the wiki, so please go ahead and fill them in with content.

I've also appended the above 'tips and tricks' as a sub-section of the editor's page, though I'm not sure how you guys want to have everything look. I've never really worked on a wiki before.

Alright, it looks like the new wiki is good to go then. I bumped the php memory limit up to 40mb -- Let me know if you still have trouble uploading large images.

Parser extensions look nice, but do we really need them? I want to keep the installation as clean as possible so it's easy to maintain, as I think it will become a crucial resource. I'm open to persuasion though -- could you give me an example of when they would be useful?

Also (I'm a bit of a noob at this) -- how does the templates thing work? Is it needed to allow importing stuff from the existing wiki in the same format? If so, I'd rather just manually reformat it (for similar reasons)

I'll take a pass over the editor section in the weekend and add some more prominent links to the wiki early next week.

Im a bit noob at templates as well, but to my understanding, no, it is not needed, in fact, I easily ported the box template I did to this wiki, others failed a bit, but the formatting problem goes only for templates. Copy pasting articles from the old wiki will work, as long as we have replicas of the old wiki's templates in the new one.
The problem is, the wiki has no basic, pre-installed templates at all. Some of those are needed for custom templates, and some are just useful for pages (like the stub one).
Copy/Pasting all of them is a load of work, so the idea is to import them from another wiki that is similar to the one we intend to create (I would suggest minecraft's).

ParserFunctions would be vital to me. I have crafted a monster page template which includes a list of behaviors each monster exhibits, such as if it can jump, shoot, or break voxels. Unfortunately, without ParserFunctions, it is currently completely impossible for me to automate this to ANY extent, instead I am forced to rely on clumsy manual template input to populate the list.

Compare:
{{Monster|Alien.png|8|damage=y|jumps=y|shoots=AlienShot.png|shotsbreak=y|evades=y}}

{{Monster|Alien.png|8|behaviors=* Damages player on contact

• Jumps
• Shoots [[File:AlienShot.png]] which breaks voxels
• Attempts to evade the player's projectiles}}

The newlines are non-negotiable, and this list needs to be made consistent/extended across each page manually, particularly if the wording of some lines are changed or additional representative icons are added.

I wonder if alternatively I could call templates for each behavior from inside the template to pass them? That kind of thing sounds completely ridiculous.

I'd love to help out if I could!

@Rammite can you edit your original post to include the proper link to the new wiki? It's a pain searching through to find it each time when you don't have it bookmarked.

I would love to be able to help out the wiki. I am very bored with the game (too much playing), and played most of the player created levels. I would like to be able to help out at the wiki. I will start by editing pages now.

I did not italicize text on monster pages... What? You mean the additional notes-type thing at the bottom? I suppose. It was mostly there because I couldn't think of a decent way to add in things like the movement speed or other interesting unique features of a particular monster that don't really fit into any of the generic behavior checkboxes, you know?

Actually, since every monster has SOME particular movement speed of relevance, generally either being very fast or very slow (or in the Alien's case, both) it'd still be better to have a section of the template specifically to give the speed in some distinct measure of units. I don't know, voxels per second?