yes.


also rj scripts are shit

shit as in they don't work well or shit as in they are lame?

you have no control over your height and it's easy enough to do a max RJ if you use mouse2 for jump. it's a waste of a bind unless you have trouble doing them consistently.

rj scripts are for effortless, consistent maximum height rjs. anyone can do small rjs.

It's starting to happen too often that I fail top balcony YA rocket jump on ztn. I don't use any scripts at all but starting to think more to get one lately. But it's weird, so incosistent.. I think earlier I was able to do 9/10 and now it's like 5/10.

you reversed the evolution, I smell god here

they are not consistent, btw. they are obviously bound to network latency and fps, if i'm not mistaken. see lorfa's and draxus' posts on ninjascript, they need exact valus for different fps.

should just be framerate that matters, nothing else, in which case they are consistent.

try a rjscript with ping 80, then try again on lan (or with a sub 10 ping). you will notice a difference ;)

They're also older than Quake3 is.

Thou shalt not bind +attack and +moveup....

.

Big Bada Boom

lilu

allowed and included with your purchase of a ninox aurora

i used one like, seriously when i was a little kid. and yes they kinda suck. if you're good you can perform tricky rj's like @ bawss.

i thought yaw and pitch speed were locked?

I also thought they did something to prevent rocket jump scripts like this, but I haven't tested it at all. I would like to see the script.

This. I don't believe "it snaps your aim to the floor, jumps, fires, then snaps your aim back up to center"

Well here's the script:

seta _rocketJump "cl_anglespeedkey 50000;+speed;+lookdown;wait;wait;+moveup;+attack;wait;wait;-lookdown;+lookup;wait;wait;-attack;-moveup;-speed;-lookup;cl_anglespeedkey 1.5"

just bind a key to "vstr _rocketJump" and try it out :)

EDIT: Updated the script, got rid of a few waits, should work better now :)

anglespeedkey! brilliant.

Don't know how that was overlooked. Good find!

Will probably be locked down though in next update or w/e.

Until then, have at it hoss!

thanks Lorfa :)

Your CVAR guide was invaluable while working on my config!

Here's my current config if you have a few minutes let me know what you think of it :) http://www.willamp.com/quake/draxconfig.zip

You don't need these:

