Quote:Dangers[edit]
A bean bag round can severely injure or kill in a wide variety of ways. They have caused around one death a year since their introduction in the U.S.[2] A round can hit the chest, break the ribs and send the broken ribs into the heart. A shot to the head can break the nose, crush the larynx or even break the neck or skull of the subject. This is why many officers are taught to aim for the extremities when using a bean bag round. A strike in the abdominal area can cause internal bleeding or strike the solar plexus which can disrupt breathing or heartbeat, but such a hit is generally safer than most other areas as well as presenting a larger target than an extremity. Fatalities are occasionally the result of mistaking other shotgun rounds for bean bags.[2]

In 2013, in Park Forest, Illinois, an autopsy showed that a 95-year-old man had died from hemoperitoneum as a result of being shot by police with a bean bag gun.

Quote:David Klinger, senior research scientist for The Police Foundation in Washington, D.C. who is an expert on police decision-making and the use of deadly force, said that officers are trained to fire the beanbag rounds at some distance, rather than being up close, and to aim at the extremities.
Typically, we don't want officers to fire the beanbag shotgun rounds in close proximity, but there's always, like anything else, extenuating circumstances," Klinger said.

(Aug 29, 2017, 10:29 AM)Bambo Wrote: Doctor Internet, from what I've understood, the ejecting and the damaging was not intended correct? So if Wesley decided to use the Beanbag as a means to eject that should be fixed and if the player was damaged in the vehicle, that is already fixed. So the fix been rolled out would not factor in the removal of this blacklist as both what was intended and what happened was not planned to be a feature? Meaning the usage of the beanbag was in that way at that time and changes that happen after should not be a factor at all in this UBL.
 
I didn't decide to use the bean bag round as means to eject the person. I was using the less-lethal options to somehow scare him off enough to stop and get out of his bus on his own. I did not have an idea that the bus driver was going to explode backwards and hit the concrete like that. And even then, a fix was supposed to be pushed through a week prior to that. It wasn't however and thus created this situation. I do think it accounts for in the possible removal of my recent blacklist item.
 
As well as it being used to eject people, players were also getting damaged by it when in vehicles and they've written it in OOC. Something that rarely occurred incident but known by most. I do not know if this was fixed prior or after but I am aware it was a problem at one point.
 
Which would have been tolerable. If they were getting small hits being inside a vehicle but weren't ejected out, that would have been the perfect application of it as it might manually get a driver to exit his vehicle. I know they can mostly penetrate thin panels of glass but the way he ejected and slammed onto the concrete is not something I could have prevented. Plus, the whole excessive part shouldn't apply to me as I immediately stopped firing after seeing the damage it does. That's what you usually do, if it incapacitates them and halts them in any actions they are doing, stop firing. (obviously).

Last note, as you said you had enough time to warn the driver countless of times and had the same amount of time to move away from the front of the vehicle, take other precautions, spike-strip, vehicle block and so on. You've said that you study to become a law enforcement officer, but even I know that shooting any kind of weaponry be it non-lethal, less-than-lethal or lethal IS a last resort.
 
And as the bus driver was given multiple commands, just as in real life during a BTGV (or felony stop, or dangerous situation however you want to call it), it was a last resort because he evidently did not want to listen. Or as later was proven: wasn't able to listen due to his lag.
 
You said, and I quote;
 

Quote:You don't have enough time for more patience and observation during a split second situation though, Bambo.

 
However given that you've stated that you've given commands to the driver multiple times which would be beyond a split second situation and allow you to observe and find ways to immobilize the vehicle even more with the tools you had access to.
 
If that split second situation is referred to the nudge the vehicle had while in a position that it was highly possible that it couldn't move due to it's state, can you decide if a person is a threat in that split second and possibly do something that could potentially end in a bad way?
 
Potentially end in a bad way, Bambo. If I had let the bus driver go on with accelerating and it would have gained momentum or move more than it was going to, it could have potentially ended in a bad way too. Again, we come back to the split-second decision where you either have to figure out if you, your officers and civilians are at risk or if you, your officers and civilians aren't at risk. And I decided they were. I am sure many other players would have taken the same choice taken the circumstances.
 

