honestly i don't really care enough to work on this more then 20 minutes so figure out how to get 2354235253% groundspeed off a single strafe jump if you want.

That isn't bunnyhopping - what you've scripted is called glidejumping. They work on completely different principles.

Which unit goes 270 base? Skulks walk 290, marines 175-220 (depending on weapon and ammo loadout).

Edit : Also linking several of these is pointless, as the whole idea behind using air acceleration is the control it involves - having a first jump, provided you can get the correct turn rate to top out perfectly, however would be useful. How exploitive it is considering the inflexibility, well judge for yourself. *shrug*

Yawspeed 320, 35l and 35y during the jump - 420 groundspeed (which is what I get manually). Problem : It only releases the controls back to you at the end of the jump, making it hard to time. Lets see if I can maybe lower the amount of turning to get 420 a bit.

Edit : Oh, and theres a cap on the first jump anyway afaik. I don't think you can break 420 ground on the first (Sans movedown or elongated jumps via dropping)

Edit 2 : Well, doing it manually I seem to get 460-480 almost the instant I touchdown for the second jump if done correclty, but I'm assuming that reading comes after the first landing.

Edit 3 :
alias jjump "+forward;+duck;2y;25r;5r;2r;+moveleft;2y;25l;5l;-forward;+jump;-forward;y;35l;-moveleft;+moveright;y;35r;-moveright;-jump;-duck"

440. Albeit a bit slow. Roughly the equivalent of the manual jump, just done a bit more slowly. 2y = yawspeed 340.

445 at yawspeed 360 and fps_max 125. Anyway, that was some fun experimenting, thanks (and considering I was too lazy to write up a set of testing aliases as you did myself ). Now I'm off to get some food, maybe I'll try again later this evening - see if 480-500 can be reached in one jump.

hmm ok i did a little bit of work, i figure the problem of control might be solved best if it does a strafe jump plus a jump after that. otherwise, it's very hard to bring into a bunnyhop.

also yawspeed probably is far far too high once it's past 3x or so, i hadn't accounted for it really.

guys...where shall i write my code..??

in the consol....or are there a program to open the scripts in the windows??

plzz if there....do u got a link to download it??

Mutli

Hmm, interesting. If you guys want to get into these kinds of experiments, your best bet is to go into Quake 3.

Quake 3's straf jumps are a little different then the ones on the HL engine, but they follow similar principles... Although the speeds you can attain in Q3A are enormous.


You can reach something like 1000Us easily without any rocketjump aid, if you add in rocket jumps to the equasion your speed just skyrockets and such, but rocketjumps dont involve much strafjumping.


When straf jumping in quake 3, you use no scripts. There are quite a bit of variables to take into consideration. Now as for trickjumping, well the number of variables triples. Quake 3 is the single best game for trickjumping. A Trickjump tourney will be held at QuakeCon 2005. Watch the video in the link for a collection of the best trickjumpers and trickjumps (its a large video, but its worth it)..


The video has a README! Read the readme if you want to be able to play the video! There are HTML files included for downloading Windows Media player Classic which is STRONGLY reccomended if you want the video to play properly.


Good day

bind [key] "towhat?

Waits are 10ms now? I'd like to see some proof of that, I cannot remember valve ever changing how waits work The original Q1 'wait' command was based off cpu cycles, not time. A single wait on person x's computer could differ a lot from person y's computer, which made for some very difficult times back in Q1 scripting, which was passed onto the HL engine, and which then made HL scripting just as hard. If you can, please, proove me wrong (I havent done much scripting for a while), but if you cant, something like this would change drastically from PC to PC. It made testing scripts on multiple computers a **** years ago because it was near impossible to make them exactly the same on two PC's, and sometimes led to heated arguments on the best settings

The duration of the wait command is still one frame. If the game runs at 100fps, one wait effectively lasts 1/100 of a second (10ms).