Home Creators Posts Import Register Favorites Logout

Content

Hi,

here is the Public Release of Space Journey X, Version 2.20 (V220_022). It contains quite a number of fixes compared to V220_021 so I recommend all Patrons and Members to grab it and update!

Download Links and walkthrough can be found in the updated Release Notes Post.Primer for new side quests:

Underverse Relic: Once you have completed the Shadows uof the Underverse Quest you may run into an interesting Relic in Drengar Space

Tris Milking: Run into Moira after you have gained the achievements Dairy Queen with Nimhe and Moira

Turbolift Encounters: Find out what your Crew is doing when not in their locations... Check the new Turbolift ;) 

For hint to other content see gallery or quest log hintsEnjoy

y.v.

Files

Comments

PepperMint

I wanted to take a moment to say how much I truly admire Space Journey X and the incredible universe you’ve created. The depth and creativity of your work are inspiring, and I especially find the Krell world fascinating. Your project has motivated me to begin developing my own space-themed trainer game in which a race of lizard-like beings holds positions of power. I wanted to ask if it would be permissible for my project to be set in the same universe as Space Journey X, specifically incorporating the Krell race. I would like to clarify that I would not be using any of your existing characters, storylines, or other protected material — only the concept of the Krell race itself as inspiration. If this is not possible, I completely understand and will move forward with creating an original race instead. I simply wanted to reach out and ask directly, out of respect for your work. Thank you for your time and for creating such a masterpiece.

y.v.

i'm glad you like the game. Great that you also want to go into developing your own stories. I have no problem if you use some of the lore which is present in space journey X If you are using DAZ for the character renders: the krell race is the model bullwarg :)

AndrasV

I must confess that it has been somewhat confusing that the release candidate and public release versions seem to share the same version number (unless I missed something terribly - V220_022) ... It came to foreground again, when You posted last minute patch (I assume that goes for the public release ...) I would like to raise (most likely unnecessary and redunant) suggestion about using distinguished version numbering - bijective mapping.... Sorry for the trouble - feel free to ignore this comment!