Staying Humble - Clouds over Myrkr OOC

[Algarus]

@Mad Dog @Algarus just a quick clarification on my post, I made it on the assumption that you both got warned of my presence at the max range for normal sensors, not max range for long range sensors. Algarus, your post stated that you sensed my ship at the same time as the Cloud, but your fighter does not have long range sensors. From the tech rules: "All ships are considered to have basic functional necessities such as life support, engines, a sealed environment, a hatch or ramp, short range sensors, fuel tanks, short range coms, etc, unless otherwise specified. All other items must be listed, up to and including things like shields and escape pods." So you detected me with those, normal, short range sensors.

As per the ruling the Cloud shouldn't have long range sensors and the storyteller post says there was a conflict between two sensor readings in the Cloud's systems, but as the fighter does not have long range sensors and you times your own spotting of me with each other, it tied in that you both got readings at the same time because of normal sensors. Also as you had attempted to fire at me, and I stated in my post that I was flying in to cut the distance, I think it was. given that we were in combat range.

Oh and, "had a Direct connection to the gods", cute.

The storyteller indicated the Cloud did sense your ship at maximum range. Also, the announcement was made on comms, which my character was in before everything shut off, as such I could be able to react to the announcement before everything cuts off. You can assume the range, but there wasn't anything clarifying how close you were nor the speed you were using where 'shit hit the fan' per say. We have no way of knowing what you intended when you made your post either. You also mentioned that you fired your missiles, then immediately cut your engines off and put it into reverse.

 

[Wit]

The storyteller indicated the Cloud did sense your ship at maximum range. Also, the announcement was made on comms, which my character was in before everything shut off, as such I could be able to react to the announcement before everything cuts off. You can assume the range, but there wasn't anything clarifying how close you were nor the speed you were using where 'shit hit the fan' per say. We have no way of knowing what you intended when you made your post either. You also mentioned that you fired your missiles, then immediately cut your engines off and put it into reverse.

Brianna hadn't had much time to relax. She wasn't planning on leaving her ship, as Ray was just towing her closer to her freighter so they could jointly leave the system together. She kept her eyes on the sensors, knowing that they weren't exactly out of danger yet. That proved to be the case when she noticed the indication that a Sith fighter was on approach. This was doubly confirmed when she overheard Ray over the comms. It looked like the Sith hadn't had enough yet.

Well, your post clearly states you first sense it on the sensors and then hear the warning. Also, keep in mind that the Cloud made an attack on me, and my attack is in a similar timeframe, so you already put us in combat range.

 

[Mad Dog]

Well, your post clearly states you first sense it on the sensors and then hear the warning. Also, keep in mind that the Cloud made an attack on me, and my attack is in a similar timeframe, so you already put us in combat range.

The Cloud firing at you does not specify distance, though the bolts would have been ineffective against your ship at the distance we were at, a person firing in a direction doesn't state how far the target they are firing at is.

For instance, if I were to shoot at the moon, I have made the attack, but my simply shooting in its direction does not change, or state, the distance between me and the moon.

 

[Wit]

The Cloud firing at you does not specify distance, though the bolts would have been ineffective against your ship at the distance we were at, a person firing in a direction doesn't state how far the target they are firing at is.

For instance, if I were to shoot at the moon, I have made the attack, but my simply shooting in its direction does not change, or state, the distance between me and the moon.

The incoming Heavy Laser Cannon fire, from the rear mounted, ventral mounted, and dorsal mounted heavy laser cannon turrets, would make it difficult for the small interceptor to maneuver, and even more difficult for it to gain a straight unimpeded shot on The Cloud without getting hit itself.

It sure looks like you expected to get hit and fired at me to avoid getting hit, while expecting your shots to hit me if I didn't dodge. You set up things to be in combat range in your first post.

 

[Wit]

@Algarus, noticed your auto hit comment in your post.

From my previous post: "So her sudden braking maneuver would keep her well behind the fighter, thereby sending the fighter's attacks flying off aimlessly into open space. If they did somehow fire towards her, she would dip her nose and go into a dive and put all power into her forward thrusters, the sudden dip allowing her to avoid the lasers and fool the missile."

 

[Wit]

@Wayrider could you edit your post a little to clear up your timing, you jump back and forth between different periods of time and I can't follow if you attack before the cloud's failure, or after or somehow make it all happen concurrently.

 

[Wit]

