to biohazerd87:
I understand that many things depends on how waypoints done. I understand
that jump-auto-wp-placement works actually as a failsafe - if human could
jump there then bot will be able to do that. But i disagree that all MUST
depend on it. IMHO main goal of waypointer is to "show" where to
go, where to camp and where to jump, but bot must make descisions depending on
situation on when and how to do that. Realistic behaviour must be in code
not in waypoints. Why not to make "hard to reach" flag to signal bot
that this certain wp can be reached only by high level bots. WP edit must
easy and fast. Yes, noobs with this manual jump connection would be
a "clinic case"
. But to expirienced waypointer it will be just another
instrument.
>> Actually this is incredobly hard this would pretty much require a
>> whole rewrite of the code
There is no need in rewriting a whole code. Init/load data on map start.
Update it in every next round. Save on map change/disconnect. Not THAT
easy
but still...
to SpLoRyGoN:
>> the visibility table has existed in CF's version of pb, I dunno when
>> it started but it did exist in 2.5. it's just that in pb2.5 it didn't
>> save the visibility table and would rebuild it every map start...
It all (vis calc) started in that 2.6 "hdd crash" version. In 2.5 there was
no vis calc. Im tellin' ya
.
>> Are you saying open source programs aren't good???
No, i'm not about open source. I like open source ideology. I just wanted to
know, will u implement something new to bot or just finish what was started
by Count Floyd.
>> Zero would never exist.. if it did then theres a bad waypointer afoot!
It doesnt matter. This koef is just a relative measure of how visible this
wp to others. Yeah, i'd wanted to see how that "waypointer" would do that
.
P.S. Anyone can help me with CVS?