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?! 

And adjust that in-game for best quality. Gamma 0.8 should be good. I would NOT alter brightness and contrast.

About level names: I asked before, why should they be uppercase? 

 

In the source, all is lowercase: http://inside3d.com/browse.php?show=world.qc 

And you clearly never tried to "map E1M1". 

 

Remember that in the quake console font, both upper and lower case letters are rendered as uppercase letters of different sizes. This probably explains the difference between people who are internally converting "ᴇ1ᴍ1" into "E1M1" and the people who convert "ᴇ1ᴍ1" into "e1m1".

Obviously the solution is to use the small-caps unicode characters to render them as they appear in the console: ᴇ1ᴍ1 

I can't see a time when you'd ever need both for the articles. Having everything lower case seems like the best idea. 

It needs to be consistent. Either all capitalized or all lower case, but not mixed as it is now. There've already been accidental duplicates and there're going to be more without a consensus.

Regardless of the ingame font, the levels have always been named E1M1 since Doom or even Wolfenstein, so it can be considered a common convention, I think. 

Just make some consensus as how to capitalise multiple word titles. Case solved?

The was one conflict (vanilla quake) I know of. Other problems are only because the old articles are first letter upper case.


Quake is case-sensitive and so are many file systems. Try "map E1M1" in the console. 

Meanwhile, I've messed up the Recent Changes list. 

in a way like messing up the hair of a wonderful girl though. nice!

I don't remember, should those have a gpl header?

clearly the wiki needs quakec syntax highlighting. there are extensions with geshi, anyone know of an add-on for that or something?

spawn is a great example for case sensitivity. we could have spawn for the function and Spawn for the monster. with cross links. no one ever would get confused by that!! 

I actually prefer 100% lower case, since it's 100% unambiguous, whereas with upper case, you have to worry about the correct case of a word with regard to the sentence it's in, which leads to grammatical errors creeping into article titles and grammar Nazi's getting angry*.

The article title can be fixed using {{DISPLAYTITLE:Correct Title with _Underscores_ and all}}, although I found this sometimes doesn't work...

* I am not a grammar Nazi, since I like the qualifications to be one. 

I'm trying to get conditionals to work:

http://en.wikipedia.org/wiki/Help:If#Conditional_expressions
{{#if: {{{parameter_not_null}}} | yes | no }

No luck yet. Are they supported?

Starbuck: Are you thinking of changing the style of the tables etc. that we are using? It might be good to make a couple of test css classes for tables and infoboxes so that we can use them for our templates. I don't know how to do it and it's best if you think about it since you've been doing the overall site design. 

You can see installed extensions at http://quakewiki.org/wiki/Special:Version

I will install that one right now.

Be aware that Wikipedia is a website that uses Mediawiki. So if you want to google about functionality, google for "mediawiki something". Then it should be more easy to see what is supported out of the box. Confusion�. 

spirit, don't bother converting the old ones, it'll just make it harder to make the entries because i'll have to go check if they are good and then reformat them to fit the current format i'm using (java api). 

Too late! You posted that just as I ran the script.

I dumped a list of conflicts here: http://quakewiki.org/wiki/User_talk:Necros

Some are conflicts with than's stuff too. 

As I was testing, I noticed that #if is now supported!

http://quakewiki.org/wiki/monster_shalrath

The content is a bit dodgy, but I'm trying to tidy up the page template a bit.

By the way, who is Hectate? Does he post on func or hang out in #terrafusion? Would be useful to be able to contact him more easily. 

No idea but he is in #qc regularly (irc.anynet.org).

I love what you are doing with the monster&entity pages!