added qtdm3 and moved "autoexec.cfg" out of the frogbot.pak, making it easier to remove/modify the message on startup.

could u maybe add the loud mega health sound as default?

i don't think so.

why not? or am i being nooby? since it does gives players a disadvantage if mh sound is less clear.

I dont think that many people are using it, but its a matter of taste, I prefer the old sound thats in nQuake...

well it's not that hard to add yourself.

having good looking skins and map textures gives players a disadvantage as well, a much bigger one.

if you want an optimized pro quakeworld installation, don't use nquake.

updated ezquake to build 2017

updated ezquake to build 2020

added dm5a (double kenya)

Are you joking?

Sure not. The more unimportant details you see on the screen, the harder it is to focus at the enemy.

updated ezquake to build 2025

any update on installer? (association, etc)

Whats new in this version?

More bugs, as it's alpha build

up2, i'm too busy with school to even think about modifying the installer atm

but i can start thinking about how to incorporate it into the installer.

do you think it should have its own page?

if not, what page should it be stuck into?

should the associations be 1 checkbox, or 1 for each association?

i just update ezquake in nquake as often as i can, to keep it up to date.

that way ezquake gets more "beta testing" and people won't have to download ezquake separately if they want the latest version after installing nquake.

if some major bug is found, i will either update ezquake or replace it with an older, working version asap.

updated ezquake to build 2028

latest build seems to have broken bloom i loved that

Last night I installed nquake again to start all clear. I bumped into couple mysterious selections.

- Why does nquake v1.7d installer downloads ezquake 1.9 alpha(build 2028) and not the latest stable? Would be nice if nquake would use ezq 1.8.2 and security module for it. Both allowed for eql.
- Why defaulting cl_fakeshaft to 0.8?

2 very interesting questions But i think i can answere them:

1. There hasnt been a new release of nquake since 1.8.2 was released, it will soon come...
2. Its a misstake, cl_fakeshaft should ofc be 0 by defualt.

Best regards

1. because ezquake 1.9 alpha is the latest ezquake, "stable" or not, it has the most features. if a particular build of 1.9 is not recommended for use in nquake, i will of course "downgrade" to an earlier build.

2. because i've found 0.8 to be a good value for fakeshaft. it's a variable though so you can change it if you don't like it.

adding ezquake 1.8.2 to nquake + security module would not be a good idea, since i would then have to remove a lot of the eyecandy that is appealing to newcomers, which after all is the intended audience of nquake.

I agree on the first one but not on the fakeshaft thing. It's a bad start to get playing using the values half of the players hate. Just my opinion.

Thanks for your answers. I was just thinking...

fakeshaft is allowed in tournaments, so it doesn't matter if people hate it. if someone who downloads nquake dislikes fakeshaft, he can turn it off in 0.5 seconds.

downloaded this today, been a while since i played.. graphics look sick in this. high five!

I get a qizmo error when I have played a game and it wanna compress the demo from qwd->qwz.
The error is something with qizmo.exe cant be used, wouldn't it better if we took away the compression? (or am I the only one with this problem?)

another suggestion, I believe that the shaft sensitivity is to high, wouldnt it better if we lowered the sens for lg to 70% of the normal sens?
I believe that the rookies trying it out would be better shafters with it and therefor enjoy the game more

i get that shit that spams my console and chat box all the time. anybody know how to stop this?

yeah, perhaps. but then you'd have to think about how new players probably don't expect the sensitivity to change when using different weapons, so this could also confuse them a bit.


looks to me like the mod you're playing is putting too much crap in your info string. post this in the help forum and you can probably get some help with how to prevent that.

ok cool, i'll repost there. thanks man.

what about binding mouse3 (scroll) to shownick, you got it on zoom now