In regards to trick submissions, it has come to my attention that several of the demos submitted have been cheated by way of physics alteration or timescale. This is not acceptable, and these demos will be discarded accordingly. I urge anyone who has submitted a trick that falls into this criteria to re-record your trick in non-devmode or in a live game. I can not accept cheated material in anyway shape or fashion, and any and all materials proven to be cheated will be removed from the post roster.

Demo: roflcopter_ctf1_demo.zip (5 clicks)

Demo: Marco_van_Basten_QZCTF4_3StrafeJumpsToYellowArmour.zip (7 clicks)

Demo: kittenignition_qzpractice2_s-curve_proxjump.zip (8 clicks)

DEMO: megaddd_ctf4_demo1.zip (5 clicks)

You can find the Video and more on the Videos page.

you can also find the interview from TastySpleen.tv here.

• First, if the demo is lengthy, then include a README.txt file with the time of the trick. Doesnt have to be exact but id like an approximate time to start looking. Include your quake alias, and a email address so that i can contact you later if needed.
• Second, make sure to rename the file with the following format so I know who it came from.playername_mapname_trick_time.dm_73Mapname is important.

If you have a really simple trick that you are submitting then what will probably happen is I will either save the trick or combine the trick with a whole set of tricks to create a demo worth watching.

Now then, do you know how do a specific trick or fast capture that helps in game? Then why dont you show everyone else how you do the trick. Do this by recording yourself doing the trick, and include a README.txt file with the above noted items and a explanation as to what you did. Feel free to add as much detail as you feel is needed. I will take the demo(s) you sent and create a tutorial demo from it with your explaination of the tricks idea and how it works. If you would like a specific song used as background music in the tut then please list the song you want used in the README.txt. DO NOT SEND MUSIC WITH THE DEMO.

When a demo is posted, it will be listed by the map first then the trick, then who did it. Please refer to previously posted viewer submitted tricks for example.

If you submitted a demo, and it hasnt been posted then fill out the contact form, and ask what happened with the demo and make sure to give the demos name and description of the trick, as well as your quake alias.

NOTE:

Do not submit demos that have altered physics, used timescale, or thirdperson.  Any demo found to have been recorded in this way will not be posted.  This is cheating and it is not acceptable.

Due to some life experiences that loveless has been forced to deal with, loveless has handed the movie over to me to finish. Ive got all the capturing completed and im working on the editing and soundtrack. Ive teamed up with Tritin Films to include some nice 3d touches to the movie. The original release date was middle to end of Feb, and im officially announcing that the release date has been pushed back to begining/mid of April.

GPlayLive:

Ive been working on some nice additions to the script and I am hopeful to release the new version in the next few weeks. Still have alot of testing. If your interested in testing it, please drop me a note via the contact form or post a comment.

Base Website:

Ive been also working on a several new features, plugins, and of course a community demo submission and archive listing that will be both public and privately managed. I am on the lookout for a graphics designer to build a new fresh look for the site and to be welcomed onboard the staff. All applicants for the graphics designer should submit contact information and a small portfolio to the contact form.

QuakeCon:

Ive been asked by lots of your guys if I or any q3schools staff will be attending the event. At the moment whether or not i attend the event is still in the air. But should something happen so that I plan to attend the event I will be sure to announce it here on the site.

Demo: q3schools_qzdm17_teleporter_rjs_beefjerky (9 clicks)

Demo: q3schools_qzca3_wallbug_tritin (5 clicks)

Demo: q3schools_qzctf2_flagroom_tactics_kimmygibbler (10 clicks)

Demo: q3schools_qzteam1_itssimplyscout_kimmygibbler (5 clicks)

Demo: q3schools_qzctf9_flagroom_shortcuts_kimmygibbler (7 clicks)

Demo: q3schools_qzctf4_2newconcepts_kimmygibbler (7 clicks)

Demo: 3easy2usejumps_qzteam6 (7 clicks)

Demo: Scornforge-Basejump (6 clicks)

Demo: kimmygibbler_qzteam3_bridge_strats (5 clicks)

Seems like id for got to clip a ceiling in qzpractice2. Well, its pretty much pointless but still has some classic value because this bug will be fixed soon after id developers see this vid. Props to 10ghz for a sweet find.

Demo: q3schools_10ghz_qzpractice2_wallbug (10 clicks)

Enjoy!

[See post to listen to audio]

Mega caught me in game and said “I got a trick that is not posted on q3schools”, so I was like send it on, and here it is. Not a difficult trick but it looks awesome in first person and it definitely gets the girls wet! =)

