science console

12/50 caps of Our Lady of Cheekbones: Beverly Crusher


“My future dream is to be a scientist. I like experimenting, too. I bought a microscope. I looked at my hand and it was gross looking. I looked at a down feather and I saw a down feather. The goldfish was slippery. I realized the scales make him difficult to hold.”

– Heechul’s diary entry, 1992 (age 8)

Imagine Jim gets caught up in memories of Spock

Not even far away memories, but flashes from the previous night. The press of Spock’s lips into the curve just below his collarbone, the hot tongue darting against his own, the brush of Spock’s mind. Waking up with his head curled into Spock’s chest, getting to see his immaculate first officer’s hair shocked up in all directions around the pillow, watching Spock blink slowly awake, kissing up his neck and-

And he has to shake himself out of the memories, because he is on the bridge and has been staring at his pad with a stupid smile pushing into his cheeks for over five minutes. He hadn’t comprehended a single word of the mission report he was reading after he caught sight of Spock’s name printed at the top. 

So he clears his throat, bends his legs into a cross and refocus. But of course, he flicks a glance to the science console and catches Spock’s eye. His bondmate lifts an eyebrow, and oh isn’t that endearing, he did that last night right after he tugged off Jim’s-

And the whole process starts anew. 

But jim is multilingual and he likes saying really cutesy stuff to spock in public in different languages and the first time uhura hears she almost swallows her tongue and then jim learns some vulcan and one day he goes up to spock and drags two fingers up spock’s and whispers “t’hy’la”

and spock accidentally breaks off the edge of his science station console because he’s jUST SO TURNED ON


TumblrCards Update v0.0.2

Hi all,

GitHub here.

So I think to help promote the game and keep up interest, I will write a blog post with each release update! For those of you that don’t know right now releases are structured as follows:

For something to be considered for merging in to the master branch it must be submitted as a Pull Request to the development branch first. All Pull Requests will be given at least 24 hours before being merged in to the development branch. Pull requests may take longer to be merged if more needs to change. On every Monday the development branch will have a pull request made (assuming development is ahead of master) to be merged in to the master repository. This pull request will sit for one week to be reviewed until it is merged in on Sunday. The weekly pull request may be delayed if more changes need to be made.

Now, why is it v0.0.2?

Normally release numbers follow the format Major.Minor.Patch, and eventually we will follow this. However the game itself is not actually playable. So until we have a working alpha version, I will be increment the patch number for each development merge. Master currently sits at v0.0.1, and the current pull request will make it v0.0.2. Once we have a working single player game (no matter how awful the alpha version starts) I will set the release version to v0.1.0.

So whats new?

The biggest thing so far is the Console API I have created. What this aims to do is give us a simple set of tools to handle console output for drawing. The Console API will mainly be used for the single and multiplayer games, as well as the deck editor. v0.0.2 will contain only 2 pieces (Console and ImageMap) of this API, and it will expand as development continues.

Besides that, this update really just contains a lot of error message fixes and other minor tweaks. For a full list of changes in this update check out the pull request here!

How can I help?

Well there’s a TON we still need help with and could always use new people. The biggest need is for programmers. The game is written in C++, however it’s totally ok if you have a negative amount of experience with C++. This is a learning experience for many of us, so use this as an opportunity to learn a new programming language!

For details on contributing check out this page!

We also have a Slack chat. If you would like to stay in the loop and get to know your fellow Comp Sci blogs shoot me a message with your email so I can get you an Invite!