Signups are up and we hope you'll enjoy this season! Also a
BIG change in rules, read more by clicking on the link...
... First of all, WELCOME! We are back and ready to upload
some hot games on our site again!
Are GO! So signup your team for some 4on4 if you at least
have 4 active players that are really active. Requirements
of this season is that you have a squad that is capable of
playing 2 official games/week. As the activity has increased
really much lately we have no doubts that there wouldn't be
several, if not almost all capable of doing this. So in
reality this means less pracs and more officials than
This season will be LONGER, BIGGER and hopefully also
better. We will have TB3 as maps this season. So friends of
not kenyans should be happy!
This season is also longer than the last 2 seasons, we will
have ~9 weeks of regular season to play instead 6 as
earlier. But there is a reason for this -> Divisions are
bigger which means more games, more drama and of course more
fragging! Even if the season is longer you should be able to
field players more active than in the last two seasons.
Thanks to johnny_cz's KT Log Parser, fog added stats to the
match pages. So make sure to upload your .log-files when you
report games for some nice statistics!
Fuhquake, Mqwcl are not listed as accepted clients anymore.
Also versions before 1.9 of Ezquake have been removed. So
plainly explained: Only new Ezquake and FTE clients are
accepted. There will soonish be new clients (rumours) of
both clients which will have new f_ruleset to check for
cheats. So to make this crashlanding easier on fuh and mqwcl
users we have decided to remove them already instead of
midseason. Read more about it on the rules section.
Before these new versions of the clients are out we will
have to use following commands before starting our games:
f_skins (enemyskinforcing is illegal)
Yes, we know, it's lots of writing. If these procedures are
not done before game has started and other clients have been
used there will be points deductions! Also notice that Mqwcl
and Fuh will not answer to these commands.
Once again, read more about it at the rules section. Most
people should know anyways what those values should be.
Also if somebody doesn't have these settings as they should
then MAKE them change them. There are some huge advantages
of having these turned on/tweaked.
As earlier mentioned as it is a longer season we have also
increased the amount of players in a team to 10. Also
additions/swaps increased from 2 to 3. It wouldn't also hurt
to ask your mates if they are going abroad or similar things
to prevent losses of players during mid-season.
The WO-system is totally different, instead of giving points
for having problems with fielding players we are mostly
taking away points this season instead. So yes, you might
suddenly miss 3 points after 3 weeks or so. Don't be
surprised. In cases when Clan A has played against Clan C,
but Clan C has not been able to field players against Clan B
the admins might consider giving a "normal wo" to Clan B, IF
it makes a difference that the clans haven't played. Mostly
points deduction anyways.
..is not legal to use in EQL games. Later this season as new
clients will be up for use this will easily be removed. Be
FAIR until that and remove the existing ones in your
Hopefully you'll frag often and well!
Yours, the admins!
yeh, really hoping for a good season! from my side aswell
..I beat hagge to post \o/
#32009-01-28 09:20 by soma (134.130.50.XXX)
Awwww, no fuhQuake?! :(
#42009-01-28 09:22 by blAze (83.102.10.XXX)
Looks like more restrictions are being forcefed to the
#52009-01-28 09:31 by Zalon (80.165.18.XXX)
As always, rules are updated before season start, so people
can whine, and we can change it back in time. :)
#62009-01-28 10:51 by zapp (213.65.180.XXX)
Really it\'s all about the inability to check that people
are following some basic rules in those clients, if anyone
would take the time to make sure they respond to the new
f_ruleset there wouldn\'t be much of a reason to remove them
but as no one is working on them at all I doubt it\'s going
#72009-01-28 11:56 by JohnNy_cz (78.128.193.XXX)
ezQuake never announced, promised, not even mentioned that
there will be a new version that bans "strafescripts". Yet
again EQL makes public announcements of things that haven't
been discussed at all.
By the way, if you allow Qizmo, there is no point in banning
enemy skin forcing, as very similar functionality is
available via Qizmo color forcing, as you probably know.
#82009-01-28 12:13 by 1tsinen (85.156.193.XXX)
Well atleast I've understood that there will be a ability to
check if a player is using those strafescripts, correct me
again if I am wrong. And I apologize if that is not true
Qizmos will be removed as soon there are more new routing
proxies instead of the qizmos. Several servers that have bad
routing that can be solved with qizmos atm but don't have a
nicely routing "new proxy" :(
#92009-01-28 12:30 by fog (130.235.35.XXX)
Hmm Itsinen: There are a lot more qwfwd proxys now then
there were qizmos? Only host that doesn't have a proxy atm
(afaik) is CSN?
johnny_cz: "ezQuake never announced, promised, not even
mentioned that there will be a new version that bans
"strafescripts"." I think people made their own conclusions
based on the ezQuake nightly builds/SVN-builds, where it is
blocket when using allow_scripts 0.
Atleast I thought it was a fact, Renzo stated something
like: "Strafescripts will be banned anyway in ezQuake 2.0,
no need to use that #"%"#%6346 piece of shit" blaha blaha.
Saw him as a reliable source ;-)
As for scripts - no, at the moment (2.0 alpha version)
scripts containing movement commands are disabled, but
cl_iDrive 1 (which isn't checked by any check) emulates the
functionality of the "strafe script". The check could be
added as part of the new f_ruleset, but that wasn't planned
for the upcoming 1.9.3.
#122009-01-28 13:10 by Renzo (88.112.180.XXX)
"Atleast I thought it was a fact, Renzo stated something
like: "Strafescripts will be banned anyway in ezQuake 2.0,
no need to use that #"%"#%6346 piece of shit" blaha blaha.
Saw him as a reliable source ;-)"
The text above was stated because of two things:
1) I saw junior (johnny_cz) adding the feature in 2.0 alpha
since I and many others have been bitching about the script
and 2) I saw EQL admins take the same stance about it.
The fact that EQL admins actually want this enabled is
something they decided, however if the other part (client
guys) don't have proper client out then it's a bit
What are the reasons for banning mqwcl please elaborate.
#152009-01-28 16:04 by Zalon (83.89.93.XXX)
bUn, it doesn't support the new f_ruleset trigger.
#162009-01-28 16:26 by JohnNy_cz (78.128.193.XXX)
If you decide to disallow "new" (not controlled before)
stuff, it's only logical to require clients that can be
updated to reflect the requirements.
#172009-01-28 18:36 by zapp (213.65.180.XXX)
I really dont see the problem with clients being disallowed,
if people want to use them so much cant they spend the time
it takes to update them to support these few new things we
requier them to have?
#182009-01-28 20:55 by bUn (82.117.96.XXX)
lack of skill otherwise i would be on it right away
#192009-01-28 21:55 by Defcon 5 (85.127.231.XXX)
no kenya :(
#202009-01-29 00:16 by Stev (86.41.152.XXX)
#212009-01-30 09:34 by Hagge (85.226.47.XXX)
congrats peppe! :E
guess there will be no eql for me this season since I can't
get ezquake to work properly, thanks eql :EEE someone plz
start up nqr again \o/
#222009-01-31 02:19 by bUn (82.117.96.XXX)
i second that
#232009-01-31 20:20 by pleuraXeraphim (86.41.117.XXX)
Is fuhquake disallowed so ?
If so that rules me out. EzQuake wont work on my machine :(
#242009-02-01 03:14 by TiMMi (83.109.177.XXX)
I've not bothered much with the client discussion, but it
amaze me how many people that actually don't want to play
the game anymore cause they have to install ezquake. I dont
care much about what client people play with, but this kind
of attitude makes me think: GO FUCK YOURSELF, WE DON'T NEED
YOU. When that's said, I suggest fuh is allowed basicly
because I dont care if people cheat. If they do its their
problem, not mine. :) Though, this is my opinion, not
anywhere near the admins view. :>
#252009-02-01 09:53 by Elguapo (130.243.188.XXX)
Timmi, this is not about cheating. I am unfortuneatly with
Hagge and Pleura in that question since also for me, Ezquake
does not work properly on my machine. Thus I need to use
Fuhquake or I cannot participate! ALLOW FUHQUAKE! :)
#262009-02-01 12:11 by soma (134.130.50.XXX)
I'm in the same situation as pleura, elguapo and hagge. And
to claim that laziness is the only reason some people don't
switch to ezQuake is pretty nasty. =/
#272009-02-01 12:22 by 1tsinen (85.156.193.XXX)
Those who have mentioned problems with Ezquake should tell
us what the problem is and we might consider an exception.
If we don't get an explanation you will not have any chance
of beeing allowed to use it. Only one who has personally
reported and acceptable reason what I know is Soma. So those
who have problems with Ezquake contact admins and tell us
WHY we should make you and exception!
#282009-02-01 13:38 by Slajer (86.61.25.XXX)
"f_skins (enemyskinforcing is illegal)"
hm, so i can't use this that i got from fuhquake page?
enemycolor 13 13
I can barely see enemy models as it is :)
#292009-02-01 15:09 by Åke Vader (90.231.222.XXX)
Reply to Slajer:
"Enemyskinforcing" doesn't mean that it's illegal to force
skins on the opposing team, as long as they all use the same
What is illegal though is the new feature in ezQuake (which
is also available in the much older Qizmo software) which
makes it possible to separate the individuals in the enemy
team, so you would know exactly who you are shooting (for
example by having all their bodies bright white, but their
heads in different colours)
#302009-02-02 12:59 by JohnNy_cz (78.128.193.XXX)
Huh, seriously, what's all that "ezQuake doesn't work for
me"? I'm not saying our software is perfect, but why haven't
you contacted us for help? We can't fix problems we don't
#312009-02-02 14:56 by B1aze (93.80.237.XXX)
ezquake with sys_highpriority 0 don't work correctly. After
few mins of playing mouse freeze and i need to alttab to
windows and back to be able to move mouse again.
With sys_highpriority 1 or -1 all work great.
But with priority -1 i got lags in picture and with priority
1 ts/vent don't work in right way.
No problem with fuh or mqwcl.
#322009-02-02 17:59 by djevulsk (85.24.188.XXX)
Johnny_cz, just a theory here but it MIGHT be because there
were alternative(s) to ezQuake up until now. i don't report
to microsoft that ms explorer crashes all the time for me, I
simply use firefox instead. you follow?
#332009-02-02 20:37 by ezux (207.58.187.XXX)
ezquake didnt bringed any new players , u r getting not your
scene down , u divide people , colored text and co.
. play ur monopoly ... fkn arrogant ...
all legends quit becose of ppl who dont know when to stop
WE ALL KNOW EZQUAKE IS A BETA . I MEAN ALFA on STEROIDs .
real qw community dont need ezquake and buggy ktx. EZ advert
- "only good client on the planet erth , colored and fancy .
compatibile with blue screen , skill no needed , perfect for
stupid noobs 100% garantee or u quit qw"
#342009-02-03 00:56 by Stev (213.94.232.XXX)
That post is one of the most disgustingly wilful displays of
both astounding ignorance and unquestionably misplaced
arrogance that I have ever seen on a quake site.
I'm fairly certain my accusation of ignorance can be backed
up by anyone who actually ever used ezquake or ktx, or
anyone who managed to make it through the drivel you just
spewed into the comment box through your fake US proxy
(which, by the way, shows how confident you yourself are in
Your arrogance is plain in your ridiculous claim that you
can somehow speak for "all legends", or even more than a
sliver of a percent of all the people that have played and
made this game great in its long life. I've never met anyone
who has shown such impossible stupidity about these
subjects, so I'd be slightly surprised if there was anyone
that shared this view perhaps aside from some small cabal of
idiotic lackeys that you surround yourself with ... or
perhaps you are the lackey yourself. That would explain your
half-formed thoughts and incomprehensible rambling on a
subject in which you obviously can't grasp even the most
basic of concepts.
#352009-02-03 01:07 by Stev (213.94.232.XXX)
In the interest of contributing instead of just ranting at
that moron up there ...
B1aze, have you tried adjusting the sys_yieldcpu value in
conjunction with the priority? It might reduce the strain on
mm3 clients, or maybe make highpriority 0 playable.
Something else you could try is an alternative mouse input
like "in_mouse 3" which might not have the same freezing
problem on normal priority.
#362009-02-03 11:12 by B1aze (93.80.237.XXX)
I tryed sys_yieldcpu. And its don't help.
I'll try in_mouse 3, but played with directinput for years.
#372009-02-03 17:27 by 1tsinen (85.156.193.XXX)
B1aze: the feeling of in_mouse 2 (direct) compared to the
new ezquake versions in_mouse 3 (raw) is somewhat the same.
The in_mouse 2 got somehow abit buggy for some players
somewhere between ezq 1.8x and 1.9x. So shouldn't be a
problem there with inm3
#382009-02-03 17:56 by gore (78.105.163.XXX)
Don't feed the troll Stev :p
#392009-02-05 13:14 by Otto (130.231.63.XXX)
Allow teamoverlay for lower divisions and disable weapon
scripts ("bind mouse1 +attack" ftw)!
#402009-02-05 18:30 by 1tsinen (85.156.193.XXX)
#39, if allowing teamoverlay to lower divisions it would
mean atm that there would be either 1 or 2 divs who wouldn't
use it. There is no specific rookie division this year and
we are talking about 3-4 divs instead of 5-6, so it would
allow half the scene to use it which I personally believe
would be disliked.
#412009-02-08 16:37 by peppe (81.231.117.XXX)
afaik ezquake is NOT impossible on your machines, somas case
was extraordinary from talking on irc, but pleura and hagge
I\'m sure you\'ll be able to get it running some way, I
myself was very much against switching to ezquake because it
wouldn\'t run perfectly, but with loads of work it did. I\'m
sure if you want to play in EQL you\'ll take the time and
make it work somehow, otherwise you can\'t say that EQL has
excluded you, but you\'ve chosen to ignore the future of
#422009-02-08 16:38 by peppe (81.231.117.XXX)
on that other note about "legends" quit b/c of new clients,
jesus forget the past! they're not around anymore! we have
new top players! great ones that have a promising future for
bringin us "the big games"
#432009-02-08 18:17 by Kalma (88.115.44.XXX)
Well said mr. Peppe.
#442009-02-09 15:10 by antne (81.200.160.XXX)
Can I play?
#452009-02-10 10:36 by 1tsinen (85.156.193.XXX)
As information, signups will close the 13th!
#462009-02-10 15:08 by samek (212.160.235.XXX)
I hope it won't be another idle season...
#472009-02-10 16:02 by 1tsinen (85.156.193.XXX)
Afaik there's more activity on the qwscene now than there
has been the last 2 years. And with bigger divisions than
before you could say that it should be quite insured that
there will be more activity.
#482009-02-10 18:44 by samek (83.17.191.XXX)
I hope so...
#492009-02-11 13:30 by Jimo (213.50.73.XXX)
Allow teamoverlay for every division.
If someone don't want it, just add /scr_teaminfo 0 in your
Teamoverlay is default on 90% of the servers where we are
So why don't just allow it in eql?
When I started to play qw, it was default.
And it is very much players that have started to play after
me, and we are used to use teamoverlay.
I don't understand what the problem is?
And don't say it is some kind of "cheating" when both Q3 and
QL use it instead of oldschoolteamsays.
#502009-02-11 14:27 by 1tsinen (85.156.193.XXX)
In that case also autotook messages and timers etc should be
allowed. So it's not as easy as that. Using team messages is
also a skill, reporting automatically is not. Same with
movementscripts etc, they all are a way of making everything
automatic so you don't soon anymore even need to play, you
have a bot instead ;)
Showing Page 1 of 2 A total of 61 comments Previous Next Page: 1, 2
Note On this site we log the IP of all users who post comments on matches/articles.