 |
Attention | Topic was automatically imported from the old Question2Answer platform. |
 |
Asked By | jarlowrey |
Set_meta, has_meta and get_meta. When would you use this?
1 Like
|
Reply From: | Larpon |
Meta data can be useful in cases where it’s difficult to distinguish objects from each other by looking at their primary attributes like .name or at their type.
Meta data is especially useful in collision handling where you might need to handle collisions with a, say, StaticBody2D - but your level is full of StaticBody2D’s - the ground, platforms, walls etc. so to easily find out what type you’ve collided with you give them a meta data entry type (e.g. .set_meta('type','wall')) - later on when your player collides with something you look at the meta data for the object and handle the collision accordingly.
… you could also let objects share state via meta data or similar.
So, yeah - use it for whatever you find useful?
Wouldn’t groups be easier to use for this?
Lightning_A | 2021-03-01 16:01
Because group you can only ask a node if it is in group X. If you have just “wall” and “ground” that query is simple. If you have more types, you will need to ask for each possible group. In effect you’d need to do multiple ‘finds’ instead of being able to use a match statement.
The other way to think of meta data is it is a way to add a “property” without needing to attach a script.
Groups are powerful when needing to address certain nodes anywhere in the scene tree.
dotty | 2021-06-05 15:22
Another aspect of meta is that it allows you to store any sort of data and use them dynamically in response to events. Mimicking that with groups would be unfeasible.
byrro | 2021-12-23 17:57