Forums » Bugs

bots can shoot you in NFZ and not trigger violation

«12
Dec 09, 2014 Kierky link
Having the Strike force start a shit fight with traffic2 would be gold. Not that they're useful anyway.
Dec 09, 2014 Pizzasgood link
"you are arguing that rules were made to be broken and not realizing that what is being discussed is a response to _breaking_ a rule, not removing the ability to break the rule"

"This suggestion to fixing this bug wasn't meant to end the ability to shoot people in the nfz"

Your suggestion would (except in the case of death-in-one-volley) eliminate the possibility of killing people inside the NFZ. So yes, you are talking about removing that ability. It doesn't matter whether that was the intention of the idea.

"Nobody is saying a device couldn't exist that you could equip to jam the signal and not be affected. But it could be easy to imagine such onstar-like-tech would be built into the fundemental systems of the ship and not be disconnectable."

Sure, if we were talking about a strong, unified, totalitarian galactic empire. That is not the setting we are in. It is completely impractical outside of ships produced within Serco and Itani spaces (thus my comment about nation space). Not to mention completely fucking stupid to attempt when there are so many hostile factions who might find a way to use it against you.

"we were discussing an issue involving just NFZ violations. The fact that you become temp KOS after had nothing to do with the topic. We could start another thread to apply the same logic to other violations, but the disabling of weapons was in response to the NFZ violation. "

Oh, I'm sorry, I didn't realize you were the only person allowed to bring up irrelevant things. With how you were saying the already implemented (and stupid) friendly fire protection somehow made kill switches a reasonable suggestion, I thought it was acceptable to bring up how the kill-switch concept would be ludicrous because if such a thing existed, it would be used all the time; to not use it would be insane. But obviously using it so widely isn't acceptable because it would completely change the nature of the game ("nowhere is safe" is a fundamental aspect of VO). So adding it in only small situations would actually increase the lunacy, not decrease it as you seem to think.

But hey, pardon me for not realizing you're a hypocrite. I'll try to be more understanding of your special needs in the future.
Dec 10, 2014 meridian link
"I'm all for treating npc's exactly the same as players. But if that's too complicated or causes more issues than it fixes, then [having stations disable weapons] is just as effective..."

How about we remove all weapons from the game entirely, and then we can abolish the NFZ altogether. Doesn't get any simpler or more effective than that.
Dec 10, 2014 cellsafemode link
The reason I suggested the KOS statement to be another thread was because I read it as a statement of "what if" after the suggestion would be implemented, since that is the only situation that your statement and line of reasoning would possibly make sense. It would be a valid question assuming the suggestion was already implemented and arguing how this affects non-NFZ KOS players.

I didn't read it as an example backing a point of view against the suggestion because the suggestion doesn't stop you from breaking any rules, rather it's explicitly a response to breaking one. Not sure how that equates to being a hypocrite, but feel free to think that attempting to make your comment have any merit at all (since its rooted in a false implication) equals hypocrite.

It's a bug. I offered a couple suggested fixes with arguments to defend them, feel free to make a serious attempt at one. The devs may choose to just address the bots not triggering NFZ and be done with it in which case this particular suggestion is moot, or they may take on the additional and more complicated one of also triggering NFZ violations by defending yourself in the NFZ. Fixing the bots may negate the need for the other though, depending on how/if they fix it.