charlieamat

using System.IO;
using log4net.Config;
using UnityEngine;

public static class Bootstrap
{
    [RuntimeInitializeOnLoadMethod(RuntimeInitializeLoadType.BeforeSceneLoad)]
    private static void ConfigureLogging()
    {
        XmlConfigurator.Configure(new FileInfo($"{Application.dataPath}/log4net.xml"));

charlieamat

using UnityEngine;
using UnityEngine.Events;

public class SimpleClass : MonoBehaviour
{
    private UnityEvent _event;

    private void Awake()
    {
        _event.AddListener(() =>

charlieamat

1. Comment out the existing logic (except for _nearestInteractable)
   • We’re going to re-write Interactor using under-performant code
2. Implement the Update method
   • Instead of reacting to GameObjects that invoke the “OnTrigger” methods, we’re going to poll the scene for interactables
3. In Update, declare and initialize a variable called “interactables” using FindObjectsOfType()
   • Like the “GetComponent” methods, Unity has a set of “Find” methods that allow you to search the scene for GameObjects
   • These are generally unsafe because you can’t always predict how many objects will actually be in your scene
4. Add a foreach that loop that iterates over interactables
5. Check if _nearestInteractable is null:

• If it is, set it to the current interactable

charlieamat

1. In Unity, Right-click the _Project/Scripts folder, expand the Create menu, and click C# Script
2. Name the new file "Inventory" and open it in Visual Studio
3. Add a public String array called "Items"
4. Initialize the Items array in the Start method
   • e.g., "Sword", "Potion", "Scroll"
5. Use a for-loop to iterate over the Items array
   • Log each item to the console
6. Back in Unity, run the scene
   • Point out that nothing happens because the script hasn't been instantiated
7. Add the Inventory component to the Player GameObject in the Scene

charlieamat

• Create Interactor.cs
  • We want to let the Player interact with the environment
  • Or in other words, we want the Player to be an interactor of the environment
• Create Interactable.cs
  • Interactors needs something to interact with, so let's define a new component called "Interactable"
• Open Interactable.cs
• Implement a public method called Interact()
  • The idea here is that Interactors will call this method
• Add a Debug.Log() statement to Interact()
• Debug.Log("I've been interacted with!", gameObject)

charlieamat

public class Achievements : MonoBehaviour
{
  public void Track(string identifier)
  {
    // Track achievememnt progress
  }
}

charlieamat

public abstract class Interactable : MonoBehaviour
{
  public abstract void Interact();
}

charlieamat

• Create ItemType.cs
• Make ItemType derive from ScriptableObject
• Add a string field called "DisplayName"
  • We could add more meta information (e.g., stats, description, icon, etc.), but we don’t need to at the moment
  • Each instance of ItemType will represent a type of item and will be referenced in our code instead of strings
  • But how do we create item types?
• Add the CreateAssetMenu attribute
  • Like components that derive from MonoBehaviour, scriptable objects don't support constructors and can't be instantiated with new
  • You can use ScriptableObject.CreateInstance
• But the CreateAssetMenu allows you to create your scriptable object assets right from the Unity editor, which is what we want

charlieamat

public class FadingInteractable : Interactable
{
  [SerializeField] private float duration = 3;
  
  private float _elapsed;
  private Renderer _renderer;
  private bool _isFading;
  
  public void Interact()
  {

charlieamat

1. In the top navigation bar, click Window → Analysis → Profiler
2. (optional) Dock the profiler to the editor
3. Enable only the CPU Usage and Memory modules
   • Each profiler module provides information about a certain aspect of your game’s performance
   • Performance issues related to your code will appear in the CPU Usage and Memory modules
4. Run the scene, wait a few seconds, and press the pause button
   • The profiler window is split into two sections
     • The top shows a set of time-based graphs
     • The bottom gives information about the selected frame that’s contextual to the module that is currently in focus
5. Click on a frame in the CPU Usage graph