MaxV wrote:Mariasole, consider this:
local/global variable = bad
custom properties = good
That's a broad generalization. It depends on usage. Custom properties are very useful for permanent storage but they need to be managed carefully to avoid mistakes between sessions when used as transient storage. Variables are managed by the engine and are cleared automatically when no longer needed. In almost all cases, a script local provides the same functionality without the need to manage existence and content.
I speak from embarrassing experience. I now go out of my way to avoid transient custom properties. I use them for permanent entries that are part of the stack, never as a substitute for variables.
Variables and custom properties are meant for different uses. While it is possible to use properties as temporary storage, I'd advise against it. There are better ways that won't cause unexpected problems later.