bind ` "toggleconsole"
bind ~ "toggleconsole"

As it is hard coded.

bot_thinkTime "0" won't work in a config. It will have to be inputted each time you enter a practice game. I asked this to be changed 999 times, but so far no such luck.

I don't recommend sv_fps 125, because it will give you an unrealistic amount of responsiveness on localhost. It's already kind of removed from the online experience due to the lack of latency, but this is ridiculous.

I've never personally understood how players manage to jump with their pinky, but there have been a few decent ones throughout history. In this particular case it is even worse since the pinky key pulling the movement key fingers out of place.

I would think that if you were going with a numpad movement key setup that you'd be inclined to jump on the mouse.

It's rather nonsensical to use m_cpi with an m_yaw other than 0.022 because then sens will mean some especially random value.

accelstyle doesn't exist.

senscap is meaningless when accel is 0.

Offset defaults to 0 in case you were wanting to leave this at default. (also has no effect with accel 0)

There are defaults throughout the config, and some ineffectual/irrelevant cvars but probably not something you're concerned about.

I recommend stencilbits 0, as it can cause a problem on some vid cards, and there is nothing to stencil in QL.

I cannot think of any reason to use s_doppler.

Setting s_mixPreStep to 0 seems crazy. Wouldn't that disable the sound system? Also mixahead 0.04 seems too low not to cause static/repeating or other issues.

"hitbeep" is not a cvar. The cvar is "cg_hitbeep"

snaps doesn't exist in QL (of course any cvar you set or seta will show up, but will be ineffectual)

smoothClients is ineffectual in QL.

I'm pretty sure autoProjectileNudge is unavailable. Projectilenudge itself may be ineffectual, but I keep up the placebo myself.

con_height 0.4666 lol

cg_newWeaponbar doesn't exist anymore.

allowConsole defaults to 1.

compHud may be unnecessary now (not 100 % sure, too lazy to test). I remember sync saying something about not requiring it.

drawTargetnames might not exist or is ineffectual.

drawSpriteself may be ineffectual.

I recommend screenDamage 0.

noProjectileTrail doesn't exist.

I recommend trueShotgun 1, but it's a fairly minor issue.

If lightningImpact is 0, no need to bother with lightningImpactCap.

These are some unusual cg_gun numbers. I don't think any value can really be "bad", just odd.

Not sure why you'd go to the trouble of having different crosshairs (and different colors!) when shooting vs. not (on top of having unique crosshairs for weapons). Seems like a lot of scripting for questionable gain.

why would there be no reason to use s_doppler "1"? i've been using it for a long time, so now i'm gonna go try setting it to 0, but i'd be interested to hear why you think there's no reason to use it.

All doppler 1 does is make a scratching sound when a rocket goes past your face. By the time the sound plays the rocket is too close for you to do anything about it. This isn't useful, it's just extra noise, noise that could contribute to drowning out an important game sound.

The only circumstance I can think of where it would provide information that you wouldn't otherwise have is if you were facing say 'north', and a rocket comes from far away such that you can't hear the shot from the southeast or southwest at an angle that crosses near your face yet still manages to explode somewhere out of view.

Then you could tell if the rocket originated from the southeast or southwest based on whether you heard the scratching in your left or right audio channel.

This is a really bizarre scenario though, because you'd pretty much have to be not looking around you the way newb's sometimes don't, and other information that decent players use to determine where a threat might originate would also have to be unavailable.

One of the best moments in DeFRaG is when you get in your own rockets and hearing that WHOOOOSSHH.

Turn it on when doing defrag then =)

Thanks a ton for the input!

My m_yaw and m_pitch came from copying tox's cfg. Do you think there is any negative effect of using lower than .022 like pixel skipping or anything like that?

I'm left handed so my right hand is on the numpad. I jump with my thumb :)

s_mixPreStep 0 and s_mixahead 0.04 works fine on my system and is the lowest values I can get without issues. The point is to get the lowest sound latency possible right? I might have to do some more testing with these...

con_height 0.4666 is just so that I can see my crosshair when the console is down :)

The crosshair stuff I know is goofy but I like having more visual feedback. :)

What else would be cool to change on a per weapon basis or on +attack? I know some people use different sens and fov for each gun...

Anyway thanks again for the input!

My m_yaw and m_pitch came from copying tox's cfg. Do you think there is any negative effect of using lower than .022 like pixel skipping or anything like that?

No, and I don't think 'pixel skipping' is really a serious issue either.

It's not a problem using yaw different than 0.022 and m_cpi, just makes your numbers an ugly mess that can't be understood at a glance.

I'm left handed so my right hand is on the numpad. I jump with my thumb :)

Ahh.

s_mixPreStep 0 and s_mixahead 0.04 works fine on my system

That is really, really strange. Long as it works though.

The point is to get the lowest sound latency possible right? I might have to do some more testing with these...

I took them out of my guide because I could find no evidence that they reduce sound latency.

I keep the 'placebo torch' lit though using mixahead 0.07 and prestep 0.04.

What else would be cool to change on a per weapon basis or on +attack? I know some people use different sens and fov for each gun...

Donno. The only things I have are different hitbeeps (hitbeep 1 for everything but explosives/sg for a more consistent sound), and gunY 2.7 (lg center) for all weapons except rail, where I have 5.1 to center the beam.

My settings have the gun hidden though so it would be different for you.

lg center is more like 2.75.

2.7 is probably already more than accurate enough given the size of the beam.

I'm curious though, are you using a high resolution? Do you have a couple good comparison screenshots between say 2.7 and 2.75 that could confirm this?

I'm just curious as to how far the precision on that number can be taken, even though at my low resolutions I probably won't be able to see any difference.

640 x 480 for lyfe.

..and you're seeing some difference between 2.7 and 2.75 gunY on the LG?

0.05

FYI "+moveup; +attack" instead of "+moveup;wait;wait;+attack;" will give you greater height

You're right. Just did some testing and noticed with the original script I couldn't get full height RJs if I was aiming upwards at all, but I fixed it and got rid of some of the waits! Here's the current script, let me know if you think it can be improved further... I got it down to 6 total waits:

seta _rocketJump "cl_anglespeedkey 50000;+speed;+lookdown;wait;wait;+moveup;+attack;wait;wait;-lookdown;+lookup;wait;wait;-attack;-moveup;-speed;-lookup;cl_anglespeedkey 1.5"

Instead of doing: "wait ; wait ; something"

You can do: "wait 2 ; something"

You don't have to return anglespeedkey to 1.5. Unless you play with the keyboard it won't have any effect on anything else.

Imo centerview is preferable to lookup and shouldn't affect the height.

Can also be done this way:

bind KEY "cl_yawspeed 22500;cl_pitchspeed 999999;+back;+moveup;+attack;+left;wait 10;-left;-attack;-moveup;-back;+right;wait 10;-right"

Not in QL, yawspeed and pitchspeed are locked.

a maximum limit was put on cl_pitchspeeed, afaik. i just checked anglespeedkey and it still works (as in #11)

keep the fire and jump, just remove the floor aiming function, then work on your mouse aim and your all set : )

i always tried to shoot people behind me with the ninjascript in q3. really though you dont need help to rj, just l2play :>

Yeah I used to try that too, was pretty fun. I take it that script doesn't work in QL?

yea, they locked pitch and yawspeed.

i want a script for turning 180°, but i guess that's not possible anymore due to cl_pitch/yawspeed restrictions. :(

It might be possible with anglespeedkey! Until that is locked down too of course..

If you get 250 fps try this:

cl_anglespeedkey "321.45"
set 180 "+right ; +speed ; wait 2 ; -right ; -speed"
bind rightarrow "vstr 180"

That's really close to exactly 180. I should just look up the source code and calculate what the value should be but w/e.

You need a completely different value for something other than 250 fps, like for 125 fps I think just exactly half so try 160.725.

great, seems to work even pixelperfect. \:D/
my shoulder says thank you.

Much easier to just flick a 180°.

dont get me wrong, id never use a ninja script, but how can doing something be easier than not doing it?

I mean pressing 1 button instead of pressing 2 buttons and turning 180 degrees

But why would you want such a script?

If you can't do a 180 flick reliably, something is very wrong with your setup. Not only that, you may not only need to turn around, but also start looking down/up which will take longer if you press a button first and only then start aiming.

In short, this is a bad thing in the long run.

i was talking about 180 turn plus rj, not just 180 turn. I got the impression he needed the 180 turn script to combine it with rj script. I might be wrong tho

nope, just for turning with my quite low sens atm.

i would only want it for convenience.
but it might actually have some real benefits in some situations, when you can keep the mouse centered on your mousepad.

I don't press any button. Just moving the mouse.

check above ^

Then I press a button too.

This and the rjscript are both cheats in my book tbh:/
I know that nobody cares or asked for my opinion, just my two cents.

Don't know why a 180 alias would be a cheat, but doesn't matter anyways because it's very likely anglespeedkey will be locked in the near future.

Unless you think the script that shoots and jumps at the same time for you but doesn't look down is a cheat. I don't know what to tell you there. Really a stretch to call that a cheat.

There is that : "use and communicate exploits to gain unfair advantage in a game" line, and doing a perfect rj or a 180 turn without the risk of failing or without the need of the effort to do it yourself is (imho) an "unfair advantage" against players who are doing it (or can't do it) legit.

Well, it 's a "stretch" indeed, maybe I'm just too old fashioned when it comes to "cheats".

It's just different way of doing things.
You won't win againts someone just because you use rj script or you 180 noscoped them faggots.
Using scripts in game that allows you using scripts is so wrong m8.

and also, if you can write it in a config, and anyone else in the game could do the same, it doesn't give an unfair advantage - everyone else could have that advantage if they chose to as well. or is it an exploit to buy a nice mouse/pad? BASICALLY AIMS FOR YOU.

and yes, i'd say that kapca is pretty darn old fashioned when it comes to "cheats"

everyone has the ability to download wh/aimbot. doesnt make them legit

the 90s are calling, they want their arguments back. there is quite a difference between a external program aiming for you and editing a config file.

i fail to see how ardor failed to see that argument going into this :/

I do believe that tweaking your config is awesome, and I also loved to tweak it for endless nights over and over again..... Quake would be less without the config tweaks happened in its lifetime, much less imo.

...... however.

Time definitely won't make an argument invalid. I still believe that doing pixel perfect 180s, max height RJs, timers etc, so all the "roboty" things possible with scripts are indeed unfair advantages, and I did not yet see any valid arguments to believe otherwise.

Sorry if I'm stupid and can't understand your point.

...
- there are no pixel perfect max height jump scripts in quakelive, unless you are one of the selected few to play it on lan. depending on how bad the latency is, i wouldn't trust a script over my eyes and fingers ;)

- i liked ninjascript. q3/ql's movement is slow, sluggish and boring and that was one awesome (and still punishing) way to speed things up.

in the end, i wasn't serious only annoyed by his post :d

i just think that everything you can change should be available in the menu. all the scripting shit just makes quake even more inaccessible for new ppl.

They don't even know that console and cofig files exist, so it's pretty much irrelevant for them.

.

Use a joypad lol
Yuo shouldnt use a 180 script, the only reason is a very very low sens (>50cm no accel)

so i guess ninja scripts are gonna be a thing a gain thanks to you :D

What exactly is a ninja script? Like RJ off a wall and instantly 180? Also I hope I haven't pissed anyone off with the script :X

A script that turns 180 degrees, jumps and fires, then turns 180 degrees again. I recall that it was popularised by Venture in Quakeworld. I remember seeing it for the first time in this demo
http://www.challenge-tv.com/index_old.php?mod...demo=15866

Just after 50 seconds in with the slowdown shows you exactly what it does.

"he isnt using it lol ... this 360 thing i can do it also with a high sens..."

Rj script where you have to look down yourself ( so u can do it to the left or right or down at an angle ) and it brings back the cross to the center.

//Rocketjump

set autoRJ "+moveup ; +attack ; wait 10 ; centerview ; -attack ; -moveup" // -> auto-lookup

bind pgup "bind alt vstr autoRJ ; echo ^7AutoRJ"


simple, oldschool but very effektive. max height aswell

rasta :)

You shouldn't need 10 waits, and shortening it might provide more height. I think you can do wait 3.

*effective

I used them back in OSP when bad framerates and netcode made me miss the ZTN rj's from ril2gl and rl room ya to stairs.. I don't miss them.

or why don't you just develop your RJ'ing skillz and not be a pussy?

am i mistaken, or doesn't cooller have an RJ script? and did you just call cooller a pussy?

forecast: cloudy with a chance of shitstorms

I don't know about Cooller, but Cypher used one for sure in the ql era.

Evil has or at least had a rj script in his config.

i need one cus ninox aurora...

Tbh, a press of a button shouldn't move your mouse around in a pinpoint fashion. But on the other hand I don't understand how some people are looking down on a script that pretty much just shoots and jumps at the same time while others are using per weapon scripts to change fov/sens/enemymodel etc..