You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Protector nodes that are marked compatible with parent protector should have their own default settings for param2 and also ability to disable param2 cloning.
Currently for example protector:protect does not use param2 but protector:protect2 uses it for orientation.
Should param2 be always 0 for former and only cloned for latter.
Currently cloning param2 from badge to block and vice versa allows keeping orentation of badge even if blocks are placed in between. This can be seen as benefit.
Does having useless param2 on block cause any harm?
The text was updated successfully, but these errors were encountered:
Protector nodes that are marked compatible with parent protector should have their own default settings for param2 and also ability to disable param2 cloning.
Currently for example protector:protect does not use param2 but protector:protect2 uses it for orientation.
Should param2 be always 0 for former and only cloned for latter.
Currently cloning param2 from badge to block and vice versa allows keeping orentation of badge even if blocks are placed in between. This can be seen as benefit.
Does having useless param2 on block cause any harm?
The text was updated successfully, but these errors were encountered: