Crime Update a factual speed limit?

Well, a few might have already got it from today's dev update...

With 1.3 ramming inside the no fire zone with more than 100 m/s will be considered a crime.

Although I can understand that ram-griefing might be a problem to some, will this change not just reverse the situation?


Imagine the following situation:
You are approaching a station in your fully loaded Anaconda at more than 100 m/s. A griefer in a Sidewinder rams you, you get a bounty, because you rammed another ship while going faster than 100 m/s and the station will kill you. Of course it will also destroy the Sidewinder, but he won't care, because replacing it costs next to nothing. The only protection against this would be crawling all the way through the no fire zone at 90 m/s or so.


Not sure, if I got this right, but if so, I think this "solution" might cause more problems, than it solves. Maybe the docking computer will become a very popular module with these changes in place, but it would have to be limited to <100 m/s, too :)
 
I'm going to hang around the slot at George Lucas lazily swanning back and forth at about 50m/s in cycles. Anyone who touches me is getting boom boom.

Sounds like too simplified to me, although 100m/s speed limit isn't a bad thing IMO. Just doing it because of deliberate ramming seems strange.

Got a link to this?
 
They might consider the angles during a collision, fine the ship that pointing at the other ship, they might try backwards or sideways ramming but that's really hard to do from a front only view.
 
100ms? Seriously? I boost my 'conda in from 4k flat out and don't hit the brakes 'til the toast rack! How am I going to get in and pay my bounty now? Unless they've seriously overhauled the accidental shot bounty problem....
 
100ms? Seriously? I boost my 'conda in from 4k flat out and don't hit the brakes 'til the toast rack! How am I going to get in and pay my bounty now? Unless they've seriously overhauled the accidental shot bounty problem....

You can still do this, just make sure you don't hit anyone with your ship whilst doing so.
 
That's not the problem... but how will you make sure, that nobody will hit _you_?

Well if you're the one speeding that's _your_ problem.

Go faster than allowed and risk it or take it slowly and carefully and play safe.
 
100m/s is fine, I rarely go faster near other ships around stations anyway. You know, common courtesy and all that. ;) Personally I am getting a little bit tired with the condas and T9s boosting through the slot hoping to catch a newbee for lolz. Right now innocent people can be 'griefed' by rammers with little you can do. After the change the only victims of 'griefing' are those who knowingly speed around dense traffic areas. You can still speed all you want, but if *anything* happens you are responsible.
 
That's exactly what I'm criticizing, glad you finally got the point :)

My solution would be to use the scanner to see what ships are in your environs. Or the mark 1 eyeball.

Mostly there aren't any other CMDRS around where I am so I can speed in as fast as I like. If there are other cmdrs then I'll go a bit slower.

<pulls up space crate> in all my years of trading, rares and smuggling I can count on one hand the amount of NPCs I have hit coming in or going out, and it has ALWAYS been because I am boosting in or out, so I can't see it being a problem.
 
I normally cruise through the slot in my Clipper at 150-180 m/s.

That's 402 miles per hour.

A "speed limit" is reasonable. A 700 ton ship traveling at 402 miles per hour would be capable of causing catastrophic damage to anything it hit, including the space station.
 
100ms is a joke people intent on killing with ramming aren't trying to bump you they're trying to kill you at full speed plus boost. 250ms is still a bump not intent to kill..
the rammers are going to have a field day with this..
 
So, now people will wait for some trader to enter the station at 150m/s, bump them at 90m/s and boom! the trader becomes the criminal. Now executed by the station.
 
Back
Top Bottom