No Way Home
By: SMG Studio
No Way Home is an Apple Arcade game from SMG Studio in which you need to fly around space with your trusty robot sidekick, destroying enemies and completing missions. This walkthrough guide should help you if you get stuck, but it’s a work in progress. Feel free to ask for extra help in the comments section.
Tips & Tricks:
– Use the mission arrow as a guide to where you should be heading next.
– Your robot sidekick can shoot enemies and doesn’t seem to take any damage. So if you want to play it a bit safer and take it slower, you try to hide behind rocks and space debris while he shoots at enemies.
– Your robot will also bring items to you, like scraps, that enemies dropped.
– The game does a pretty good job telling you where to go next, but you can explore for extra currency and materials.
– Don’t forget to upgrade your ship’s parts!
Walkthrough:
Part 1:
Part 2:
More coming soon!
ΓÇô Your robot sidekick can shoot enemies and doesnΓÇÖt seem to take any damage. So if you want to play it a bit safer and take it slower, you try to hide behind rocks and space debris while he shoots at enemies.
Actually, he can take damage, just that it’s in part that he’s a smaller target and more maneuverable than you are and the shield may be more resilient. He’ll respawn after a period of time. Guy tends to get in my line of fire, which is a bit odd since friendly fire doesn’t seem to affect me, or maybe it’s just much better at not accidentially shooting at me.
Yes, he does take damage. And if he gets in your way while shooting enemies you can easily destroy him. But he comes back after about 30 seconds. With my maxed weapon if he gets in the way of 2 shots heΓÇÖs dust.
Use ice rocks or frozen edges to cool dow an overheating gun. You can shoot from one of these types of rocks and your gun win not ever heat up
I really was enjoying this game until I hit a fatal flaw that halted all progress. The ability to upgrade your ship reactor capacity is elemental to any other upgrades for your ship and weapons. I wrote the developer in late April 2021 and received the response below (their formatting). Update 5/5/21 still no fix available.
Thanks so much for your report! This bug seems to have slipped in with the 1.2.3 update, which we’re currently investigating. I apologise for any annoyance caused by this issue in the meantime. Please bear with us while we work to fix it!Γò¼├┤Γö£├ºΓö£┬╗
Josh@SMG