Good, I will add more in depth information about how the plane points are interpreted (point order, normal computation) and about floating point vs. integer coordinates tonight. 

What than said! There are at least two more duplicates: info_null and info_notnull. The older (capitalized) articles were submitted by me a couple of years ago, the newer ones by Quaketree.

The Into_null one also made me aware of a critical aspect about writing style. All general wiki articles should be written in a neutral tone, not addressing the reader. So instead of "You can...", "do not...", or "use this", it should be something like "It is possible...", "it should not be done", "it can be used.." etc. 

It's only plagiatism if the content is used in a way that suggests authorship of the wiki editor. Those certain texts can still be used as citatations, with a little footnote about the source. A possible compromise. 

http://quakewiki.org/wiki/Textures

I CITED MY SOURCE

(metlslime, if you are reading, plz to have permissions) 

Do you work at the university & publish papers?

Generally, I agree with you on style, with the exception of tutorials and other articles where it indeed makes sense to address the reader directly. 

You know that thread with all those crazy QC tricks and hacks? might it be an idea to get all that stuff in the wiki? I found it really interesting and illuminating at least, even if some of it wasn't tremendously practical. 

you have permission to use my text, but you seem to have lost some of the information from the original article in your rewrite. e.g. the fact that vis.exe looks for both "*water" and "*04water". And the fact that power of 2 dimensions are not required, just recommended. Maybe other things too, i just skimmed it. 

Level 0 

I did skip that it looks for *04water... It was a choice to say that power of 2 dimensions are required, as I believe it's just simply better to state that as that's what modern GL engines want anyway. 

negke: Plagiarism was not the issue, not having permission to fully copy works regardless of displaying the authorship is.

http://www.mediawiki.org/wiki/Manual:$wgCapitalLinks is the option I enabled because I thought it would be super fantastic for all the variables, entity names and so on. If you guys want it off, say it sooner than later because it will require fixing links. 

plz :( 

I only mentioned it, because scampie brought it up. 

I added a stub article called Map_based_hacks. I don't know if that's the right name for QC tricks done in a map, so feel free to move it somewhere else.

http://quakewiki.org/wiki/Map_based_hacks

Also, re: tone, I agree that neutral is best for most articles, but tutorials are probably best in a more informal style, such as that used by Scampie. All the stuff I have written is fairly neutral - probably because I waste a lot of time on Wikipedia.

Also, I added some content to the Quake article last night:
http://quakewiki.org/wiki/Quake
http://quakewiki.org/wiki/Quake_story

The small section I wrote on custom levels on the Quake page needs fact checking. I don't actually know the real circumstances of the QuakeEd release, whether id made a Windows port or how the tools were released etc. I also remember a couple of maps made in text editors (!!!) such as daskull.

Another thing, I originally put a link to the Wikipedia article on Quake II, since I assumed we are wrtiting a purely Quake 1 wiki, but I later changed it to an internal link since we might want to have a short description of each sequel, as they are still related to Quake 1. Again, feel free to change that back to a wikipedia link if we are definitely not have any Quake II or III content. 

id released the QuakeEd and tool sources, but did not port them to windows, it was up to the community to do so. 

id released the QuakeEd and tool sources, but did not port them to windows, it was up to the community to do so. 

Sorry, random BS - was thinking along the lines of how it wasn't obvious that Quaddicted already was a wiki. 

Was originally written in Objective-C for the NextStep system. It was most certainly not ported by id. Wasn't it Robert Duffy who did the (or a) port and then got hired by id as a result? 

it would be nice to get this either as a link or right on there: http://ouns.nexuizninjaz.com/dev_programming_introduction.html#working_with_the_code

setting up an ide like codeblocks for quakec basically increased productivity by like 10x. 

A way to set up code blocks to develop whatever recent engine everyone is modifying (mark5? Quakespasm?)

By the way, is there any way we can upload arbitrary files to the wiki? Should we put them on Quaketastic etc?

For mapping tutorials, we need to have source maps etc.

Also, I recommend for the mapping tutorials to only ever use stock Quake textures, except in specific instances where the tutorial is about making textures, or non-standard textures such as skip etc. That's probably how stuff is at the moment, but I thought I'd just suggest it anyway. 

I added some more file extensions but please only use this if you need the files as references in pages or example material for tutorials. Do not upload tools and such. Mention the source and if possible the license of uploaded things if you did not make them yourself.

than: I noticed you seem to think that some rules exist for naming? I think you linked to a Wikipedia guide somewhere but could not find it right now. That is Wikipedia, not this Wiki. ;) 

http://www.celephais.net/board/view_thread.php?id=37116&start=275

I started this page and added an example. Please add more to it! 

spirit: i'll try to merge the old and new ones. i have no idea how to reply to you on the wiki itself. :P 

Edit the page and add a new line with a : in front makes nice thread discussion. More :: as applicable. :D

Thanks!

I will run a script to convert all the variables and entities that were added in the old wiki with a upper case first character to the "proper" capitalisation later. Only Scampie voted against it and that ain't enough! ;) 

If you add screenshots of any kind in articles, please make sure they are bright enough for everyone (=increased brightness and contrast)! Keep in mind there are different types of monitors and settings, and the pictures are shown on a white background which further influences their visibility.

Currently, some of the pictures are very dark, too dark in my view. Than's level shots are good, though. 

While capitalized entities look strange to me, too, I'm inclined to vote against lowercase articles. If only for the sake of compatibility. Why are the level names ("e1m1") lower case as well?!