Triggering the Lift

• I wanted a new structure
  • Apparently, you need to declare one in c++ if you want to use it in c++.
  • So I added this to my TransporterFunctions.h

  • USTRUCT(BlueprintType)
    struct FDestinationType {
    	GENERATED_USTRUCT_BODY()
    
    		UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "TransporterFuns")
    		FString name;
    
    	    UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "TransporterFuns")
    		FString Description;
    
    		UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "TransporterFuns")
    		float x;
    
    		UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "TransporterFuns")
    		float y;
    
    		UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "TransporterFuns")
    		float z;
    
    		UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "TransporterFuns")
    		bool active;
    };
         

  • Compiling this gives me my new destination type
  • 
• I am going to build a number of components
  • A button (BP_Selection)
    • It has the following components
      • A sphere (the button)
      • A Text render
    • It has the following variables
      • A text value to display in the text render
      • A bool indicating if it is active or not.
      • An active color
      • An inactive color.
    • It has the following methods
      • Setup
        • Input: a text color and a height.
        • Set these.
        • Also, return a reference to yourself.
        • 
      • On begin play, just to make sure, set everything
        • 
      • Activate (Custom event)
        • 
      • Deactivate (Custom event)
        • 
      • IWasHit (Custom event)
        • Delay this construction for a moment.
  • A Pannel to hold buttons (BP_Pannel)
    • This is responsible for "managing" the buttons.
    • It takes an array of DestinationT
    • And constructs the buttons on the fly based on the array contents.
    • So I added an array of Destionation Types that I populated
      • 
    • And an array of BP_Selection types
    • In the construction script
      • Loop over the array of destinations.
      • Add ChildActor Component for each item.
        • I need the output of this, so I promoted this to a local variable. (CurrentChild)
        • 
        • 
      • You need to call SetChildActorClass
        • 
      • Then call setup on the new item, with the correct height and name.
        • 
      • Finally, add this to the array of buttons.
        • 
      • 
      • I messed with spaces a bit and ended up with
      • 
  • I also added a Custom Event (ChildHit)
    • A child that has been hit can call this.
    • It takes the name of the child as a parameter
    • Makes that child active by calling the Activate function
    • Deactivates all other children.
    • 
• Back to the selector.
  • Add the last function, IWasHit, a custom event.
  • Just call the ChildHit function of the parent.
  • 
• We need to use this pannel now.
  • To do this, we will add an input to the controler.
    • Edit project settings, input.
    • Add interact with the right mouse button to action mappings.
    • 
  • Edit the first person character
    • Add InputAction Interact To the event graph
    • We will be adding a line trace
      • This shoots a ray and finds the first thing it intersects with.
      • It needs a starting and ending position.
      • The camera is a good thing.
      • So we need the location of the camera.
        • The starting point will be the camera (GetWorldLocation)
        • The ending point will be along the look at vector
        • We can get this with GetForwardVector.
        • Adding these gives us a point along the forward vector.
        • 
    • Check to see if we hit anything, and if so, was it a BP_Selector?
    • 
    • If so, call IWasHit.
    • I had to change the trace to Trace Complex.
    • And the distance to 2000