If this is not possible may I offer that I provide hosting somehow? Its very difficult for me to get a hold of the voxel people if you have interest in this please message me on skype. username: Chamunks

http://voxelwiki.com/index.html I suppose I should have been more verbose. The wiki explaining the different brushes and things is just simply gone. This text only raw dump is a bit rough.

This does simply not belong here. We're working on it.

Yes I'm aware and I'm sorry its just very difficult to contact you all please I would love to volunteer anything that I can I've been idling in irc for about 2 weeks patiently waiting and I can recover some of it via the wayback.archive.org but its no replacement.

I think using GitHub wiki would be more convenient and then we can sidestep the IT issues. I've forked and added a wiki here. @Chamunks you're welcome to contribute formatting to the wiki pages. That would be much appreciated. I'm going to get back to breaking Voxelsniper documentation into multiple pages after I finish some landscaping. Thank guys, awesome tool!

While github's wiki feature is really good I do actually think it'd be better to have an in-source based documentation. It is much easier for devs to update the documentation of a feature they just changed if the documentation was somewhere in the source tree (possibly an orphan branch). - I was looking into Read the Docs (https://readthedocs.org/) earlier this year but just haven't had time to migrate the old documentation.

GitHub has a special branch called gh-pages that is designed to host images and documents that are referenced from the wiki. If you put HTML in your gh-pages, you can just create a dummy front page on the wiki and then link to that. Then changes to the docs are just good old fashioned commits. Of course, you don't get a free HTML editor that way, so it depends on your setup. I suppose ReadTheDocs is more featureful. Whatever you decide, I'll be happy to help. I'm a mod developer and I consider VoxelSniper a mainstay of the Minecraft community.

My main issue is who has the imagery from the page about brushes. Those infographics were very helpful illustrating what the different brushes do. Like things with the CopyPasta brush etc. It would be brilliant if we could start getting this stuff all glued together.

Also I love the idea of self documenting code. But in the mean time lets not set ourselves up learning curve barriers up and just get the documentation starting to come back together. To be honest it clearly looks as though you guys no offense have no desire to really repair the website or at least drive to do so. VS is too awesome to let die like this.

Can you please just drop this. As @MikeMatrix already said, "We're working on it". We're building an entirely new site which will be a centralised home for all the Voxel Mods and Voxel Plugins, it will include all of the documentation and more. Please stop flogging this ticket, it's not going to make things happen any faster, we are friends with the current admins of The Voxel Box and thus have access to the old wiki contents, including the images, so your concerns are completely unfounded.

To be honest it clearly looks as though you guys no offense have no desire to really repair the website or at least drive to do so. VS is too awesome to let die like this.

No offense? What on earth are you on? How can being told that it's being worked on (and that this request doesn't belong on GitHub in the first place) be construed as "letting it die", and how can you possibly think that that statement isn't offensive?

It's being worked on, as originally mentioned right at the top of this thread, please stop resurrecting this ticket.