Skip to content

Commit f6b51ed

Browse files
committed
docs(api): update Fabric entrypoint registration to reflect 545d4a7
1 parent a3d22b0 commit f6b51ed

File tree

1 file changed

+19
-17
lines changed

1 file changed

+19
-17
lines changed

docs/developers/controlify-entrypoint.mdx

Lines changed: 19 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -49,24 +49,26 @@ dependencies {
4949

5050
## Registering the entrypoint
5151

52-
- On Fabric, you register an entrypoint like any other, by adding an entry to your `fabric.mod.json` file under the `entrypoints` section.
53-
- On NeoForge, you register an entrypoint using a Java service provider interface (SPI) in **`META-INF/services/dev.isxander.controlify.api.entrypoint.ControlifyEntrypoint`**.
54-
55-
<CodeTabs>
56-
```json !!tabs (Fabric) fabric.mod.json
57-
{
58-
"entrypoints": {
59-
"controlify": [
60-
"com.example.mymod.ControlifyEntrypoint"
61-
]
62-
}
63-
}
64-
```
52+
The entrypoint can be registered using a
53+
Java service provider interface (SPI) in **`META-INF/services/dev.isxander.controlify.api.entrypoint.ControlifyEntrypoint`**
54+
55+
```txt
56+
com.example.mymod.ControlifyEntrypoint
57+
```
58+
59+
### Fabric Entrypoint
6560

66-
```txt !!tabs (NeoForge) META-INF/services/dev.isxander.controlify.api.entrypoint.ControlifyEntrypoint
67-
com.example.mymod.ControlifyEntrypoint
68-
```
69-
</CodeTabs>
61+
On Fabric, the same entrypoint may **also** be registered via `fabric.mod.json`.
62+
63+
```json
64+
{
65+
"entrypoints": {
66+
"controlify": [
67+
"com.example.mymod.ControlifyEntrypoint"
68+
]
69+
}
70+
}
71+
```
7072

7173
Then simply create the class and implement the interface:
7274

0 commit comments

Comments
 (0)