PMB
i put in the new bot.
i wanted to start correcting cs_bikini for the pack.....
i corrected all i saw fit.
then i played it.......
waypoint problem: no path found
so im like......what.....a camp spot i forgot? i walked around and looked at all 20 of them.....i had readjusted them all.
so i began making sure every connection would lead our hostage carrying CT's out of the house......all things are connected as i had released it in the Bikini waypoint pack i made where everything was fine.....and the way it was i had not BLOCKED ALL possible ways to lead the hostages out to the rescue waypoint with a no hostage flag.
still got the message......so i went back in and replaced EVERY single waypoint from any goal waypoint in all its directions leading it to a replaced rescue waypoint too.......so basicly i practically redid the entire map........
still get the message........now something is not right here......it seems to me that a no hostage flag is acting like a button flag.....using proximity things instead of what flagged on a specific waypoint.......cuz i took off one no_hostage flag.....from a ledge that can lead a bot onto the roof(not an area to bring hossies) and suddenly the bot could go past below this waypoint......down the cliff.......unfortunately this bot died.......on the next round i got the damn message again.
what causes this message????? i dont put no_hostage flags along paths they can use man no way no way in hell......im really going nuts!!! hehehe
i didnt even get a chance to see if the camp spots are being used right......but ladders seem fine now
in 1.6 we see the rebuild of the vis table in percentages in a countdown(up) fashion.....not in 1.5 tho......
im finding the red node readout hard to see(am i the only one that has to point in directions to get the red print onto some dark background to be able read it?)
and im finding it a must-happen to have the no_hostage flag visible somehow on a waypoint......it will be easier to debug a waypoint of a cs_map as we go correcting......