Limelight - Link watcher

You're about to enter the following site: Limelight - Link watcher You're about to enter the following site: https://www.nbcmiami.com/news/local/Shoot-or-Not-To-Shoot-How-Police-Make-The-Split-Second-Decision-400635271.html Please note: You should only visit trusted sites. We are not responsible for any loss of your privacy. https://www.nbcmiami.com/news/local/Shoot-or-Not-To-Shoot-How-Police-Make-The-Split-Second-Decision-400635271.html Please note: You should only visit trusted sites. We are not responsible for any loss of your privacy.

https://www.nbcmiami.com/news/local/Shoot-or-Not-To-Shoot-How-Police-Make-The-Split-Second-Decision-400635271.html
 
[url=https://www.nbcmiami.com/news/local/Shoot-or-Not-To-Shoot-How-Police-Make-The-Split-Second-Decision-400635271.html][/url]
 
That is an article that gives some insight on what split-second decisions can be as I don't think you completely understand the concept behind them. They're usually based on a totality of circumstances and seeing the circumstances that have risen during this incident, I had all the right to discharge my firearm the second he continue to disobey the orders given to him and started to try and make his way out of that scene.
 
You are probably going to say that it wasn't meant to kill and that it was meant to be used as a ram in a way but from Doctor Internet's post, the damage the beanbag had as well as the ejection was not an intended feature thus both of them are not factoring in this. The main case here is you discharging your weapon through assumptions. Assumptions that the vehicle revving up the engine without the driver of the van was still a threat without observing. Observing might not happen in a split second but if you had multiple chances to give commands to the driver, you had multiple chances to observe.
 
I had multiple chances to observe when I first got onto the scene. I observed how a bus/van was ramming into our vehicles. I observed how it hit ForceGhost after he stepped out of his vehicle to try to verbally make it to stop. I observed how it got to a stop and under gunpoint of me (and probably a few others), I observed how the driver pressed down the pedal. Nothing was done out of 'plain assumptions' as you two are trying to put it, everything was done as what happened prior and what was about to happen if I hadn't pulled the trigger once. You do not have time to observe during split-second decisions and that split-second went live as soon as he started pressing down the gas pedal. Not when I was still trying to talk him out of the bus. Most officers would have made the same choice.
 
The bean bag round was also not supposed to work as a... ''ram in a way'', it was supposed to work as a deterrent for the bus driver and his idea to start driving again.
 
"Any suspicious action and you will be shot.'' is what I kept in mind. It is a line (out of many) we practised during BTGV. He made a suspicious action and was shot. Not fatally, but in an unconscious and injured state. It is not my fault the game's engine decided to throw him out of that bus and smack him onto the concrete.

I obviously know the effects of that on lethal weaponary (being the normal M3 or my Glock I usually carry) but I expected differently from a less-lethal shotgun.
 
Not only that, but if the staff team will start handing out blacklists everytime THEY think we discharged based on an assumption, there will be a long list of weapon's blacklists after mine and I certainly don't want to see that happening.
 
What I want in this UBLR is for the staff team (not just you and Enzyme) to take a look at the situation and to deter whether or not one bean bag round was suffient and whether or not it's fair to keep this on my history even though I had no idea the bean bag round was going to act the way it acted. It's only because of the damage the suspect gained through the game's engine that this got out of hand so much. It's not because I figured one less-lethal round at someone that was still a threat and was actively continuing to be a threat was justified, which, in my opinion it was.

(Aug 29, 2017, 04:19 PM)Wesley Lawrence Wrote:

(Aug 29, 2017, 10:29 AM)Bambo Wrote: I didn't decide to use the bean bag round as means to eject the person. I was using the less-lethal options to somehow scare him off enough to stop and get out of his bus on his own. I did not have an idea that the bus driver was going to explode backwards and hit the concrete like that. And even then, a fix was supposed to be pushed through a week prior to that. It wasn't however and thus created this situation. I do think it accounts for in the possible removal of my recent blacklist item.

The fix does not account for the removal as the system was existent during the blacklist. If we follow that mindset every player that was blacklisted for a rule that has changed or removed should have that blacklist removed. You used the force when the system 'bug' was in place and hence the results. Was the bug totally not known? Was players not aware that it damages and also ejects players? I highly doubt that as there are suggestions to stop it as well as multiple OOC comments.
 
Which would have been tolerable. If they were getting small hits being inside a vehicle but weren't ejected out, that would have been the perfect application of it as it might manually get a driver to exit his vehicle. I know they can mostly penetrate thin panels of glass but the way he ejected and slammed onto the concrete is not something I could have prevented. Plus, the whole excessive part shouldn't apply to me as I immediately stopped firing after seeing the damage it does. That's what you usually do, if it incapacitates them and halts them in any actions they are doing, stop firing. (obviously).

If you know they can penetrate it why use it that up close?

And as the bus driver was given multiple commands, just as in real life during a BTGV (or felony stop, or dangerous situation however you want to call it), it was a last resort because he evidently did not want to listen. Or as later was proven: wasn't able to listen due to his lag.

He might be lagging, he might not be listening but if the person was not a threat, it didn't require such force. You had many choices to further make sure the vehicle was immobilized but those were not done.
 
You said, and I quote;
 

Quote:You don't have enough time for more patience and observation during a split second situation though, Bambo.

 
However given that you've stated that you've given commands to the driver multiple times which would be beyond a split second situation and allow you to observe and find ways to immobilize the vehicle even more with the tools you had access to.
 
Potentially end in a bad way, Bambo. If I had let the bus driver go on with accelerating and it would have gained momentum or move more than it was going to, it could have potentially ended in a bad way too. Again, we come back to the split-second decision where you either have to figure out if you, your officers and civilians are at risk or if you, your officers and civilians aren't at risk. And I decided they were. I am sure many other players would have taken the same choice taken the circumstances.

That is not certain at all though due you acting from a nudge we weren't able to see the threat the vehicle would have posed.
It's not would've but of a could've 

Limelight - Link watcher

You're about to enter the following site: Limelight - Link watcher You're about to enter the following site: https://www.nbcmiami.com/news/local/Shoot-or-Not-To-Shoot-How-Police-Make-The-Split-Second-Decision-400635271.html Please note: You should only visit trusted sites. We are not responsible for any loss of your privacy. https://www.nbcmiami.com/news/local/Shoot-or-Not-To-Shoot-How-Police-Make-The-Split-Second-Decision-400635271.html Please note: You should only visit trusted sites. We are not responsible for any loss of your privacy.

https://www.nbcmiami.com/news/local/Shoot-or-Not-To-Shoot-How-Police-Make-The-Split-Second-Decision-400635271.html
 
 
That is an article that gives some insight on what split-second decisions can be as I don't think you completely understand the concept behind them. They're usually based on a totality of circumstances and seeing the circumstances that have risen during this incident, I had all the right to discharge my firearm the second he continue to disobey the orders given to him and started to try and make his way out of that scene.

One question, if the vehicle did ram through vehicles why did you stand in front of it that up close without taking other precautions?
 
I had multiple chances to observe when I first got onto the scene. I observed how a bus/van was ramming into our vehicles. I observed how it hit ForceGhost after he stepped out of his vehicle to try to verbally make it to stop. I observed how it got to a stop and under gunpoint of me (and probably a few others), I observed how the driver pressed down the pedal. Nothing was done out of 'plain assumptions' as you two are trying to put it, everything was done as what happened prior and what was about to happen if I hadn't pulled the trigger once. You do not have time to observe during split-second decisions and that split-second went live as soon as he started pressing down the gas pedal. Not when I was still trying to talk him out of the bus. Most officers would have made the same choice.
 
The bean bag round was also not supposed to work as a... ''ram in a way'', it was supposed to work as a deterrent for the bus driver and his idea to start driving again.
 
"Any suspicious action and you will be shot.'' is what I kept in mind. It is a line (out of many) we practised during BTGV. He made a suspicious action and was shot. Not fatally, but in an unconscious and injured state. It is not my fault the game's engine decided to throw him out of that bus and smack him onto the concrete.

You have experience with Garry's Mod and the server for quite a while, the vehicle was in such a bugged state that it wasn't certain if it was going to move, it wasn't certain if the driver left the car he'd die, it wasn't certain what would happen. But you used a weapon that is known to eject players at an immense force as a 'deterrent' for him to not move. There were actions that you could have taken that would have ended in a much more secure way but you chose to shoot at a glitched vehicle's driver and the result is not the game's fault but yours.

I obviously know the effects of that on lethal weaponary (being the normal M3 or my Glock I usually carry) but I expected differently from a less-lethal shotgun.

As I said countless of times, less-than-lethal shotgun is still lethal.

Limelight - Link watcher

You're about to enter the following site: https://articles.latimes.com/2002/jun/03/local/me-nonlethal3 Please note: You should only visit trusted sites. We are not responsible for any loss of your privacy.

https://articles.latimes.com/2002/jun/03/local/me-nonlethal3
 
Not only that, but if the staff team will start handing out blacklists everytime THEY think we discharged based on an assumption, there will be a long list of weapon's blacklists after mine and I certainly don't want to see that happening.

It's not everytime, it was this time because you shot at a vehicle that did NOT pose visual threat to warrant a shot from any kind of weaponary. You assumed that the bus would move and that assumption was one of the causes of the blacklist.
 
What I want in this UBLR is for the staff team (not just you and Enzyme) to take a look at the situation and to deter whether or not one bean bag round was suffient and whether or not it's fair to keep this on my history even though I had no idea the bean bag round was going to act the way it acted. It's only because of the damage the suspect gained through the game's engine that this got out of hand so much. It's not because I figured one less-lethal round at someone that was still a threat and was actively continuing to be a threat was justified, which, in my opinion it was.

Quote:Non-lethal in this case would have been my ram, but no way was I going to get closer to the bus than I already was to try and strike this guy out of his vehicle. I can already imagine what would have happened when I would move in and the guy would start accelerating. 

Quote:The fix does not account for the removal as the system was existent during the blacklist. If we follow that mindset every player that was blacklisted for a rule that has changed or removed should have that blacklist removed. You used the force when the system 'bug' was in place and hence the results. Was the bug totally not known? Was players not aware that it damages and also ejects players? I highly doubt that as there are suggestions to stop it as well as multiple OOC comments.

Quote:If you know they can penetrate it why use it that up close?

Quote:He might be lagging, he might not be listening but if the person was not a threat, it didn't require such force. You had many choices to further make sure the vehicle was immobilized but those were not done.

Quote:However given that you've stated that you've given commands to the driver multiple times which would be beyond a split second situation and allow you to observe and find ways to immobilize the vehicle even more with the tools you had access to.

Quote:That is not certain at all though due you acting from a nudge we weren't able to see the threat the vehicle would have posed.
It's not would've but of a could've.

Quote:One question, if the vehicle did ram through vehicles why did you stand in front of it that up close without taking other precautions?

Quote:You have experience with Garry's Mod and the server for quite a while, the vehicle was in such a bugged state that it wasn't certain if it was going to move, it wasn't certain if the driver left the car he'd die, it wasn't certain what would happen. But you used a weapon that is known to eject players at an immense force as a 'deterrent' for him to not move. There were actions that you could have taken that would have ended in a much more secure way but you chose to shoot at a glitched vehicle's driver and the result is not the game's fault but yours.

Quote:It's not everytime, it was this time because you shot at a vehicle that did NOT pose visual threat to warrant a shot from any kind of weaponary. You assumed that the bus would move and that assumption was one of the causes of the blacklist.

Quote:But you felt threatened by a nudge, wouldn't that mean you were already close enough?

Quote:I have requested everyone in the staff team to voice their opinions and have considered them and am close to reach a conclusion.
Please add anything you'd want to add before this is concluded.