The Rebel Faction

Does that somehow make the aforementioned discrepancy come together..? I showed you yours; where's mine?

You say that it is not Griff's responsibility to inform anyone that the roleplay is on hold. Yet you also say that I should not be have been able to post, because the RP was on hold.

And..

Once the complaint was issued, the responsibility of managing the roleplay fell into the hands of the Staff; enforcing [or beginning] a suspension was not Griff's duty.
He is not the one to blame, and therefore doesn't stand to be punished, which would be equally unreasonable.

I can't state it much more clearly than that. When Griff issued his complaint, it became the Staff's responsibility to suspend the thread until a ruling was made. The thread was not suspended, however, which is how you came to post without being aware of Griff's actions. However it is unreasonable to punish Griff with a post that shouldn't have existed as a result of the negligence that was not his.

Never did I claim that the post was actually on hold.


That was all in my first post, Drayson...

Jesus H. Christ!


Look peeps,

Drayson, the thread is considered on hold due to a damage assessment from your previous post (not the last one).

This is why Griff did not post within the 72 hour timeline.

Therefore, the staff will make an assessment regarding your second to the last post, then Griff will post, and then you will be able to put your last post back in (though probably edited).



Now, for everyone:

If you want a staff decision, letting them know on AIM is fine, but back them up in the rp's OOC thread so ALL are aware of what is going on. Also, follow it up with the "Staff Attention Needed" thread because the staffer you talk to on AIM is subject to RL issues which may see your concerns lost in the shuffle and the rest of the staff may not know something needs attention. The staff cannot pick up each other's slack if we do not know there is slack.

In other words, help us help you.


Drayson, you incur no blame for posting since you did not know. The staff incurs some fault in that and we apologize.

Drayson: Personally, I do not like capital ships destroyed in 1 post (if they are over 1,000 meters at least).

Heavily damaged, fine... depending on what is being thrown at them and where.


Unless the firepower is overwhelming (ie: ESD vs. 1 ISD ..or something like that).

But you have 1 sphere per capital ship it seems.


But that all may be beside the point because, unless I am mistaken (and I could be) the Torp Sphere fires things "launched". And as such, I do not see where they were "loaded".

You make mention of Mezzer (I believe that's the name) loading missiles and that the rest of the fleet followed suit, but in my opinion, that would be the rest of the fleet that was engaged at the time the order was given.

The Torp Spheres had yet to show themselves.

Now in the smaller ships, where you have 12 missiles on a ship, when firing missiles: 1 post to load is not really necessary but I am under the impression that Torp spheres fire ..hundreds of them? Or at least quite a bit more than that.

If so, a loading post would be required.



So, either the missiles on the torps were not loaded and so didn't fire meaning the damage is much less than shown.

Or if they did fire. And if so, do not destroy previously unhit capitals totally in one post. Heavy damage. Fine (depending on their size.)

Now, if the Majestics are 500 meters, then... I can see where they would be destroyed but I am going on the assumption that Majestics are at least close in size or defense power of an ISD.

It's late and I am not really sure.

So long as it takes 2 posts per volley, you can interchange almost anything for the 'loading' post. Acquiring target, obtaining targeting lock, etc.

Just so it takes 2 posts.

I beleive a loading post is unnecessary for the first firing, simply because no sane commander would enter battle with his torp tubes empty for the exact reason that otherwise he'd have to load them before firing.