Source-X icon indicating copy to clipboard operation
Source-X copied to clipboard

Butte issues

Open Tolokio opened this issue 3 years ago • 0 comments

-Butte got no delay so player can use it very very fast, but it can be solved by script using @dclick. For this, I prefer to leave it as it is.

-Butte can only deal with one kind of ammo. If butte have 1000 arrows inside, and then anyone fires at butte with a crossbow, all arrows will be replaced by a one single bolt. (new ammo will always replace old ammo no matter amount)

-Ammo inside the butte can be grabbed by anyone but only if he got a ranged weapon equipped. If there is no ranged weapon equipped, ammo can't be grabbed (I think this can be fixed by script using @dclick

NOTES: -Ammo will not be removed or replaced if weapon used uses no ammo, for example throwing weapons. In this case ammo already in the butte will remain until it is picked up or new ammo replace it. -I dont know how OSI does it, so Im not sure what shall be done.

-I got this trigger done (not added to sourcex) image It allow more control of butte behaviour and in theory it could be used to fix the ammo issue as it allow u to use tags instead "mores". Maybe it can be fixed by @dclick as well. Would need to test it to be sure. image

For me, butte can stay how it is, I am just informing about. Anyone can script a t_archery_butte_custom, to replace default archery buttes.

Tolokio avatar Oct 20 '22 14:10 Tolokio