obj
var
autoInitialized = "Some value"
nullUntilNeeded
Now let's say we had a verb to print out all of this obj's .vars list -- autoInitialized would appear of course, but assuming nullUntilNeeded was never assigned and remained null, would it appear as well? To more generally put it, do null variables still exist in every instance's var list, or are null variables left out of its .vars until initialized?
I am hesitant on just how many variables I can get away with assigning to specific types of mobs and objects, if they will all be carried around and bog down its .vars; I'd much prefer if null vars were left off that specific object.
Let's say we had a verb to print out all of this obj's .vars list. Like, if the DM Reference had an example for printing out all of an object's .vars list:
You'll see that some built-in vars default to null, and they're still in the vars list. The vars list is a list of vars defined for an object, and null is a valid value for vars before and after initialization, so it wouldn't make sense to leave them out.