create custom properties on entities.
- Thread starter dcelso
- Start date
@dcelso,
I'm working on a tag system in next engine update to add properties at design time. For now, you just answered your own question. Use entity vars. I reccomend setting them in the onspawn event. Don't forget the script engine supports #define. That's a good way to code your starting values.
DC
I'm working on a tag system in next engine update to add properties at design time. For now, you just answered your own question. Use entity vars. I reccomend setting them in the onspawn event. Don't forget the script engine supports #define. That's a good way to code your starting values.
DC
Entity vars.
Rule of thumb for any variables in any engine, language, etc: Always use the most narrow scope possible.
About Script Variables
I've noticed some confusion about variable scopes and types, so here is a quick rundown to help ameliorate that. Local/Inline Variables Inline variables are variables you define inside a given function without specifying the scope. It's technically correct to call them local variables, but...
www.chronocrash.com
DC
Bloodbane
Well-known member
It depends on how long you want to store the value. If you only want to store it for one level only, entity var is good choice. But if you want to store it for multiple levels, use global var.
If your knives are carried from level to level, you'd have to use global variable.