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
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,7 @@ Coding in Unity DOTS indroduces new boilerplate that needs to be remembered. Fro
34
34
| dcj | Create a Unity DOTS Job (no `using Unity.Entities` added with this command, for it is likely added to a System file & not standalone) |
35
35
| dcb | Create a Unity DOTS component baker & its authoring monobehavior class |
36
36
| dcbd | Create a Unity DOTS component baker referencing another data source (i.e. mesh, gameObject, scriptable obj...) |
37
+
| dca | Create a Unity DOTS aspect (used to group related components) |
37
38
38
39
### Naming Convention
39
40
The commands above all begin with dc standing for "Dots Create ..." which means you can always just type dc and use the dropdown to find or read more about any command. For example, `dcsc` stands for Dots Create Shared Component.
0 commit comments