For an explosive to bounce into the air one would have to simply increase the height of the explosion, can easyily be done.

As the wirecutter also gives a significant bonus on defusing, I'd strongly advise having one ready on your sappers.

tag available, right? Is it wirecutters only that should get that bonus, or any item (in hand) that has that tag, even if it's not a wirecutter?

P.S. get your ass back on irc, people complain that it's too quite without you

// Flugente fix: there is a severe problem with Action items. The problem is that in the above switch statement, we use the default stuff for action items.
// If the action item is a bomb etc. (bActionValue = 3), we want to set the bomb item. But due to EXTREME RETARDEDNESS, the ugYucky-struct differs on variable positions.
// To be precise (see in ItemTypes.h: union OLD_OBJECTTYPE_101_UNION for reference), its
//
// ...
// INT8 bGunStatus; // status % of gun
// UINT8 ubGunAmmoType; // ammo type, as per weapons.h
// UINT8 ubGunShotsLeft; // duh, amount of ammo left
// UINT16 usGunAmmoItem; // the item # for the item table
// ...
//
// in the first struct, that is used for the default stuff, but
//
// ...
// INT8 bBombStatus; // % status
// INT8 bDetonatorType; // timed, remote, or pressure-activated
// UINT16 usBombItem; // the usItem of the bomb.
// union
// {
// ...
//
// in the struct that stores the bomb item.
// Now, if our action item has a Bombitem > 255, that value is read from UINT16 ubGunShotsLeft in OBJECT_GUN.
// In the OBJECTTYPE::data union, OBJECT_GUN and OBJECT_BOMBS_AND_OTHER both have the UINT16 that stores the usBombItem or ubGunShotsLeft at the same position. So until here it is ok...
// However, this value now gets written into ugYucky.ubGunShotsLeft - which is an UINT8 instead of UINT16. This means that any item number > 255 is cut down.
// This error seems to have always been here (13 years). It just never occured until now.
// An easy fix would be to just switch the positions of UINT8ubGunShotsLeft and UINT16 usGunAmmoItem. However we cannot do that, as that will affect every object read ever anywhere.
//
// For this reason, I now present you this filthy, ugly hack, specifically for action items handle bombs: