sloshed works. I like Sloshed. Also Merry. And completely s**t faced.

Yeah, I was wondering... lol .A good phrase for being drunk;

"I was totally car parked last night!"

Um, no, if you are posh enough you can practically use any word to mean drunk (Trollied, plastered, gazebo'd, etc.) but tossed is not one of them, it tends to imply something a bit ruder, lol.

I thought tossed was UK lingo for being drunk. Is that not the case?

And sadly, I will be in SoCal this weekend, so I doubt it. Oh well.

in germany only few parts of the doc comes out.

some in the late 80's or 90's and on 2008 2 seesons that all. very bad that in germany the doc is far away with his tardis

I've named several Trills as both a player and fanfic writer. Here they are. I came up with most of them after reading names of Trills on Memory Alpha.

1. Zwen Amana, a captain in Starfleet Intelligence, introduced in an episode of "ST: Pandora" ("Passing").
2. Captain Zex (no first name), a Trill I've been using in a Foundry mission I'm working on.

These next two shouldn't be taken that seriously, as aspects of their names were adapted from characters in Champions Online. I tried to make them more Trill-like, but feel free to not include these in the Institute's database.

3. Lt. Commander War'en Lok, my Engineering BO. However, following his joining, his name is now War'en Sadda.

4. Rear Admiral Izen Sadda, one of the former heads of Starfleet's Corps of Engineers and last host of the Sadda symbiote. Introduced in ST:Pandora "Passing".

Super-tossed? I'm not gonna ask, lol.

If you can't make the Cheesy Pop events fo the UK times, Spark is looking for someone who can run it for US times, so fingers crossed. Also we are having the Spring Social this Sunday, so you can come and listen to some music on Vent then?

I'm suddenly very sad that these happen at 1 PM my time. Zep, promise me you'll be super-tossed!

Oh, god, you're not going to sing, are you?

Due to Sparks connection issues, we have agreed that I will be taking over as DJ for this week's Cheesy Pop event, and this week only. So I'll see everyone there tomorrow!

Updated with the events for May :) Remember to subscribe to this thread to keep up-to-date with the events

Episode 256 - The Next Generation - "Second Chances" - 05/24/1993



Parts 2-5:

Found from the above link in the related videos section

Riker encounters a duplicate of himself created by a transporter malfunction stranded on a planet. "Thomas" vies for Deanna's affections.

Enjoy!

Title: The Spirits of Ramok Nor
Author: @alimac30
Faction: Federation
Level Requirement: Any level

Author Notes:
I've just published this, my very first Foundry mission. Please give it a play and let me know what you think.

Any and all feedback very, very welcome.

Thanks!

Ali
x

PS. At this early stage, you may need to be a Reviewer in order to find the misson in the "Community Authored" tab. Once a few people have played it, everyone should be able to see it.


Mission summary: Spirits are haunting an old Cardassian-built medical facility on Bajor. The terrified patients and staff fear the apparitions are the tormented souls of Bajorans tortured and killed at the facility during the Occupation. With the pain of Cardassian atrocities still raw after 50 years, Kai Kira has asked Starfleet to investigate...

[Author's notes: This is NOT a Devidian mission. Intended to be single-player; takes around an hour. It's more of an investigation than a shoot-'em-up; there are some baddies to shoot, but the focus is on the investigation.]

With my web down, it looks like I will have to cancel this event.

Appologies all

We will take the lot! lol.

Well anything you can spare now and in future. We are not only trying to get enough samples to reopen the store, we also need to ensure we have a sustainable supply so we don't have to spend ridiculously large amounts of money to buy from the exchange anymore, hehe.

All donations are gratefully recieved, so Thank You for your help!

250 would be nice, but I was settle for 100. We currently have about 20 Chronometric and Vertiron, 50 Antithoron and 90 Metreon. So still a ways to go.

Hello, How many:

- Chronometric Particle Traces
- Vertiron Particle Traces
- Metreon Particle Traces
- Antithoron Particle Traces

do you need to get the store back to normal operations? Not just the minimum number, but the number of traces that would give the store sufficient "operating capitol"? I can probably provide quite a few, just need a goal to reach for.

Thanks!

Regulus@Marcus_Jellico

I'm not sure if this will be helpful or not, but.... thought I'd spout off about some theories.

Based on my extensive PHP background (heh), it sounds like a multi-threading problem. I'm not a PHP expert, but I do know Java and general programming quite well (day job is working with Java on corporate finance systems.)

What's being described (sometimes it's 3, sometimes 8, sometimes 10) can be caused by multiple threads processing the mail queue. The 'simple' solution there is to make sure only one 'daemon' or thread processes the queue.

Multiple submits would queue up multiple emails, but I find users are generally unwilling to admit they've clicked the button 3, 8 or 10 times (which doesn't mean they didn't). Javascript on the submit button, or session tokens can be used to prevent multi-submits.

It's also possible there's a bad database join. Making sh*t up, let's say the user table that contains the email has multiple records (one for each edit you make to your profile). Only one of those records has the 'currentProfile' column set to true, which indicates which record is the current one. The other part of the system that queues up emails to people? It just records your username. The other code that emails then must join to the user table to retrieve your email address, but forgets about the 'currentProfile' column. So your email gets pulled 8 times (if you've made 7 edits to your profile). evidence for this: if you (you reading this) consistently get 'x' emails... make a simple edit to your profile and see if your next email is 'x+1'.

Finally, it's also possible that the emails are being re-sent, through some faulty re-try logic. Evidence for this: view the full headers... bad joins would show you nearly identical timestamps. If they're spread out a bit, it's some process that is re-sending because it thinks the first 'x' tries didn't work.

yeah ive been getting them for along time. one time I had like 8 duplicates :lol:

@flounder all orders are done :) I posted that before I said they were done. Thanks for all your help! :D