(07-23-2014, 01:16 PM)Moriarty. Wrote: What you just said, is sanctionable. btw, this solves a lot of problems, like cloaked BS sneaking up and then suddenly uncloaking, killing you.
Since, before this change, people typed in engagement notices, waited for some time while still sneaking behind, and after ample amount of time, instakill you. Which, as Alley said, is borderline abuse.
We already had insta kills before cloaks existed even. And yet, I've never seen anyone being sanctioned for this line: "aggressors are not allowed to destroy a ship before allowing sufficient time to respond".
When there has been roleplay (of any kind), you can engage whenever you like to without having to write an engagement notice even. Of course, it has to be reasonable according the roleplay done before.
As for the change. (I know it's just a test period.) It was said, that only local chat will be disabled. Yet local, system and PM are disabled while cloaked. Why the sudden change of mind?
I will test this change for a few hours and see how it'll affect the roleplay experience. However, at this early point I pretend that the system and PM chat (except /r) deactivation is stupid.
If people can go up the plane and troll others in system chat, how will it help that cloaked ships cannot?
I think the local deactiviation (which was the main topic), is highly reasonable. Though the others not so much.