Current JoeBOT Version : 1.6.5.1

[@$3.1415rin]

For all those who havnt seen it yet :

March 16th, 2004
JoeBOT 1.6.5.1 has been released. Most of the work done is this time by cruft, so thanks to him.You can download the current version 1.6.5.1 for windows and linux, for the "traditional" installation and metamod, via the download page.

JoeBOT 1.6.5.1
- Metamod plugin dll released
- CS 1.6 compatible (shield use not implemented yet)
- CS 1.5 backward compatible (set cvar jb_cstrike 1)
- Added jb_* cvars to control all global settings
- Added joebot.cfg cvar config file as alternative to bot.cfg
- fixed : joebot server command no longer needs '|' delimiter
- fixed : bots don't jump during freezetime
- fixed : crash with waypoint unreachable unsigned int range
- fixed : camping bug related to round start/end initialization

/@$3.1415rin

Great. I testet it immediately at 1.5 and it works well.

In my opinion, Joebot became more single-minded.
Did you managed it now?
Was it that problem:
"fixed : camping bug related to round start/end initialization" ???

[@$3.1415rin]

that was some error due to differences between messages in cs 1.5 and cs1.6

[Minh-Lo-Hwang]

nice job peeps



minh

Are there differents in the old waypoint-files and the news ???
And why are the bot.cfg and joebot.cfg files so "untidy" ???

Originally Posted by Evil of Devil

Are there differents in the old waypoint-files and the news ???
And why are the bot.cfg and joebot.cfg files so "untidy" ???

Some waypoint files for CS 1.5 won't work in CS 1.6. The de_aztec waypoint file had to be updated in this version. I also noticed that some of the waypoints in this version are slighty off due to updates on some maps. They're not totally unusable but could use some minor adjustments/edits.

As for the "untidy" comment, how tidy do you want it? Seriously, are you just looking for a more complete bot.cfg/joebot.cfg file to know all the options? The existing .cfg files are just examples of a few settings but I wouldn't consider them messy.

[MusicMan]

I think joebot is great, but I would like some updated waypoints, because the bots liked jumping alot even when there was no reason for them to jump on dust and maybe others.

MusicMan

I've just installed JoeBOT 1.6.5.1 on my HLDS 1.0.0.5 (CS1.5). When I connect to the server and add some bots, they are moving *inhumanly* fast. What can be the problem with that?

I read something about setting the cvar jb_cstrike 1. I put in the "joebot.cfg". Was that correct? But I think my "bot.cfg" is currently in use.

Please help!

Chris

[Whistler]

Hmmm....I've just taken a look at the code.....

I've found the code is quite different from the C/C++ I recognized Maybe it's too l33t for beginners like me to read.

So my suggestion is: do NOT use those names of variables like this...
pWPAMPlay, STMem.f_NUpdate, FFE...and so on,

Also don't write strange code like this....

 		// process log of weapon with which the bot has been killed
 		for(ischl = 0;ischl < _MAXLKW;ischl++){
 			if(FLKW[ischl] != -1){
 				if(IsSniperWeapon(1<<FLKW[ischl])){
 					lKSniper ++;
 				}
 				if(IsShotgunWeapon(1<<FLKW[ischl])){
 					lKShot ++;
 				}
 				if(IsSubMWeapon(1<<FLKW[ischl])){
 					lKSub ++;
 				}
 			}
 		}
 		
 		lKSniper>lKSub&&lKSniper>lKShot?
 			bKSniper=true:lKSub>lKSniper&&lKSub>lKShot?
 		        bKSub=true:lKShot>lKSniper&&lKShot>lKSub?
 					bKShot=true:0==0;

[@$3.1415rin]

I know that the variable names in old joebot are not consistent and not all according to hungarian notiation which I use normally now. LKW is LastKilledWeapon, WPAMPlay is Waypoint advanced movement play, STMem is short term memory, NUpdate is next update ... but just look into the header, there should be a comment, but there are also too less comments in general, I know gonna be better with my current bot ...

and I only used this crazy multiple ? construct once ... just for fun but it's still readable, isnt it ?