3.0 Crime rules leads to marooning

thefomo

T
I'm in a fully kitted Vulture with the smallest FSD to save power and weight, the FSD is far too weeny to jump out of the system.

Here's the problem... I accidentally fired on a ship, a g wrong click, became wanted.

Now I'm screwed, I'm essentially marooned with no way out of the system.

- Anonymous protocols apply to me in the station

- I can't get access to the shipyard to switch out of this ship.

- I can't get access to the outfitting to fit a FSD big enough to jump to another system.

- There's only one other outpost in the system, it does solve my access problem

- Have tried self destruct but the bounty is still there so that doesn't solve it.

Any ideas?

I don't think I've got the patience to grind through Harmless in a Sidewinder for weeks to get my fleet again.
 

Bortas

Bortas
thefomo said:
- Have tried self destruct but the bounty is still there so that doesn't solve it.
Click to expand...

Where did you respawn? This should have taken you to a detention centre, afaik.

I don't think I've got the patience to grind through Harmless in a Sidewinder for weeks to get my fleet again.
Click to expand...

File a ticket. They will probably help you out quickly.
 

Adhock

A
Another case that supports my thesis on why the current balance based around jump rating is terrible and that A) All ships should be able to outjump a Viper 3 regardless of specialty and that B) players need to pay closer attention their ships weight and balance against ability.
 

GroundxZERO

GroundxZERO
Point your ship towards the nearest star and go max throttle in SC. Eventually with enough help from fuel rats and reloggoing you might make it. Report back in next year and let us know lol.
 

Robin of Spiritwood

Robin of Spiritwood
The bounty might just be around 300-400 credits. You shouldn't end up in this position by design, it's an unforeseen situation. A ticket seems the best option.
 

Straha Yeagar

S
Robin of Spiritwood said:
The bounty might just be around 300-400 credits. You shouldn't end up in this position by design, it's an unforeseen situation. A ticket seems the best option.
Click to expand...

Except it is very foreseeable. Fit a frame shift drive that is not capable of getting a ship out of a system, risk getting stuck in the system. This isn't poor game design. It is a poor outfitting choice.
 

M00ka

M00ka
Put it down to a learning experience. Always make sure your ship can jump out of a system, even if it mean losing a few m/s or whatever. And never play in your home system, that is just asking for trouble.

I realise others have told you to submit a ticket (good luck with that) but I wish Customer Support wouldn't help players out when the error was 100% the player's fault. FD have promulgated the new C&P as much as they can, they shouldn't be responsible for holding hands as well.

Good luck Commander.
 

master_xean

master_xean
All FSD jump ranges need to be doubled across the board.

The "repeatedly jump to star" minigame is the worst minigame in ED and the worst thing about the game overall.

M00ka said:
Put it down to a learning experience. Always make sure your ship can jump out of a system, even if it mean losing a few m/s or whatever. And never play in your home system, that is just asking for trouble.

I realise others have told you to submit a ticket (good luck with that) but I wish Customer Support wouldn't help players out when the error was 100% the player's fault. FD have promulgated the new C&P as much as they can, they shouldn't be responsible for holding hands as well.

Good luck Commander.
Click to expand...

Talk to a shrink
 

Bortas

Bortas
M00ka said:
I realise others have told you to submit a ticket (good luck with that) but I wish Customer Support wouldn't help players out when the error was 100% the player's fault. FD have promulgated the new C&P as much as they can, they shouldn't be responsible for holding hands as well.
Click to expand...

Except it's not working as described... He tried to self destruct... shouldn't this have taken him do a detention centre, where he could have payed off his bounty and buy another FSD?
 

Straha Yeagar

S
Bortas said:
Except it's not working as described... He tried to self destruct... shouldn't this have taken him do a detention centre, where he could have payed off his bounty and buy another FSD?
Click to expand...

That is secondary to the fact that purposely fitting a frame shift drive that is incapable of getting out of the system. Regardless of anything else, THAT is why he can't leave the system. If he had an adequate FSD fitted, he would be able to get out of the system regardless of anything else. Full stop.
 

kofeyh

kofeyh
M00ka said:
Put it down to a learning experience.
Click to expand...

A game that 'locks' a player in a state, indefinitely, isn't an experience the player should learn from. Wrong side of the coin. The game itself has failed to account for a situation that is entirely possible to do. Developers work pretty hard to ensure no such 'stuck' situations can exist. Because it's removing all choice. Consequences are fine; removal of all choice, isn't.

Should the OP have considered a bigger FSD? Probably; but the game shouldn't be 'locking' commanders so they are unable to self-resolve simply because they fitted a perfectly valid module. There is no warning when transferring that a range starve ship may not be able to leave the system, to warn players either, IIRC.

And this is once again a reminder that combat ship limitation via range is a very daft thing to have institutionalised.
 

Straha Yeagar

S
kofeyh said:
A game that 'locks' a player in a state, indefinitely, isn't an experience the player should learn from. Wrong side of the coin. The game itself has failed to account for a situation that is entirely possible to do. Developers work pretty hard to ensure no such 'stuck' situations can exist. Because it's removing all choice. Consequences are fine; removal of all choice, isn't.

Should the OP have considered a bigger FSD? Probably; but the game shouldn't be 'locking' commanders so they are unable to self-resolve simply because they fitted a perfectly valid module. There is no warning when transferring that a range starve ship may not be able to leave the system, to warn players either, IIRC.

And this is once again a reminder that combat ship limitation via range is a very daft thing to have institutionalised.
Click to expand...

Except the OP stated that he purposely did this knowing it was too small of a FSD to get out of the system. This wasn't some ooops. It was purposely done by the OP.
 

kofeyh

kofeyh
straha20 said:
That is secondary to the fact that purposely fitting a frame shift drive that is incapable of getting out of the system. Regardless of anything else, THAT is why he can't leave the system. If he had an adequate FSD fitted, he would be able to get out of the system regardless of anything else. Full stop.
Click to expand...

And the game allows it. The game does not warn you cannot leave the system in that ship. It's creating an entirely avoidable 'stuck' situation. We've just seen Frontier resolve that for fuel access due to it locking people. At the very least, the system should warn during ship transfer, that the vessel will be unable to leave the system, and potentially block transport.

A game that intentionally wedges players into locked scenarios like this is foolishness.
 

Straha Yeagar

S
kofeyh said:
And the game allows it. The game does not warn you cannot leave the system in that ship. It's creating an entirely avoidable 'stuck' situation. We've just seen Frontier resolve that for fuel access due to it locking people. At the very least, the system should warn during ship transfer, that the vessel will be unable to leave the system, and potentially block transport.

A game that intentionally wedges players into locked scenarios like this is foolishness.
Click to expand...

So basically, save some players from their own stupidity by removing their choices, even if they are bad choices to be made? Purposely extreme downsizing the FSD is something that a surprising number or players do...
 

kofeyh

kofeyh
straha20 said:
Except the OP stated that he purposely did this knowing it was too small of a FSD to get out of the system. This wasn't some ooops. It was purposely done by the OP.
Click to expand...

They already have consequences of the bounty. Which they have to leave to pay off. The entire thing is ridiculous. Frontier has specifically engineered a situation that will lock players, despite being warned this was going to happen. Before this, it was access to fuel that locked.

I have no problems with consequences; neither does the OP it appears. It's the logic-loop of requiring players leave a system, but ensure there is a state that prevents them from doing so. That, is foolish.
 
  • Like (+1)
Reactions: NW3
You must log in or register to reply here.
Back
Top Bottom