Comments

• incommunicado

  August 2023

  Great, thank you, will try this.
• incommunicado

  August 2023 edited August 2023

  I tried this, but then doing so has the effect that even clicking options on a menu require to press the "E" key (instead of the left mouse button)

  The behaviour I'm trying to achieve is this:
  1. When in-game, clicking left mouse button fires a weapon. And pressing 'e' interacts with Hotspots etc.
  2. When the game is paused or on a menu or in a cut scene, the left mouse button acts as the regular mouse cursor, at which point, left click would behave as a regular left click and interact with the UI.

  Thanks in advance for any insights on how to achieve this. Thank you.
• incommunicado

  August 2023 edited August 2023

  Hmm... I had a look at the combat example project. This code looks promising:

  if (KickStarter.stateHandler.IsInGameplay ())
  {
  if (CanAttack ())
  {
  // Recieve aim/fire input if in gameplay and a weapon is equipped
  
  SetAimState (Input.GetButton ("Aim"));
  
  if (IsAiming ())
  {
  if (Input.GetButtonDown ("Fire1"))
  {
  Attack ();
  
  // Prevent Interaction input from being received in the same frame as firing a weapon (so that the two cannot occur simultaneously)
  KickStarter.playerInteraction.IgnoreInputThisFrame ();
  }
  else if (Input.GetButtonDown ("Reload"))
  {
  Reload (heldWeaponInstance);

  I further studied the FP_Crouch script that comes with the downloadable First Person controller for AC. I think I might be able to make a copy of that and then use the above script as an FP_Shoot script

  Would this be the right approach?
• incommunicado

  August 2023 edited August 2023

  Hi Snan, thank you for checking back; I did try it again, but I'm facing the same issue. If I go to the Input Manager and map InteractionA to the "e" key, then in all the menus, I have to press "e" instead of left mouseclick to select a menu item. And mouse clicks don't do anything. Not sure what might be working differently for me, but thank you for trying to help. Let me keep checking.

  Meanwhile, @ChrisIceBox please let me know if I'm doing anything wrong.
• incommunicado

  August 2023

  Hey Snan, I started a new empty unity project, added AC into it, and then unchecked "Mouse clicks have default functionality?" and as expected mouse clicks don't work on the menu nor interact with hotspots.

  Then I added InteractionA in Input Manager and mapped it to "e" and now pressing "e" works for both interactions and to select a menu item. But mouse clicks don't work at all in the menus.

  Not sure what I'm doing wrong. I will keep trying, thank you for your help.
• incommunicado

  August 2023

  I found the solution here:
  https://www.adventurecreator.org/forum/discussion/9331/button-press-to-pickup-item

  It seems another user had the same problem; if he disabled "Mouse clicks have default functionality?" then the menus stopped responding to mouseclicks.

  Instead, he changed "Interaction Method" to "Choose Interaction then hotspot" which gives three new input actions for the Input Manager. And you can map custom keys to "use", "examine" etc.

  Thank you for the suggestions and help.
• incommunicado

  August 2023 edited August 2023

  Ok, the above method didn't fully work so I finally solved it as follows:
  1. Set "Settings > Interface Settings > Interaction Method" to "Custom Script"
  2. Keep "Mouse Clicks have Default functionality" as checked (so menus will work)
  3. Created the below script for a custom interaction:

  using UnityEngine;
  namespace AC
  {

  [AddComponentMenu("Adventure Creator/3rd-party/Custom interaction system example")]
  [HelpURL("https://www.adventurecreator.org/scripting-guide/class_a_c_1_1_custom_interaction_system_example.html")]
  public class UseEInteraction : MonoBehaviour
  {
  
      private Hotspot selectedHotspot = null;
      private bool isLookingAtHotSpot = false;
  
      private void OnEnable ()
      {
          EventManager.OnHotspotSelect += OnHotSpotSelected;
          EventManager.OnHotspotDeselect += OnHotSpotDeSelected;
          //EventManager.OnStartSpeech += OnSpeechStarted;
          //EventManager.OnStopSpeech  += OnSpeechStopped;
      }
  
      private void OnDisable ()
      {
          EventManager.OnHotspotSelect -= OnHotSpotSelected;
          EventManager.OnHotspotDeselect -= OnHotSpotDeSelected;
          //EventManager.OnStartSpeech -= OnSpeechStarted;
          //EventManager.OnStopSpeech  -= OnSpeechStopped;        
      }
  
      private void Start ()
      {
          if (KickStarter.settingsManager != null && KickStarter.settingsManager.interactionMethod != AC_InteractionMethod.CustomScript)
          {
              ACDebug.LogWarning ("This script works best when the Settings Manager's 'Interaction method' field is set to 'Custom Script'.", this);
          }
      }
  
      private void Update ()
      {
          if (KickStarter.stateHandler.gameState != GameState.Normal)
          {
              return;
          }
  
          if (isLookingAtHotSpot) {
              if (KickStarter.playerInput.InputGetButtonDown ("ActivateHotspot")) {
                  ACDebug.LogWarning ("Pressed E.", this);
                  selectedHotspot.RunUseInteraction ();
              }   
          }
      }
  
      private void OnHotSpotSelected (Hotspot hotspot)
      {
         isLookingAtHotSpot = true;
         selectedHotspot = hotspot;
      }
  
  
      private void OnHotSpotDeSelected (Hotspot hotspot)
      {
         isLookingAtHotSpot = false;
         selectedHotspot = null;
      }
  }
  

  }

  4. Add this script to a game object
  5. Add a new key in InputManager called "ActivateHotspot" and assign it any key.

  This works for me because I'm making a very simple combat based game where there is only one interaction with any hotspot. I needed a very simple solution and this seems to be working so far.