Ellri

Star Wars: Coruscant Sacked: Aftermath

We could probably help you with one.
use this doc:
https://docs.google.com/document/d/1sAKwSN9A-AVjPCL9J0KrpEnEEK_CdaXTkjulXMCCWWU/edit

Stargate - H.M.S Tempest

~| Some time earlier, on the Bridge |~

Just after the console exploded around the weapons officer, Astridh heard her own console warning of severe damage to hull, this time in the primary mess hall. She rushed over to the console, then started seeing what she could do about it. However, before she could issue any warning, the damaged section broke, venting atmosphere. She knew then that every second counted. Rapidly using the console, Astridh fired up the beam array, using the sensors to lock onto anything and everything thrown out through the breech. She had no idea if it would be quickly enough to save everything, but she had to try. Just before triggering the beam array, she remembered to expand it to anyone still within the mess hall too.

Astridh sent them all to one of the larger storage rooms near the primary medical bay, hoping she had saved them all. Thankfully the bulkhead doors to the mess hall had sealed themselves up automatically, so nothing else was vented. She then proceeded to close bulkheads near all potentially damaged sections. So long as pressure was not radically different on each side, access cards would still open them, but the doors would close afterwards. She had no idea who had programmed that safety feature, but she was glad it had been programmed in. If she could do anything about it, she would ensure that no more died this day.

“Did it work?” she murmured, even as she queried the computer about it. She had, after all, never before used asgard beaming outside calm, test situations. Eventually, the computer responded that there had been some damage to at least one transported person. Somehow, that particular beam array had been malfunctioning, resulting in some error in rematerialization of one of those who had been thrown out of the ship by the explosive decompression. The computer confirmed that the issue was only present in one patient. Astridh shut that beam array down for the sake of safety and noted in the system that it was faulty. She did not know anything about fixing such, so she paid it no more mind.

The final thing she did was to order a medical team to go to the particular storage chamber. She did not know if it would help, but it never hurt to try. Of course, that was the time the captain ordered the bridge evacuated. Looking over the room, Eydis saw that it was very sensible. Half the consoles were damaged or dead. Wounded crewmembers were everywhere. This was no place to control a starship. She initialized the shutdown command on her console and on the other bridge consoles, then followed the others to the auxiliary control room.

~| Auxiliary control room |~

The Auxiliary control room resembled the bridge in many ways, but it was smaller, and more centered around the Captain’s chair. Which for the moment was occupied by the Executive officer. They had brought the ship back online, slowly taking control of each system, isolating any damaged system so it could be repaired. As of yet, they did not have full functionality, but much of the ship was now back under control. To think they had been ready to go out exploring, when a mere debris field could cause such damage. It was strange. The Tempest’s design was clearly more advanced than its predecessors, but it was clearly not flawless. Much could be improved upon.

“Lt. Commander Thomas. Shield emitters are now coming back online. Forward, top and rear shields fully operational, bottom shields are at 13%, port shields at 56% and starboard shields at 17%. Would it be too forward to suggest installing redundancy in the shield emitters if we get the chance? I do not relish the idea of taking this vessel into combat situations if the shields are this fragile. My tactical options are severely limited by it.” Astridh’s words were spoken in her familiar irish accent and style, with just a hint of Eydis’ coldly impersonal manner.

The Insidious Night

Indeed.

The Insidious Night

That is a good reason to postpone a post, Elsa.

The Insidious Night

Yes, we can see the rotting wooden core beneath the thin layer of rust!

Nah, just joking... Post looked good to us. We don't understand your character fully yet, so we can't judge beyond that. Yet.

no rush - a question about rules

so long as the adult-level content (descriptive sex & such) ain't visible to just anybody, it doesn't really matter what you put in public. There are more than a few IntCks that go for PMs/IM/Google docs/etc. rather than publicly visible topics.

Telling someone you're into smut ain't really something anyone (except prudish, overly religious types) can complain about. This guild is paid for in part by AdSense advertisements, which are reliant upon the site following some certain rules. Mentioning you like something is not something that is punished for (except the obvious ones, like child porn).

Master Request List for bbcodes (or MCodes)

The problem we see with uploading sound files is that it could be used by nefarious people overload the server. Besides, unless the music you want is really obscure, there's probably some version that ain't extremely far off from your use, or at least is obvious in being different.

Adsense

One recommendation: For those of you who enjoy writing up cybersex or describing rape in detail and so forth. Do it in PMs. Google's adsense nerds do not browse those. The new PM system is particularly suited to having private RPs now, being thread-based and all.

Or use external tools like Google docs, if you feel that is more comforting.

The Insidious Night

throat-slitting is just the way to go about it.

Banner Ads (Yay?)

We disabled the adblocker we use, they appeared for us too. Thus it ain't just for you. Considering how the site is being built, we do believe they're mahz choice, but cannot say for sure.