As there was no response and I didn't get the feeling that a compromise was on the table, I have filed a report to resolve this issue. We do have a 48hour window to post and as I can't really do PvP posts from work that cuts down on all of tomorrow for me.

@Mad Dog @Algarus @Wayrider thread is now locked due to the report.

 

[Mad Dog]

@Algarus, noticed your auto hit comment in your post.

From my previous post: "So her sudden braking maneuver would keep her well behind the fighter, thereby sending the fighter's attacks flying off aimlessly into open space. If they did somehow fire towards her, she would dip her nose and go into a dive and put all power into her forward thrusters, the sudden dip allowing her to avoid the lasers and fool the missile."

@Wayrider could you edit your post a little to clear up your timing, you jump back and forth between different periods of time and I can't follow if you attack before the cloud's failure, or after or somehow make it all happen concurrently.

As there was no response and I didn't get the feeling that a compromise was on the table, I have filed a report to resolve this issue. We do have a 48hour window to post and as I can't really do PvP posts from work that cuts down on all of tomorrow for me.

@Mad Dog @Algarus @Wayrider thread is now locked due to the report.

It hasn't even been 24 hours since you posted your questions, I'm sure they're busy. Today is a holiday after all. I mean not for me cause work sucks, but other people probably get this day off, maybe?

 

[Nefieslab]

It hasn't even been 24 hours since you posted your questions, I'm sure they're busy. Today is a holiday after all. I mean not for me cause work sucks, but other people probably get this day off, maybe?

PvP timers don't stop so when clarification is requested it needs to be delivered asap

 

[Loco]

Although you're still free to offer clarification that was asked for. It might be helpful when we get to the ruling.

 

[Phoenix]

Admin Ruling: The missile strikes the Cloud, and without any shielding the ship is immediately destroyed, killing all occupants. The docked fighter barely manages to clear the explosion.

1. The ships are within short range sensor distance as specified here:

"That proved to be the case when she noticed the indication that a Sith fighter was on approach. This was doubly confirmed when she overheard Ray over the comms."​

Clearly, the call confirmed what the sensors already picked up.

2. The ships are within attack range as both sides have attacked one another. The quotes below are clearly intended as attacks, and to attempt to retroactively walk it back isn't a valid argument:

"The incoming Heavy Laser Cannon fire, from the rear mounted, ventral mounted, and dorsal mounted heavy laser cannon turrets, would make it difficult for the small interceptor to maneuver, and even more difficult for it to gain a straight unimpeded shot on The Cloud without getting hit itself."
"The Heavy Laser Cannon mounted on the rear of the ship would give this approaching enemy something to regret as it opened fire, sending enormous bolts of deadly laser fire directly at the Sith ship."​

3. Heavy laser cannons are by definition slow to track targets as seen in the tech rules, and are not going to be able to shoot down missiles. This would only be further exacerbated by the ship's current attempts at rebooting. Relying on shooting missiles down with heavy laser cannons is not a valid defense.

4. Simply stating your enemy is too far away when there is evidence to the contrary is not a valid defense either.

@Wit @Mad Dog @Algarus @Nefieslab

 

[Wit]

@Algarus @Wayrider could you please edit your posts to reflect the same? Your posts are now off timing wise. I believe you have 24 hours.

 

[Nefieslab]

When you can please @Algarus @Wayrider - I can't reply when literally 80% of your posts are about things that did not happen the way you say they did

 

[Nefieslab]

Officially asking for a 24 hour extension - if/when edits are made, the timer will be so short for my post and will fall during the rare hours I do actually sleep.

@Phoenix @GABA @Loco

 

[GABA]

Officially asking for a 24 hour extension - if/when edits are made, the timer will be so short for my post and will fall during the rare hours I do actually sleep.

@Phoenix @GABA @Loco

Extension granted.

 

[Wayrider]

First I’m just going to put everything in here, I don’t use this type of communication so if I do something wrong I apologize in advance.

First off if the admin @Phoenix is correct then the Cloud never has any failures since it was the sensors that supposedly caused the failure of its systems by reading an inbound ship farther than its systems were supposed to be able to reach. Not short range sensors.

As for my posts
In the first post I clearly stated that I picked up the Sith ship @Wit on my sensors and there is nothing wrong with mine or Briannas long range or short range. I then immediately dropped in behind it not making any additional attempts at stealth and allowing the Sith ship a chance to divert and run.

