Comments

• ChrisIceBox

  8:16AM

  How many such Hotspots do you have?

  A third approach would be to dynamically turn the Hotspot on when the Player selects an Item, and off again when they deselect.

  This could be done with ActionLists using the Event Runner component, but it can also be done with a custom script attached to the Hotspot:

  using UnityEngine;
  using AC;
  
  public class DynamicHotspot : MonoBehaviour
  {
  
      public Hotspot hotspot;
  
      void OnValidate()
      {
          if (hotspot == null) hotspot = GetComponent<Hotspot>();
      }
  
      void OnEnable()
      {
          EventManager.OnInventorySelect += OnInventorySelect;
          EventManager.OnInventoryDeselect += OnInventoryDeselect;
          hotspot.TurnOff();
      }
  
      void OnDisable()
      {
          EventManager.OnInventorySelect -= OnInventorySelect;
          EventManager.OnInventoryDeselect -= OnInventoryDeselect;
      }
  
      private void OnInventoryDeselect(InvItem invItem)
      {
          hotspot.TurnOff();
      }
  
      private void OnInventorySelect(InvItem invItem)
      {
          hotspot.TurnOn();
      }
  
  }
  
• SylvanKeep

  9:59AM

  Thank you for your approaches.
  So far, I only have two hotspots of this type, but there will be quite a few more.
  Both solutions sound very good and don’t have that unpleasant “workaround” feel. I’ve tested both and decided on the script option. It’s quicker to set up for new hotspots and easier to understand later on.

  I’m not good at programming, and I actually try to avoid custom scripts. But as I understand it, it does the same thing as the EventRunner, which then executes an ActionList with Hotspot: Enable/Disable for me each time.