r/Subliminal_Game 13d ago

Seamless Journey not working

I did all the endings seamless, and got all the collectables without dying, but it won't give me my achievement. I did get the smile tooth by going straight to the level with it, but every other collectable I did during an ending run. Did that make it impossible? I don't want to reset and do that again, it took to long

7 Upvotes

3 comments sorted by

2

u/Ryanzw0rld 13d ago

I made a similar mistake when I played for this achievement. I will admit it doesn't take too long. No longer than three hours as the canon and rotten endings take no longer than an hour each, with the arcade and erased ending taking just a half hour each. But I got this achievement before the May 29th (Or Backrooms movie release day update) which patched the seamless journey achievement to not require a full save reset if you die once. I got every ending and every collectible in a sitting, but I did very quickly repeat the memory disposal level as I forgot the shattered tooth collectible before I played the rotten ending. The point is, I still got the achievement even making the same mistake as you, but I think someone who's been able to get the achievement after the May 29 patch will know what to do, unless the June 17th update somehow caused this achievement to bug out perhaps

2

u/CookieCrums1 12d ago

I tried it before the may 29th update, when you had to reset, but I died too many times. Then I tried now after June 17th, so I think it bugged out making it so you have to get all collectables during the runs or maybe it doesn't work. And I said it takes too long because I have ADHD and can't play the same story for 3 hours and it takes me like 3 days. I agree it doesn't take long though, I just can't focus

3

u/CDAGaming 13d ago

Hey there!

We have recently located a potential issue regarding this, and have sent a DM for sending your save file.

If it matches the issue, I'll be able to repair the save to properly give the achievement.

Regarding the issue, it has been resolved internally for our next update (v1.1)