Then the Sith ship continues its run on an apparently fully functioning ship that is firing at it from long range. Yet the pilot somehow magically knows that all its systems are malfunctioning and makes all the correct decisions to take advantage of those malfunctions All the while having a fighter that is its performance equivalent on its tail.

As was explained in my first post I was flying high cover. For purely defensive purposes, and had placed the first Sith fighter at a disadvantage, I further gave it an easy out by simply breaking off.

In My second post I clearly acknowledge that the second Sith ship @Nefieslab and also why it cannot be any closer than it is. I further explain that I do not allow the first ship to reach weapons range of my companions, before I engage.

I would point out that you laid out the positions all I did was identify the distances based upon reasonable parameters.

I also will point out that if you had all that time to do everything you wanted to accomplish both Brianna and I have equal time to do what we have done to prevent you. I feel you are having difficulty following my timeline because you have made yours overly long and complicated by putting a bunch of maybes and if this then that and not allowing others to respond within the amount of time you used, When our actions will or would have caused significant activity that you have blown by.

I would ask @Phoenix, @GABA and @ Loco to please review the content since you clearly ignored both mine and Algarus’s presence.

Wayrider

 

[Wit]

First I’m just going to put everything in here, I don’t use this type of communication so if I do something wrong I apologize in advance.

First off if the admin @Phoenix is correct then the Cloud never has any failures since it was the sensors that supposedly caused the failure of its systems by reading an inbound ship farther than its systems were supposed to be able to reach. Not short range sensors.

Algarus locked in the identification being from the short range sensors, if you're gonna go against a ruling and make incorrect assumptions then that doesn't magically fix earlier mistakes. The ship was sensed at normal range, Mad Dog put us in combat range, and Algarus locked in the timing. The ship malfunctioned and blew up, that's all locked in now.

I would ask @Phoenix, @GABA and @ Loco to please review the content since you clearly ignored both mine and Algarus’s presence.

Wayrider

Rulings are final and the PvP mods took everything you and Algarus wrote into consideration. You have a little over 20 minutes to edit or your posts are void.

As for my posts
In the first post I clearly stated that I picked up the Sith ship @Wit on my sensors and there is nothing wrong with mine or Briannas long range or short range. I then immediately dropped in behind it not making any additional attempts at stealth and allowing the Sith ship a chance to divert and run.

Then the Sith ship continues its run on an apparently fully functioning ship that is firing at it from long range. Yet the pilot somehow magically knows that all its systems are malfunctioning and makes all the correct decisions to take advantage of those malfunctions All the while having a fighter that is its performance equivalent on its tail.

As was explained in my first post I was flying high cover. For purely defensive purposes, and had placed the first Sith fighter at a disadvantage, I further gave it an easy out by simply breaking off.

In My second post I clearly acknowledge that the second Sith ship @Nefieslab and also why it cannot be any closer than it is. I further explain that I do not allow the first ship to reach weapons range of my companions, before I engage.

I would point out that you laid out the positions all I did was identify the distances based upon reasonable parameters.

I also will point out that if you had all that time to do everything you wanted to accomplish both Brianna and I have equal time to do what we have done to prevent you. I feel you are having difficulty following my timeline because you have made yours overly long and complicated by putting a bunch of maybes and if this then that and not allowing others to respond within the amount of time you used, When our actions will or would have caused significant activity that you have blown by.

As for your post, you basically jumped back in time as you're taking action against stuff I did in the previous round, you joined a round onto the combat so you're obviously gonna have to play catch up. In your first post, when you saw me fly by and shut down systems, I made my attack run, which killed Mad Dog, now you can't go back in time in this round to say that you would hit me before I even had a chance to attack as I already made my attack run in the previous post, when you were posting your OP. So your post doesn't just need to be updated to reflect the report ruling, it also needs to be fixed timing wise.

 

[Wayrider]

No I shut down my sensors and when you passed I immediately fell in behind you as you passed it is not my timing that is off.

 

[Wit]

No I shut down my sensors and when you passed I immediately fell in behind you as you passed it is not my timing that is off.

Honestly, I'm not going to argue over this. You had 24 hours to make edit, that time is passed. As of 7 minutes ago your posts are void.

 

[Nefieslab]

Just to let you all know;

I've raised the issue of timing as a report @Wit & @Wayrider as neither of you is backing down on the issue.

Personally I agree with Wit and think that you're trying to use time travel here Wayrider but you've stated before that you disagree and believe yourself to be in the right - report was raised to get this settled as no compromise seems to be on the table