I think this is what i’m Thinking of
But you already know this, sorry it’s beyond me lol 
2 Likes
One thing that stands out to me, making it less likely to be NMS coordinates, is the fact there is a total of 17 images. Each contains a set of two hex characters. If used as coordinates, there is a load of possibilities, even though somewhat reduced due to limitations in parts of a full set of coordinates. I am basically trying to say that there should be some logical conclusion to make before trying any possible coordinates. I would prefer to focus on finding some logic first before blindly trying, because you’ll be flying around in space for a while, as there are many sets of coords to be made from those hex characters used for the images.
4 Likes
It was months ago… Lol, i just forgot! Been busy… Need also to find my CSD id.
I’ll have a personnal ARG made by my old self finding it 
2 Likes
stop! but may be 1.5 is fifth day of january?
2 Likes
Perhaps…
Consider that Hello Games is based in the UK, so if 1.5 is indeed a date, to them it would be the 1 May.
4 Likes
Has anyone tried that? I’m not able to try it yet in my game. I’m out and about.
1 Like
Found this little tidbit around Software versioning interesting, specifically when companies like Apple have skipped to a .5 of a version.
It seems in some cases, the .5 could carry more significance than the others within the same version.
2 Likes
Sadly l can’t test this, I’ve been ignoring the atlas quest and glyph collecting in favor of base customization and planet hopping. Trying to get through it now, but I’m not gonna make it in time unification day.
1 Like
Unfortunately I’m not in Euclid
1 Like
I’m in Euclid…what do you want to test?
1 Like
You can! Test in creative mode. You have all the glyphs, and you can see other mode’s comm balls. We use this at the Amino Hub all the time!
1 Like
tried both. nothing interesting
1 Like
I think we get an email today, not sure why.
(atleast i hope so, then i have something to do with my life)
2 Likes
Everything they do always has some little meaning
1 Like
This code returns atlas error and throws to different planets each time I reprogram a portal.
2 Likes
excited to see this is a go again.
1 Like
Software versioning is an entirely arbitrary business. There’s different standards used by different companies, because versioning is inherently linked to what your company needs from a versioning system. Choosing the right versioning system can be the difference between your employees knowing what’s what and utter chaos. So don’t attempt to read to much into software versions, unless you consider the specific circumstances and organisational challenges of a company, their versioning system might not even make logical sense to you.
That said, HG has so far stuck with something that bears a loose resemblance to semantic versioning, which makes sense considering their iterative approach to developing the game.
Semantic versioning was developed for developers, not for customers. It consists of three groups of digits, like X.Y.Z, where any change to Z indicates a fix or other modification that does not affect the external API, Y is a change to the API that might or might not break backwards compatibility, and X denotes a major release that will not be compatible with the old API. In other words, anybody using the software in his own programs can immediately see that they can just pull the new version without changing anything if Z changes, they know they might have to make some adjustments to their own code if Y changes, and will probably be faced with major rewrites if X changes, so much so that they might decide just not to update and continue using the older versions.
None of this is of interest to the customer. None of it was designed for the customer. You can also see that the versions are only loosely connected to actual progress. Major bugfixes and optimisations could only increment Z, while the addition of wrapper functions that don’t do anything more than make the API more convenient to code for would increase Y, without actually adding anything new or better in a purely functional way.
In case of HG, some of these considerations apply, some don’t. They kicked out Z entirely, because they’re mostly interested in tracking released builds, and the current subversioning is entirely adequate for that.
But it is entirely possible that they came to a point in development where they broke backward compatibility between the core and some systems. Especially since it can be savely assumed that they’re working on multiplayer, which I can’t quite imagine being possible (or at least clean) without some rewrites pretty deep down. At this point it would become essential to increment the version to prevent internal misunderstandings. And since this basically consists of a breaking API change, 1.4 is the obvious and clear way to go. Everybody now knows that this beast is significantly different from 1.3x. But it’s certainly not ready to be released, what with all the code waiting to be updated to actually work with this new core.
So they go through 1.4x’s for a while, and increment the version again when they reach release.
This is one possible scenario, there are others. The main takeaway here should really be: Don’t read much into version numbers. They’re mostly for the developers, not for you.
4 Likes
Maybe they’re taking the winamp approach, and skipping a number because the new winamp is JUST THAT GHOOD!
Does anyone here even remember what a winamp was?
I sure don’t but my damn it really kicked the llamas hump or ass or something I think? I dunno, it was better than WMP and quick to download on 56k dial up… So maybe NMS 1.5 will have more llamas and dialup tones?! Def an homage… I think I’ve run this bit through its course long ago so I’ll stop.
3 Likes
Entirely possible.
Does anyone here even remember what a winamp was?
Yes. Yes, I do. It was that thing that got killed of by VLC 
3 Likes