unexploded exploded cache
Posted: 2009-07-13 14:27
i was playing korengal valley on ABC server today when i encountered the following.
we had twenty tickets left (we being the insurgents) and were defending the caches. Then suddenly up came the message that a cache had been destroyed. This confused me as I was busy defending the only map visible cache at the time.
A little later I took a screenshot. Now from what I understand, only 11 cache spawn now right? Therefore, if only 10 tickets are left, there should be only 2 caches remaining. However, after a little bit, I checked the map, and there were 3 caches marked on the map, one visible, two invisible. I checked the visible cache and it was still there.
I made a screeny of the map:

as you can see, we have ten tickets left, but three caches up. Also the message that a cache had been destroyed came a few seconds earlier. Also, the cache in E4 was the one that came up after the message was displayed.
Anyways, maybe im terribly wrong, probably this is already known, but I didn't find anything recent so i figured i should post this bug
we had twenty tickets left (we being the insurgents) and were defending the caches. Then suddenly up came the message that a cache had been destroyed. This confused me as I was busy defending the only map visible cache at the time.
A little later I took a screenshot. Now from what I understand, only 11 cache spawn now right? Therefore, if only 10 tickets are left, there should be only 2 caches remaining. However, after a little bit, I checked the map, and there were 3 caches marked on the map, one visible, two invisible. I checked the visible cache and it was still there.
I made a screeny of the map:

as you can see, we have ten tickets left, but three caches up. Also the message that a cache had been destroyed came a few seconds earlier. Also, the cache in E4 was the one that came up after the message was displayed.
Anyways, maybe im terribly wrong, probably this is already known, but I didn't find anything recent so i figured i should post this bug