In this guide, I have failed to explain any inconsistencies between what I say and how it actually works.
Brandon (to Neale) smiles, "and we don't have name aliases anymore :)" Brandon (to Neale) says, "we have name templates" Brandon (to Neale) says, "look at ?security" Brandon (to Neale) says, "you gave an example for adding/modifying a command, I'd put it under programming actually" Brandon baps Neale, "and call it a place, not a room :) Brandon (to Neale) says, "and I just fixed it so you can have spaces after the comma, when specifying templates (ala: My Name, template)" Brandon (to Neale) says, "also, you may want to explain that cold is smart, if the name is "My Castle" it will match "My" "Castle" and "My Castle", so you don't need to add a 'castle' template.." Brandon (to Neale) says, "under creating objects, tell people to use @new" Brandon (to Neale) says, "basically @new should be used by the generic person, @spawn is more for programmers who know what they are doing" Brandon (to Neale) says, "@new lets the parent decide how to create the instance (so frobs can be handled right) where @spawn ALWAYS creates a new object the same way" Brandon (to Neale) says, "you may want to explain context matching as well..." Brandon (to Neale) says, "i.e. get bottle;drop it (drops bottle)"