Suggestions

I have made a suggestions thread for the obvious reasons.


This is my suggestion:

Make the WIP version load the rbw files and add to them, instead of having to redo every map. I have a lot of maps, and I have waypoints for pratically all of them. I don't want to have to redo them.:'(

Edit---

Also, they should be able to 'use' things as well, like cars, doors(the ones u have to press 'e' on) and big guns

Another edit--

If bots see guns better than the ones they are already using, they should pick them up. They should determine what is better by their personaility e.g. one might the colt and FA-MAS better, while another might like SMG's better, while another might like automatic sniper rifles better. It should also take into account the price of ammo(though I don't think anybody actually does this), how fast it fires, muzzle velocity, and of course muzzle energy.

They should also be more team oriented, e.g. in a group of 11, they might have a 3 man fire support group with rifles, 1 Para SAW, 2 snipers, 3 'runners', who go after the hostages in a hostage rescue map, and 2 shielders to protect the runners. Of course, things would be different in a de_ map. The shielders will protect the runners while they are defusing the bomb, and in a VIP map, they would protect the VIP. Here is a diagram of a VIP configuration:

* Ru Ru Ru
*
* P
* /-- --\
* Sn |Sh V Sh| Sn
*
* Fs Fs
* Fs

Where:
Ru = runner
P = Para SAW
V = VIP
Sh = shielder
Fs = fire support
Sn = sniper


For a de map:



Ru Fs Ru

P
/-- --\
Sn |Sh X Sh| Sn
Fs Ru Fs


Where:
Same as above, except X= Bomb.

Yes I agree with Pon although you can always copy the nodes folder and stash it before adding a WIP then replace the current folder would that work?

no cus it uses a completely new sys

awww the diagrams are screwed up

I just had a bad idea: make rb available thru steam

Edit--

Actually i was just looking thru thr steam sdk docs and it might not be such a bad idea.

more specifically:

Creating an application that runs effectively under Steam is basically a two-phase process. The first phase involves integrating Steam into your application and getting it set up for remote file distribution. There are a number of steps in this phase but once it is completed, it becomes simple to use. Steam provides tools to help you along the way.

The second phase involves optimizing the Steam resource acquisition mechanism. Part of Steam runs as a background thread loading file resources, during periods when your application is not utilizing Internet bandwidth. Since your application may stall if it requests data that has not been downloaded yet, you need to tell Steam what resources it should be working on in the background. Like all optimization processes, this requires a certain amount of experimentation and time. Fortunately, Steam provides a set of tools to make this easier.

If your application is also going to be released on a retail CD, there is no need to maintain two separate code bases. Everything that you do to support Steam will work with your retail version. A simple change to the Steam Engine initialization (skipping the call to SteamMountAppFilesystem) will have the desired result.

Any how, i dont think u can , because how will u get it to update when rb is in another app folder... sorry for wasting space :o

Ok, this is another idea: make the bots check the edges of maps, eg if they are walking along a plank of wood, make them check to see where it is safe to walk

anyone feel free to add things here, these are just some things i think it would be cool for rb to have, so lets hear yours

Perhaps more goal orientation... the teamwork and extras can come afterwards...

yeah

Just a thought here- Is it possible for RB to always run and make nodes, even while playing on a pub? Would mm intercept player moevements, or would that get you banned by VAC?