what lines aren't working ?

none of its not working. The game is just playing as if in default settings with my binds. i then put exec autoexec.cfg in consol then everything stops working, cant even shoot

your autoexec should be in the same directory as your repconfig and qlconfig, as in: .../quakelive/home/baseq3/ not to be confused with .../quakelive/baseq3/ where the map files reside.

try renaming your autoexec.cfg to andras.cfg and create a new autoexec.cfg, which just has "exec andras.cfg" (without the quotes) in it. At first glance i see nothing in your cfg that should prevent it from loading, although i fail to understand your forceenemymodel settings :)

"forceenemymodel" does not exist, almost all variables in quake have a prefix like cg_ cl_ r_ s_ signalling what they belong to.

from what i know forcing an enemymodel should resemble something along the lines of

cg_forcemodel "1"
model "mynx/blue"
cg_forceteammodel "ranger/blue"
cg_forceteamskin "sport_blue"
cg_forceenemymodel "keel/bright"
cg_enemyUpperColor "0x00FF00FF"
cg_enemyLowerColor "0x00FF00FF"
cg_enemyHeadColor "0x00FF00FF"
cg_teamUpperColor "0xFFFFFFFF"
cg_teamLowerColor "0xFFFFFFFF"
cg_teamHeadColor "0xFFFFFFFF"
cg_weaponColor_grenade "0x00FFFFFF"

in your config. the above is an example of course, your settings will be different from mine.

and this

bind l "nice"
bind k ":)"

should read

bind l "say nice"
bind k "say :)"

indicating that you are not binding whatever "nice" is to the l key, but having a bind instead which makes you say "nice" in the chat.

taking a second look...

if you truly are a beginner you should not use cg_fov 120, but stick to the default 100 or something inbetween of 90 and 105. otherwise you will have a far harder time learning how to aim and judge distances.

you also have no business using a zoom/sens script on +attack for lg, learn how to play first instead of relying on stuff like that.
your weapon config is far too complicated too, anything but a crosshair and chsize change you really shouldn't use.

stick to one setting for cg_fov, sensitivity and cl_mouseaccel for every weapon and just play for 4-8 weeks. don't do anything stupid (as in: anything out of the ordinary) with these settings either. play.

ps.: if you set m_cpi to the dpi of your mouse, i or others could probably judge your sens and accel settings, if you want.

This (and the following lines):

seta w1 "weapon 1"vstr zFire_LG "cg_gunX -5"cg_gunY 0"cg_gunZ 8" cg_drawcrosshair 13"cg_crosshairSize 25"cg_crosshairColor 26"sensitivity 2.5"cg_fov 120"

should be something like

seta w1 "weapon 1;vstr zFire_LG ;cg_gunX -5;cg_gunY 0;cg_gunZ 8; cg_drawcrosshair 13;cg_crosshairSize 25;cg_crosshairColor 26;sensitivity 2.5;cg_fov 120"

Line 49 also has the same problem.

On line 66, you have an extra trailing 0 that shouldn't be there.

delete unaliasall

r_picmip 6 is so ugly, I'd go with picmip 0 or 16, but perhaps that's personal taste. I'm also using FOV 105 because anything higher distorts the view and makes it harder judge situations, the plus side is that you can see more on the sides, but it can make people nauseous after a while.

I also see typos like "ensitivity" in, besides what ProT already pointed out.


//rl//
seta w6 "weapon 6"vstr zFire_LG "cg_gunX -4"cg_gunY 0"cg_gunZ 8"cg_drawcrosshair 13"cg_crosshairSize 25"cg_crosshairColor 26"ensitivity 2.5"cg_fov 120"//lg//

m_cpi could help to compare settings easier as suggested by zealot.

Here is some advice: delete all custom configs, do a settings reset on the website, and then use only the GUI or the QL console to change settings. Don't ever edit/add cfgs manually, except maybe for the QLRanks ELO announcer. It works surprisingly well, you will see.

Instead of focusing on such useless details as weapon/sensitivity scripts, work towards improving broader skills such as movement, positioning, game awareness, decision making and so on.

this i have done. thanks