"Accessed None" errors perhaps could remind users to check their references

I always check my pointers in C++, but for some reason that mindset doesn’t carry over into blueprinting :cool:

I know now that “Accessed None” errors are more often than not caused by a failure to check if a reference is valid before getting its value, but I had no idea that this was my problem before. I think it would be beneficial to the user if this error were to ask them, “Did you forget to check if a reference is valid before trying to Get it?”

Just a suggestion :slight_smile:

Thanks homies

Hi Jared Therriault,

Thank you for your request, we will take this into consideration.

This is actually in the works as well as a lot of error message updates. We’re making an effort to have them clarify better what has happened when a problem occurs.

Thank you two, I appreciate the replies.