Main branch¶
-
-
Feature: Attribute-support for saving/loading
dequeswithmaxlen=set.
-Contrib: Container typeclass with new commands for storing and retrieving +
New Contrib:
Containertypeclass with new commands for storing and retrieving things inside them (InspectorCaracal)
+Feature: Add
TagCategoryPropertyfor setting categories with multiple tags +as properties directly on objects. ComplementsTagProperty.
+Feature: Attribute-support for saving/loading
dequeswithmaxlen=set.
+Feature: Refactor to provide
evennia.SESSION_HANDLERfor easier overloading +and less risks of circular import problems (Volund)
+Fix: Allow webclient’s goldenlayout UI (default) to understand
msg+clskwarg for customizing the CSS class for every resultingdiv(friarzen)Fix: The
AttributeHandler.all()now actually acceptscategory=as keyword arg, like our docs already claimed it should (Volund)
+Fix:
TickerHandlerstore key updating was refactored, fixing an issue with +updating intervals (InspectorCaracal)Docs: New Beginner-Tutorial lessons for NPCs, Base-Combat Twitch-Combat and Turnbased-combat (note that the Beginner tutorial is still WIP).
from evennia import DefaultObject
-from evennia import TagProperty
+from evennia import TagProperty, TagCategoryProperty
+
class Sword(DefaultObject):
+ # name of property is the tagkey, category as argument
can_be_wielded = TagProperty(category='combat')
has_sharp_edge = TagProperty(category='combat')
+
+ # name of property is the category, tag-keys are arguments
+ damage_type = TagCategoryProperty("piercing", "slashing")
+ crafting_element = TagCategory("blade", "hilt", "pommel")
+
Tags are short text lables one can ‘hang’ on objects in order to organize, group and quickly find out their properties. An Evennia entity can be tagged by any number of tags. They are more efficient than Attributes since on the database-side, Tags are shared between all objects with that particular tag. A tag does not carry a value in itself; it either sits on the entity
+You manage Tags using the TagHandler (.tags) on typeclassed entities. You can also assign Tags on the class level through the TagProperty (one tag, one category per line) or the TagCategoryProperty (one category, multiple tags per line). Both of these use the TagHandler under the hood, they are just convenient ways to add tags already when you define your class.
Above, the tags inform us that the Sword is both sharp and can be wielded. If that’s all they do, they could just be a normal Python flag. When tags become important is if there are a lot of objects with different combinations of tags. Maybe you have a magical spell that dulls all sharp-edged objects in the castle - whether sword, dagger, spear or kitchen knife! You can then just grab all objects with the has_sharp_edge tag.
Another example would be a weather script affecting all rooms tagged as outdoors or finding all characters tagged with belongs_to_fighter_guild.
In Evennia, Tags are technically also used to implement Aliases (alternative names for objects) and Permissions (simple strings for Locks to check for).
Properties of Tags (and Aliases and Permissions)¶
Tags are unique. This means that there is only ever one Tag object with a given key and category.
-
-Not specifying a category (default) gives the tag a category of None, which is also considered a
-unique key + category combination.
-
-When Tags are assigned to game entities, these entities are actually sharing the same Tag. This
-means that Tags are not suitable for storing information about a single object - use an
+
+Important
+Not specifying a category (default) gives the tag a category of None, which is also considered a unique key + category combination. You cannot use TagCategoryProperty to set Tags with None categories, since the property name may not be None. Use the TagHandler (or TagProperty) for this.
+
+When Tags are assigned to game entities, these entities are actually sharing the same Tag. This means that Tags are not suitable for storing information about a single object - use an
Attribute for this instead. Tags are a lot more limited than Attributes but this also
makes them very quick to lookup in the database - this is the whole point.
Tags have the following properties, stored in the database:
key - the name of the Tag. This is the main property to search for when looking up a Tag.
-category - this category allows for retrieving only specific subsets of tags used for
-different purposes. You could have one category of tags for “zones”, another for “outdoor
-locations”, for example. If not given, the category will be None, which is also considered a
-separate, default, category.
-data - this is an optional text field with information about the tag. Remember that Tags are
-shared between entities, so this field cannot hold any object-specific information. Usually it would
-be used to hold info about the group of entities the Tag is tagging - possibly used for contextual
-help like a tool tip. It is not used by default.
+category - this category allows for retrieving only specific subsets of tags used for different purposes. You could have one category of tags for “zones”, another for “outdoor locations”, for example. If not given, the category will be None, which is also considered a separate, default, category.
+data - this is an optional text field with information about the tag. Remember that Tags are shared between entities, so this field cannot hold any object-specific information. Usually it would be used to hold info about the group of entities the Tag is tagging - possibly used for contextual help like a tool tip. It is not used by default.
-There are also two special properties. These should usually not need to be changed or set, it is
-used internally by Evennia to implement various other uses it makes of the Tag object:
+There are also two special properties. These should usually not need to be changed or set, it is used internally by Evennia to implement various other uses it makes of the Tag object:
-model - this holds a natural-key description of the model object that this tag deals with,
-on the form application.modelclass, for example objects.objectdb. It used by the TagHandler of
-each entity type for correctly storing the data behind the scenes.
-tagtype - this is a “top-level category” of sorts for the inbuilt children of Tags, namely
-Aliases and Permissions. The Taghandlers using this special field are especially intended to
-free up the category property for any use you desire.
+model - this holds a natural-key description of the model object that this tag deals with, on the form application.modelclass, for example objects.objectdb. It used by the TagHandler of each entity type for correctly storing the data behind the scenes.
+tagtype - this is a “top-level category” of sorts for the inbuilt children of Tags, namely Aliases and Permissions. The Taghandlers using this special field are especially intended to free up the category property for any use you desire.
+