# Exocraft gives signal to Proximity Switch

**URL:** <https://forums.atlas-65.com/t/exocraft-gives-signal-to-proximity-switch/6852>\
**Category:** NMS Beyond - Bugs & Issues\
**Created:** [December 9, 2019, 3:33am UTC](https://forums.atlas-65.com/t/exocraft-gives-signal-to-proximity-switch/6852 "2019-12-09T03:33:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![DevilinPixy](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.atlas-65.com/devilinpixy/32/74073_2.png) [@DevilinPixy](https://forums.atlas-65.com/u/DevilinPixy)\
**Post date:** [December 9, 2019, 3:33am UTC](https://forums.atlas-65.com/t/exocraft-gives-signal-to-proximity-switch/6852/1 "2019-12-09T03:33:17Z")

</div>

I think I finally figured out what causes Proximity Switches to fail at times, depending on location. I found out that placing a Proximity Switch near an Exocraft, remains triggered once activated once. You don’t have to be inside, they just give off a signal on their own. Moving the Exocraft away, causes it to function normally again.

Pretty annoying in my case, where I have built nice garages for my Exocraft. Maybe this could be useful, but _pffftttt_, it has given me headaches trying to figure out what caused this behaviour. 🥴

With Pilgrim near and activated

 ![275850_20191209042705_1](https://us1.discourse-cdn.com/flex019/uploads/etarc/original/3X/3/a/3a3fe805832fd7635c39dfb55b26eaccd1bfea3b.jpeg)

With Pilgrim near, but still active, while I am far away.

 ![275850_20191209042721_1](https://us1.discourse-cdn.com/flex019/uploads/etarc/original/3X/3/a/3a71ec70417451359322d5099df71fb7896c81d3.jpeg)

With Pilgrim moved and activated

 ![275850_20191209042837_1](https://us1.discourse-cdn.com/flex019/uploads/etarc/original/3X/1/4/148c0cbf7d02683158ff7a5e2a07eb90cb52413e.jpeg)

With Pilgrim moved, no longer active, while I am at a distance.

 ![275850_20191209042843_1](https://us1.discourse-cdn.com/flex019/uploads/etarc/original/3X/d/3/d3dab9343f44424421409159ec3796c7fb34572d.jpeg)

---

<div class="post-metadata">

**Author:** ![jedidia](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.atlas-65.com/jedidia/32/1237_2.png) [@jedidia](https://forums.atlas-65.com/u/jedidia)\
**Post date:** [December 9, 2019, 7:01am UTC](https://forums.atlas-65.com/t/exocraft-gives-signal-to-proximity-switch/6852/2 "2019-12-09T07:01:08Z")

</div>

Next up in NMS: The IAM update: “Identity and Access Management enables you to manage access to security critical NMS functionalities and resources securely. Using IAM, you can create and manage users and groups, and use permissions to allow and deny their access to NMS resources.” 🤣

(Text blatatantly ripped from the [AWS IAM description](https://aws.amazon.com/iam/), of course…)

---

<div class="post-metadata">

**Author:** ![DevilinPixy](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.atlas-65.com/devilinpixy/32/74073_2.png) [@DevilinPixy](https://forums.atlas-65.com/u/DevilinPixy)\
**Post date:** [August 21, 2025, 7:50pm UTC](https://forums.atlas-65.com/t/exocraft-gives-signal-to-proximity-switch/6852/3 "2025-08-21T19:50:19Z")

</div>