Trying to access a property causes blueprint runtime error

Thanks a lot for acknowledging this behavior! I’m fine with re-compiling the blueprint for the moment, it’s not as bad as I thought :slight_smile: