This section explains the core structure of AVE II. It covers which systems manage data, how responsibilities are split up, and how different parts of the project communicate with each other.
These pages are designed to help you understand where to modify or add Blueprint logic. They explain which classes should handle specific tasks and how to keep everything organized.
💡 Note: We recommend reading this section before you start adding new features. Following these patterns will help keep the project stable and easy to manage.
Core Blueprints and their responsibilities
You can find the core Blueprint classes in the Content > AVEII > Core folder.
| Blueprint | Class Name | Primary Responsibility |
| Game Mode | BP_AVE_GM | Defines default Pawn and Player Controller classes. |
| Game Instance | BP_AVE_GI | Acts as a global mediator for POIs, UI Modes, and POI filtering. |
| Player Controller | BP_AVE_PC | Handles Pawn orchestration |
| Pawn | BP_AVE_Pawn_Exp | Manages player input and interaction logic. |
