Actually we kind of did handle the GC/BDE thing ic (the whole propoganda thread, TNO backing GC, that whole deal). Bu I admit that it could have blown up a lot bigger. And in an upcoming thread the repercussions against Jan personally will be shown (ie. lack of the Minister of Defence job.) But that's all in the future.
Well, if it makes everyone happy, would we restart the thread? After all, I always save my RPs to word document before I post them. And Drayson just copied and pasted his original post to the Bimmissari thread.
Jan: What I meant is, the situation was posted IC as having taken place. It was then revoked and everyone basically said "it never happened". Granted, though, the threads were never deleted, so the situation is not exactly the same. But it still offers us some insight into how similar situations have been handled in the past, and that was without OOC 'penalties'.
I question the purpose of a penalty for making a mistake? Vance makes it clear he feels penalties are in order irregardless of the thread being deleted... why?
I also question the mindset of those who say that IC history is set in stone once written, which is simply not the case. Are unfinished threads always considered canon? No. Have threads been cancelled in the past? Yes.
So because something is written does not immediatly make it canon. The thread was, as I've said, a clear intention to attack the GC. I made a mistake, yeah. But I also moved to resolve that mistake in the easiest and most sensible (imo) way possible.
Sure, we could write out the entire TNO/BDE situation, but why? This is a storyline enviornment, and a game, and all of us have real life to take into account. It was an error on my part in that I did not research my target properly, yes. But when did TRF come to expect absolute perfection from its members?
I'm not arguing that if the community should feel that the orginal thread should stand then penalties may be in order. What I am arguing is that we should not be penalized for making a mistake and moving to correct it.
Cracker's being a member of TNO and BDE complicates things, as haas been said, but I've yet to see a proposal that would answer the question of "did BDE agree to end the thread". And as Cracker is the only active BDE rper, that leaves us in something of a jam.
I think to say the only reason Kraken made the decision he did is because he is a TNO member is unfair to him. As the only member of a faction, would you desire to start a war with another group? Especially when you are not (strictly speaking) the owner of that faction?
To answer some other points:
But as I've said, the ships are well outside of sensor range. And even then they are brand new ships, no one would know that they are Imperial. I would imagine in fact that the first suspision would go to the Union, because they are known for sneak attacks and the like. It doesn't make tactical sense for the Empire to launch a secret attack on BDE, if TNO wanted to start a war with BDE they would do so with an invasion on their terms -> that would be the view of the BDE leaders, imo.
There are dozens of other groups that might attack BDE in this manner, too. Disgruntled spice miners on the moons of Naboo, for example. Or pirates, Tholatin partiots, etc.
The OOC groups are not the only suspects.
Only factions that are involved matter, and the thread only involves TNO and BDE. They agreed. The GC does not feel this thread involved them because the name of the planet was wrong, so why should I then check with them and see if they're okay with it? If the IC thread were to be RPed out, then the GC would not be involved. So it is not a matter of "expecting" other factions to be okay with it, it is a matter of other involved factions being okay with it. Which is their right.
Im not sure wtf is happening all I can do is say that the Coalition/BDE (((inster target government here))) would not detect the Shroud if it is in sensor range - that is the point of the shroud.
I think - Ive never used them. Any questions on the capabilities of the Astrus, send them my way. AND BTW - byt this time, they have dropped the Astrus designation and are renamed Imperial-class Star Destroyers Mark V
Well Demos, for me I don't really care to see the thread continue. Yes, it would lead to some interesting RP, but still. It was an honest mistake. But just like how the guy hitting a grandma walking the street while he's drunk is an honest mistake, it doesn't mean he gets off the hook.
I know. Bad example. Just bear with me. (I'm terrible at examples)
It's just so that you don't do something like this again, and give you some form of punishment as an example to all to pay freaking attention and when they start and plot takeovers.
[subliminal] Give Irtar Dantooine. Give Irtar Dantooine.[/subliminal] ((J/K ;) ))
But I feel just drop down the fleet a bit or taking away their little bit of surprise if a fair trade off.
Now the question is, how to work losing the element of suprise into the thread. This is a one-time thing, so obviously some mistake must occur. A likely course of action is some form of sabotage or spy in the Imperial fleet manages to slice the location and make-up of all the ships and send it to the Coalition Fleet. Like a virus program, aka, what Gara Petothel did to Warlord Zsinj's Fleet Group 3 at the battle of Selaggis Six.
Oh, and a couple of other points. I not only have characters in BDE, and TNO, but also GC and TSO. So this biased character bullshit isn't going to cut the caek. The other thing is, that there was another thread that Demos let die, called Opening Doors to the future. Ahnk, Dray, me, Dolash, and GenGre were all involved in. Demos let that thread die too, also because of a lack of time to post. But GC, being in a dis-advantaged situation, did not post a single word of outcry or betrayal. It's obvious the only reason they care about this thread is because it would affect relations between BDE and TNO. So, in regards to all of you GC people, just fuck off.
I would vote that both threads be deleted = eye for an eye as it were. Mistake one made the negation of Action II - restarting the other seems in order.
