Shafted by an invisible boundry

Saool

Saool
Fighting to defend the independent system of Loperada from the capitalist clutches of the Federation who wanted to spread it's 'Freedom' to the system to exploit it, I found my trusty Viper in a gripping battle against a master rated Python in a war zone.

Out gunned, I looped and wrestled with the Python for many minutes, firing off chaff and slowly burning down it's shield. Then the break though, it's shields down and the ship facing away from me, I took the opportunity to go for it's engines. Success! After what seemed like an age the enemy ship was adrift. However it was still drifting and at speed. I held back out of it's still firing guns range to let me shield recharge. Of course thet let it;s shield recharge as well.

Round 2

Now with a clear advantage I started to work at the drifting Python's shield once again. This time I would be gunning for the already damaged power plant. On the tussle went, but soon the ship stopped firing all together. Had I shot out it's cockpit glass and the crew expired? I did not care. When the power plant finally blew, the hull was only 2% itself. Victory!

*6500c fine for the murder of Federation Navy Python*

Wait what?!

Apparently at some point in the fight we had drifted across an invisible boundary and were no longer in the War Zone. There was no warning that the rules had changed, but what started out as a legitimate target was now not a target at all. Now I had a bounty and no reward for my kill.

To make matters worse I was not effectively locked out of the war and unable to help defend the system.


Fair? Unfair? Silly? Tough luck? What do you think?
 
Last edited:

Dbrn47

Dbrn47
Saool said:
Fighting to defend the independent system of Loperada from the capitalist clutches of the Federation who wanted to spread it's 'Freedom' to the system to exploit it, I found my trusty Viper in a gripping battle against a master rated Python in a war zone.

Out gunned, I looped and wrestled with the Python for many minutes, firing off chaff and slowly burning down it's shield. Then the break though, it's shields down and the ship facing away from me, I took the opportunity to go for it's engines. Success! After what seemed like an age the enemy ship was adrift. However it was still drifting and at speed. I held back out of it's still firing guns range to let me shield recharge. Of course thet let it;s shield recharge as well.

Round 2

Now with a clear advantage I started to work at the drifting Python's shield once again. This time I would be gunning for the already damaged power plant. On the tussle went, but soon the ship stopped firing all together. Had I shot out it's cockpit glass and the crew expired? I did not care. When the power plant finally blew, the hull was only 2% itself. Victory!

*6500c fine for the murder of Federation Navy Python*

Wait what?!

Apparently at some point in the fight we had drifted across an invisible boundary and were no longer in the War Zone. There was no warning that the rules had changed, but what started out as a legitimate target was now not a target at all. Now I had a bounty and no reward for my kill.

To make matters worse I was not effectively locked out of the war and unable to help defend the system.


Fair? Unfair? Silly? Tough luck? What do you think?
Click to expand...

Odd... at any point did the tag change from Lawless to Clean? The area shouldn't matter, if it was Lawless to begin with and stayed that way, it shouldn't have been a fine. Send a bug report.
 

Nicholas Powell

Nicholas Powell
Ah, yes, the blight of the Conflict Zone. Had the same thing happen to me. Yes, I too have crossed the *cough-cough* Belgrano *cough-cough* line.
 

Muss

Muss
Ya know as much as I would be annoyed it does sort of make sense, imagine you were in WW2 and chasing the enemy towards the Swedish border, as soon as they cross they are safe. in saying that you should have been told they were no longer a valid target or been given some sort of warning like "Target approaching non combat zone" ect.


I feel that you deserve the credit for the kill in this case and FD should implement some sort of notification as above
 
Last edited:

Saool

Saool
Muss said:
Ya know as much as I would be annoyed it does sort of make sense, imagine you were in WW2 and chasing the enemy towards the Swedish border, as soon as they cross they are safe. in saying that you should have been told they were no longer a valid target or been given some sort of warning like "Target approaching non combat zone" ect.


I feel that you deserve the credit for the kill in this case and FD should implement some sort of notification as above
Click to expand...

The only issue with your European analogy, is that in this case the 'Law' , IE the current ruling party, is Loperada and Co... the very people I was fighting along side in the war zone. So here we have a group that is in a civil war, who are paying me to kill there opponents, but also putting a bounty on my head for killing that opponent... hmmm.
 

Muss

Muss
Saool said:
The only issue with your European analogy, is that in this case the 'Law' , IE the current ruling party, is Loperada and Co... the very people I was fighting along side in the war zone. So here we have a group that is in a civil war, who are paying me to kill there opponents, but also putting a bounty on my head for killing that opponent... hmmm.
Click to expand...

Well when ya put it like that....
 

n13L5

n13L5
First of all, props for your story, especially the intro line about spreading "freedom" so capitalism can exploit.

Second, I have to disagree with the answers that talked about drifting out of the war zone (and into sweden or whatever) would be just like real life and therefore "nothing wrong with you getting shafted"

The truth is, that the warzone is a TINY instance in the vastness of space that all belongs to the same system. You could not even travel an appreciable distance in that instance even if you went at max throttle uninterrupted in a single direction for a week.

So by means of logic and the relative size of space and that war zone instance, the invisible border is a bug and should be reported. Possibly, you ran up against the maximum instance boundry FD's game engine supports - something related to coordinate precision depending on how many bits are used to store those. If that was the case, FD should just give the next bubble created identical parameters to the last, or simply wrap you around, coming back into the same instance from the opposite side.
 
Last edited:

Kyudos

Kyudos
This would seem like a bug to me - surely, with the instancing model, the whole of a conflict zone instance should be a conflict zone - or the at least the bubble should be big enough that you'd have to make a determined effort to cross the boundary.
 

GrimThara

GrimThara
I had no idea this could even happen ... I'll have to be more careful. I've fought some enemies over 20km from the center of a conflict zone and been fine so far. Just how far out did you fly from it?
 

Judz

J
If your outside 50km from the warzone then it happens oddly, I have had it twice, the 2nd time I too was chasing a ship with 0 engine power and it was still quicker than me on 4 pips and boosting, I was in a Vulture and it was in a Viper. I didn't swear much at all...either time.
 

Cmdr Andy B

Cmdr Andy B
the same happened to me while going after an anaconda, i got a 5k bounty when i finally killed it.

by the time it died i was 106 km away from the CZ nav point but still showing as allied with my chosen faction.

IMO the only way out of a CZ should be to jump away, its more than a little silly that we have an invisible boundary to contend with, we at least need a warning.
 

Han Brannigan

Han Brannigan
Saool said:
*6500c fine for the murder of Federation Navy Python*

Wait what?!

Apparently at some point in the fight we had drifted across an invisible boundary and were no longer in the War Zone. There was no warning that the rules had changed, but what started out as a legitimate target was now not a target at all. Now I had a bounty and no reward for my kill.
Click to expand...

Its a known problem - but there does not seem to be a known solution
 
You must log in or register to reply here.
Back
Top Bottom