Terminal ESC
@Extered Aug 15, 2024 @ 6:41am
Impossible to make DMS379 do its job?
[Note to all the Community Hub viewers: this is no longer an issue, and the text below contains spoilers that are marked as such, but for some reason are still shown on the Community Hub. I have updated the wording to be less spoilery, but it still might give you some ideas you probably want to get on your own. You have been warned, proceed with caution]

I was stuck with DMS379 for quite a while because it overwrites a particular file with the one from a particular source . Given that after some careful .dll IR patching to alter the logic relevant to that particular file handling I got the achievement that suggests altering said file was the intended way, I wonder what should have I done to prevent it from copying the file from the external media and solve this particular puzzle?

I will not provide the command log as I botched three playthroughs trying to work this one out, but I tried:

  • Looking around to check whether I missed some other interactable objects (couldn't find anything obvious except for the unobtainable media in the validation section )
  • Towing the broken DMS around
  • Disassembling the broken DMS (that docked on my first playthrough on 1.0.9, but not on 1.0.10 somehow)
  • Literally every actuator command to the broken DMS
  • Literally every actuator command to the DMS379 with no success (due to debris)
  • Messing around with the networks/forwarding (with no success)
  • Upgrading the software to the latest versions I could find at that moment to get nothing but a fun memory management exercise
  • Looking for stpt credentials for the DMS379 everywhere I could reach (but why would this be the intended way if I get an autorun-related achievement)
  • Passing some non-existent arguments with the uirc commands hoping there's something undocumented there but there wasn't
  • Messing around SEC175, trying to do the autorun trick there. But there's no way to reboot it (unallocating the core memory has no effect lol), let alone the fact the autorun does not work on security devices.
  • Attempts to exploit a possible race condition , doomed from the very start as it seems, given that there is no easy way to run a script in the background without the dark magic of first un- and reloading the networking module, then trying to connect to the machine in a loop and uploading the file. Haven't tried it though, just a theory. This couldn't be the intended solution, could it?

So, could you please tell me what have I missed?
Last edited by @Extered; Aug 24, 2024 @ 2:16am
Originally posted by Terminal/ESC:
OOC: Thank you for the data and logs. After reviewing them I realize I may need to redesign this puzzle. You nearly solved it on several occasions, but the lack of an installed storage component stopped you. During playtesting devices would typically be equipped with this component before attempting this puzzle. However, your logs demonstrate a logical progression that omits this step, and it's not an intuitive requirement.
< >
Showing 1-6 of 6 comments
Terminal/ESC  [developer] Aug 15, 2024 @ 8:43am 
OOC: While I heartily approve of your meta-troubleshooting methods, the autorun over-write is a feature to exploit, not prevent. That said, please email at least one command log to terminal.escape.game@gmail.com so I can verify that the system is working as intended.
Last edited by Terminal/ESC; Aug 15, 2024 @ 8:52am
@Extered Aug 15, 2024 @ 11:40am 
Sent you a log and a save of my run. This time I think I found the intended solution, but only because I had some prior knowledge from the previous run where I bypassed it. Thanks!

Update: Turns out, I didn't. Still have no idea how to do this properly, given that that "solution" comes with no arm
Last edited by @Extered; Aug 15, 2024 @ 12:09pm
The author of this thread has indicated that this post answers the original topic.
Terminal/ESC  [developer] Aug 15, 2024 @ 1:11pm 
OOC: Thank you for the data and logs. After reviewing them I realize I may need to redesign this puzzle. You nearly solved it on several occasions, but the lack of an installed storage component stopped you. During playtesting devices would typically be equipped with this component before attempting this puzzle. However, your logs demonstrate a logical progression that omits this step, and it's not an intuitive requirement.
SpookyFM Aug 15, 2024 @ 2:08pm 
I'm stuck at exactly the same point. From your exchange I'm gleaning that somehow exploiting the auto-overwrite is key to the solution? Huh... I can't access DMS379's external media, so I don't see how that would help me but I'll think about it. And what does having storage have to do with it? I managed to get it from the broken DMS machine but haven't really found use for it because I can't remove any component from anything that would help me.

A headscratcher for sure. I'm really enjoying the game, the aesthetic, the sound design etc. by the way. And thanks for being so responsive!
@Extered Aug 15, 2024 @ 2:47pm 
Originally posted by SpookyFM:
And what does having storage have to do with it? I managed to get it from the broken DMS machine but haven't really found use for it because I can't remove any component from anything that would help me.

I was puzzled with the exact same question until I tried 1.0.11. In my save from 1.0.10 I found a way to pass it now that arm issues are fixed . But that seems a bit unintended :)
@Extered Aug 24, 2024 @ 1:49am 
As of 1.0.13 there are at least two options to solve this puzzle. Thank you for your help!
< >
Showing 1-6 of 6 comments
Per page: 1530 50