Shutdown Protocol Dev log – Day 3

· ·

Dev log – Day 3

Summary

Today was focused on building the foundation for the interaction system by creating a parent interactable class, establishing child Blueprint types, and beginning work on a modular door system. I also created a set of colored material instances to help visually differentiate level components. Significant time was spent implementing door logic, including opening, closing, and locking behavior driven by timelines and overlap events. The day concluded with several quality-of-life improvements, followed by a major setback: an accidental deletion of crucial asset folders during a restructuring pass, resulting in the loss of meshes, materials, and level asset Blueprints—highlighting the urgent need for version control.


What I Worked on Today

Creating Interactable Parent Class


Setting Up Interactable Blueprints


Creating Base Door System


Creating Colored Material Instances


Adding Door Logic

Overlap Logic

Locking System


Quality of Life Improvements

Asset Folder Restructure

Major Issue


Technical Notes


Challenges & Lessons Learned


Next Steps

  1. Recreate lost Blueprints (ceiling light, emergency lights).
  2. Implement triggers and interactions for door locking/unlocking using the BP_Trigger system.
  3. Set up version control and begin routine backups to prevent future losses.