Demo: megaddd_stunt2.dm_73.zip (9 clicks)

My config is modular or OO “Object Oriented”. So what is “Object Oriented”? Well in case your new to the code world there is a common phrase passed with in its realms which is ” Don’t recreate the wheel “. So if you want to learn more about what “OO” is then I suggest you check out http://en.wikipedia.org/wiki/Object-oriented_programming.

But why Object Oriented? I know what it is, but its not needed at all, the config works just fine the default way (which is top down style scripting). Well, using OO is not changing how the configuration works, its allowing for 2 things.

1. It allows for quick and easy editing
2. It allows for a much more robust and complex configuration that is not possible with the limitation and constraints of the default config reader

For example, if you have a set of large vstrs such as a auto insult script it will take away from the allowed number of lines to be read by a single config, thus causing an error when the config is loaded. Large configs also cause lag as of the amount of items that are put into the system memory from the configuration.

Now before you use my config or try to read over it, let me explain how it all works. But first lets make sure we take a good look at a list of cvars and commands used in the vq3 based games. A good detailed list of cvars and commands can be found at http://www.holysh1t.net/quake-live-commands-list/, or if you want to just get the list yourself to check for consistency you can use the following line in your game console. If you dont know how to get to the console, I recommend you google it and read over the newbie guide to quake configs. Holysh1t has a great one here.

/clear; listcvars; listcmds; condump cvarcmdlist.txt 

//The file cvarcmdlist.txt will be created and stored in your baseq folder.

First part of the config, the part that you actually execute is the “main.cfg”.

//-------------------------->
// @file main.cfg
// @author Newbi
//-------------------------->

//step 1, unbind all previous aliases used by the default or previous config.
unbindall

//step2, call the list of modules used in the config, ex.the binds.config.
exec modules/autotroll.cfg
exec modules/binds.cfg
exec modules/gfx.cfg
exec modules/player.cfg

//step3, announce that we successfully loaded our configuration
say "Newbi's Config v.1.0 Loaded Successfully!"; say "www.q3schools.com"

//alternatively you can use "tell_buddy (your player name)"
//to tell yourself instead of publicly announcing your config loaded.
//tell_buddy Newbi Config Loaded Sir!

Now lets look at the autotroll.cfg script.

//-------------------------->
// @file autotroll.cfg
// @author Newbi
//-------------------------->

set autotroll "vstr ins1"

set ins1 "tell_attacker Your Momma was a snow blower!; set autotroll vstr ins2"
set ins2 "tell_attacker My gun is bigger then yours; set autotroll vstr ins3"
set ins3 "tell_attacker You couldnt whip a fly with a flyswatter!; set autotroll vstr ins1"

Now lets look at the binds.cfg script where all of our aliases and in game commands are stored. This part is important because the “unbindall” command will wipe out our current bindings so its important that you include all of your binds in this file. The following example will only list a few of the possible binds to be used.

//-------------------------->
// @file binds.cfg
// @author Newbi
//-------------------------->

bind w "+forward"
bind s "+back"
bind a "+moveleft"
bind d "+moveright"
bind c "+movedown"
bind mouse2 "+moveup"
bind v "+button3"
bind BACKSPACE "+button2"

//custom commands binds
bind \ "vstr autotroll"

Next lets look at the player.cfg. This script will house all of our “player specific” settings.

//-------------------------->
// @file player.cfg
// @author Newbi
//-------------------------->

seta name "^2O^5nykag^2e"
seta model "keel/default"
seta headmodel "doom/default"
seta cg_forceenemymodel "tankjr/bright"
seta cg_forceredteammodel "mynx/default"

And finally lets look at the graphics settings configuration file. This is where the look and feel of the game is presented.

//-------------------------->
// @file gfx.cfg
// @author Newbi
//-------------------------->

seta r_vertexlight "1"
seta cg_drawfps "1"
seta cg_draw3dicons "0"
seta cg_noprojectiletrail "0"
seta r_picmip "3"
seta r_fullbright "1"

And that will complete the demo package. Now when you want to edit something or add a cvar, just put it in it perspective place and its always so easy to work on and alot easier to read. Not to mention its cleaner and doesnt lag your game session as much.

Now for you lazy bastards that just want to use my config Ive published it for you so you can both view it and download it. I would recommend that you at least attempt to design and build you own config. It will really teach you alot about the game itself and it may even help you find that little edge you have always been looking for. Click here to see Newbi’s Actual Quakelive Config.