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
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -152,7 +152,7 @@ class IncrementingIntComponent implements IntComponent, ServerTickingComponent {
152
152
```
153
153
154
154
*Serverside ticking is implemented for all providers.
155
-
Clientside ticking is only implemented for entities, block entities, worlds, and scoreboards/teams.*
155
+
Clientside ticking is only implemented for entities, block entities, levels, and scoreboards/teams.*
156
156
157
157
If you want your component to **be notified of its provider being loaded and unloaded**, typically for advanced setup or cleanup,
158
158
you can add the [`ServerLoadAwareComponent`](./cardinal-components-base/src/main/java/org/ladysnake/cca/api/v3/component/load/ServerLoadAwareComponent.java)
@@ -169,7 +169,7 @@ class IncrementingIntComponent implements IntComponent, ServerLoadAwareComponent
169
169
}
170
170
```
171
171
172
-
*Serverside load and unload is implemented for entities, block entities, chunks, worlds, and scoreboards.
172
+
*Serverside load and unload is implemented for entities, block entities, chunks, levels, and scoreboards.
173
173
Clientside load and unload is only implemented for entities, block entities, and chunks. This is an experimental feature,
174
174
any feedback welcome.*
175
175
@@ -204,15 +204,15 @@ The next step is to choose an identifier for your component, and to declare it a
204
204
205
205
Components can be provided by objects of various classes, depending on which modules you installed.
206
206
The most common providers are [entities](https://ladysnake.org/wiki/cardinal-components-api/modules/entity),
* Entrypoint getting invoked to register <em>static</em> item component factories.
31
-
*
32
-
* <p>The entrypoint is exposed as either {@code "cardinal-components"} or {@code "cardinal-components-level"} in the mod json and runs for any environment.
33
-
* It usually executes right during {@linkplain ModInitializer mod init}, or before the first {@linkplain LevelData save properties object} gets loaded, whichever comes first.
34
-
*
35
-
* @since 2.4.0
28
+
* @deprecated renamed to {@code LevelDataComponentInitializer} in the module {@code cardinal-components-leveldata}
* Registers a {@link ComponentFactory} for all {@linkplain Level worlds}.
36
+
* Registers a {@link ComponentFactory} for all {@linkplain Level levels}.
37
37
*
38
38
* <p>If the component's actual implementation has different capabilities to {@code C}
39
39
* (typically if it is ticking and {@code C} is not), one should use the {@linkplain #register(ComponentKey, Class, ComponentFactory) dedicated overload}.
@@ -43,14 +43,14 @@ public interface WorldComponentFactoryRegistry {
* Registers a {@link ComponentFactory} only for {@linkplain Level worlds} with the given {@code dimensionId}.
53
+
* Registers a {@link ComponentFactory} only for {@linkplain Level levels} with the given {@code dimensionId}.
54
54
*
55
55
* <p>If the component's actual implementation has different capabilities to {@code C}
56
56
* (typically if it is ticking and {@code C} is not), one should use the {@linkplain #registerFor(ResourceKey, ComponentKey, Class, ComponentFactory) dedicated overload}.
@@ -61,7 +61,7 @@ public interface WorldComponentFactoryRegistry {
* Entrypoint getting invoked to register <em>static</em> world component factories.
30
+
* Entrypoint getting invoked to register <em>static</em> level component factories.
31
31
*
32
-
* <p>The entrypoint is exposed as either {@code "cardinal-components"} or {@code "cardinal-components-world"} in the mod json and runs for any environment.
32
+
* <p>The entrypoint is exposed as either {@code "cardinal-components"} or {@code "cardinal-components-level"} in the mod json and runs for any environment.
33
33
* It usually executes during {@linkplain ModInitializer mod init}, or right before the first {@link Level} instance is created, whichever comes first.
0 commit comments