CT's Not DefusiNG the BOMB!

[ilovepodbot]

hey ive noticed that C^T DONT DEFUSE THE BOMB even if they are in the bombsite im using V3B19m always dont defuse bomb if all T's are dead they just look at the Bomb until it ...poof....... explosion or sometimes just running around the site and dont care about the bomb

Help!!!!!!!!!!!!!!

EDIT: BUT IT DEFUSES THE BOMD IF THERE ARE T'S ALIVE!!!!!!!

[KWo]

For the new version I'm going to re-search the code for finding bomb again and I'll take a look why they don't defuse the bomb if all Ts are dead.

[Blakhart]

I see that the ct often didn't buy a defuser and just stand over the bomb like idiots, so mebbe this is the problem? On bomb maps, the first thing they should all buy is a defuser no matter what. How can we make it so?

[KWo]

What is the map it happens like that? I was testing on de_dust2 and they haven't had any problem with defusing (V3B19n) - no matter if they had or haven't the defuser.

[Blakhart]

Last I saw this happening on aztec. They huddle over the bomb and after a few seconds they walk away.

[Sc0Rp]

Did he saw an enemy? How many hp did he have? Was there enough time to defuse? Was the bomb completely visible ( if a bot planted it, there is not much possibility the planted bomb is partially into an object, but I'm only sure of it about the default waypoints of de_aztec )
Do you remember any of these specifics?
Details are very important in bug solving.

[Blakhart]

The bomb was right out in the open, as it was planted by a bot. The ct was covered by other cts and there was no enemy near. He just huddled over the bomb, never making the sound of when you deploy the defuser. He just kinda twisted around on it and then after a few seconds walked away. Plenty of time left to defuse it. None of the other ct bothered with defusing it either. I have seen this often enough. I'd like to see them defuse it no matter if they're under threat or not.

[Sc0Rp]

This is strange, they normally defuse under most circumstances.
But since I can't test podbot anymore, I'm not sure if it really bugs the way you describe it with the latest beta.
Which podbot version do you experience this behaviour?
Do you notice it also on other maps; if yes, name them.