Rules around Cloak and Rp Clarification

[Eternal.Journey]

Metagaming, Powergaming. People use them interchangeably and the point remains the same. Whether its defined as one or the other, the fact remains that content presenting itself as either term is against the rules. Wild discord had a very large discussion (with staff present and also part of the conversation). This whole cloaking issue is far less about the why, the when, the where. Its about the How.

Someone logs in, launches, cloaks. They don't interact with the people, they don't do anything other than follow them around/camp them out at their base while remaining invisible. This has no counter-play. And before you throw at me about a cloak disruptor. disruptor type 3 is 9k 10k range, and mountable on Battleships and Battlecruisers. Disruptor type 2 is 6k 9k range and mountable on GBs and Cruisers. Disruptor type 1 is 3k 8k range and Snub mountable. Like the cloaks that they're undoubtedly made to counter. Someone sat at 7k on a snub cloak while observing any wild is never ever going to get to counter-play this, even if they go and buy the cloak disruptors that they can mount.
Its possible that someone can counterplay this kinda move, using a snub cloak disruptor. Barely, but yes. There is. Let's also note down the absurdity that it should be mandatory to watch the player list to see "Some.Random.Name, System: ????", because that's also both technically Metagaming and against the rules.

I saw the original post, and the image contents that were there. There were Three images in the initial post within a spoiler labelled "Noth Infection" (if memory serves me correctly on the title of the spoiler), that was then laughed off by another RPer that the base wasn't even remotely interesting to them, no concrete evidence that it was alien in any way (of which this person should be congratulated on decent roleplay conduct). Of which after was then edited to insert an additional screenshot that was an almost point blank close up of the "Maybe Nomad Power Source" Which they did not collect from in game, nor during the encounter, due to the activity around and in the area of the system.

Not only that. But the person used the fact that the ambient NPCs, that are SPECIFICALLY DESIGNED to NOT ENGAGE ANYONE were "Not Attacking Them, So They Must Be Infected". Yeah. Smort move eh?

Personally I have no issue with anyone trying things to expose Covert Operators of the Wilde, be they Official or Indie. I have a problem with poor use of something that was specifically done to get back at the multiple clashes these Wild Boys have had with the various Omicron Organisations. Notice that this is also another "Staff Vote" scenario where people are dissatisfied with the outcome of a VR that was sent against their actions.

Being a Dick is rather easy. Especially when you are doing it to get back simply because you cannot beat them in game. Its disappointing to see that people are fighting a corner of a VR that simply resulted with a slap on the wrist and a telling off, rather than an actually substantial action. If people too are willing to quit over being slapped once over something that they were merely being corrected on what they shouldn't have done, then it kinda also speaks about their real life character/mindset. Not to mention the fact that their position is that they're willing to leave over the whole telling off, rather than accept the consequences of a staff decision. Like. Really? Over being told off from one adult to another?

We are at a similar point with the whole "[STAFF]: WARNING" thread, that people cannot take a sanction over incidents that have happened. People need to stop feeling hurt over sanction threads popping up against them. We play a game, we all make mistakes. Its part of a process. Called "Learning." It won't kill you, I promise!


Edit: I have been informed that the ranges i quoted for cloak disruptors is actually wrong. I lay corrected. 10k/9k/8k respectively aparrently. So theres that. Theres also this lovely edit notification telling you what happened, and rather than just edit out the old incorrect info and hide it like it never happened, I have left in the incorrect data to show.

---