Pardon me bad english, gain...
>> I don't understand why you have problems... if you can jump just
>> right, you should be able to make a jump connection as well.
>> Can you explain what you mean a little bit more in detail? I'm
>> not sure if I got your point...
Erm... Dunno haw tah explain eet...
As was told, try cs_siege with SoulFather's wp-pack.
Look at how CT bots try to jump on building. Try to fix it youreself.
Or maybe its just low-fps prob...
Manual jump connection would just ease wp editing in some situations.
Nozing more.
>> Hm, that's actually 2 ideas in one...
Nope, its one idea. The designated Idea-B part
is more like explanation
of why that new check is needed. I agree that eight connections are
enough (most of the time). But sometimes...
>> Do you really think it's that bad? Thanks to the new markers, I'm
>> getting along with this aiming system quite well, although I agree
>> with you that it's not perfect.
No, not that bad... But trying to aim to point that is somewhere in
32 (world units) rad off the center of waypoint, again sometimes, IS
PAIN IN ZEE ASS. Just sometimes.
>> Errrr.... come again? I really don't quite get what you mean...
>> Do you want to store info like "AK has been very efficient around
>> WP nr. xxx" in a separate exp file?
Coming again...
No, there is no need to store it for every wp. The idea is (as is):
Example of statistics:
Statistics for cs_office
bot carrying AK47 killed 43 times, died 24 times
bot carrying AWP killed 9 times, died 67 times
...
Its easy to collect/enterpret such stats, dont u think?
(simple && effective) = Simply effective
So there is finally no bot's with AWP's on cs_office!
And no, no separate exp file. There is already one exists. Why not to
store all EXPerience data in it? Isnt this is what it was created for?
This could worth even three thoughts!
>>>> 5) Adding overall visibility coefitient of waypoint to its properties
>> I'm not sure if it would be possible to do that without giving
>> up compatibility to PB 2.5 waypoints... then again, it could be
>> discussed whether this compatibility has to be kept at all costs,
>> but that's quite a big issue.
There is no "compatibility issue", period
There was NO vis calculation in 2.5.
There was NO *.vis files in 2.5.
It all began in 2.6.
And vis-files in 2.6mm.
Even if there was one, bot IS evolving.
Always wanted to ask SpLoRyGoN about his goals.
Path nr.1: continuation of original source ideology, pushing it to the limit.
Path nr.2: making it CS_Bot_of_my_dream (whatever it takes).
What's his?
Sorry for offtopic...
Simple (simply effective, remember?)
Again, idea (as is):
float temp_overall_vis_coeffitient[NUMBER_OF_WAYPOINTS];
for every wp(1)
{
int overall_vis_coeffitient = 0;
for every wp(2)
{
if (there_is_trace(wp(1), wp(2))) overall_vis_coeffitient += 1;
}
temp_overall_vis_coeffitient[wp(1)] = overall_vis_coeffitient;
}
This all can even be stored in float (0..1) for simplicity's sake
(0 - complitely invisible to any other wp, 1 - maximal visibility to other
wp's):
for every wp
{
wp.overall_vis_coeffitient = temp_overall_vis_coeffitient[wp]
/MAX_VIS_COEFF_OF_THEM_ALL;
}
This coeff can be used in A* or any other proc aswell.
Btw: why not to make generic A* dll or static lib (optimized ofcourse w'MMX
n stuff).
Btw2: i could do it... probably (full day work'n stuff, aint got much time,
but still got some and wanting to use it to recall my prog skills).
Btw3: watz wiz CVS. Couldn't connect to it. Some error wiz localhost or
something...
Btw4: (guess what) there is vis-file
...
>>>> 6) Is there any sniper specific code? Like using camp spots with longer
>>>> tracers fired from binding angles (uh, pardon my english).
>> ???
It depends on effective sniper_camp distance (say 1024 world units).
When u create camp spot u make it by creating first direction and
after that - the second. Now fire tracers from them and remember distances.
Then add them together and divide by 2. This is the distances to choose
from to sniper. The longer, the better. Think - if u bought AWP - u're priority
one would be to camp at spot with bigger depth of FOV. Hell, u're sniper,
so snipe on BIG distaces, right? Yes, this explanation is primitive. Cant think
of anything better now... sorry...
//================================================== =====================
As i told, its all more cosmetic thingys than something realy important.
The ideas already implemented are great and work most of the time.
MOST OF THE TIME.
I dont know about you, but i got that feeling that most of them are kind of
unfinished. We got wp highlighting, but u still have to search for that spot.
We got experience collecting system, but how many thousand times bots have
to die to understand that it is BAD to jump on that wp - guns akimbo.
Bots can buy sniper weapons, but can't properly use them (and most important,
how to camp wiz zem right). Bots can buy shields, but cant use them right...
And this list can go on and on...
Right now (guess what) i'm too drunk to continue... no beer pleaze...
Slipknot - rulez...