Issue #8 Deadline: June 30th…

Good Morning, All,

This is just a quick note to let everyone know that the deadline for submissions for Issue #8 is Saturday, June 30th, 2007. I already have a number of interesting submissions, but I’m always open to more. We could easily use a few patron encounters, starship articles, adventures, amber zones, how-to articles and the like. Art submissions would also be very welcome.

Thank you all for your continued support and interest,
Jason “Flynn” Kemp

6 Responses to “Issue #8 Deadline: June 30th…”

  1. Commander Drax Says:

    Hi I am presently working on Part 2 of ‘The Lorimar Slot’, this originally intended to be a 2 part adventure, although with the story arc developing as it is, it will most likely be a 5 or 6 part campaign. No worries though, after such a long time being out of the zone, its good to be writing Traveller again. I’ve had some serious problems these last twelve months, hence the delays…

  2. Flynn Says:

    Commander,

    It will be good to see the next segment, then, as I have had a few emails requesting this piece. :) I’m definitely looking forward to it.

    With Regards,
    Flynn

  3. Commander Drax Says:

    Well it’s not going to be what you expect, hopefully it will be better, the writing is tricky, got some complex ideas ging around.

  4. Commander Drax Says:

    i think i will need an extension to the deadline of one or two days, I’m up to 11, 000 words at present (including NPC’s and Ships etc). Got a very complex story arc going.

  5. Flynn Says:

    I’m going to start putting the zine together. If you can get it to me in time, I’ll add it to the contents. A day or two shouldn’t be a problem, but a few weeks may mean that it slips into the next issue. Either way, I look forward to reading it, as do our readers, I’m sure. :)

  6. Commander Drax Says:

    I think wednesday (4th July & My Birthday) should do it, please hang on for it as I would really like to see it in the next issue, as I would like to place the sequel to it in the following issue.

Leave a Reply