Address reviews
This commit is contained in:
2 files changed
+7
-8
No files matched your search
@@ -1,9 +1,9 @@
|
||||
{
|
||||
"bedrock": {
|
||||
"supported": "26.0-26.33",
|
||||
"supported": "26.0-26.40",
|
||||
"latest": {
|
||||
"id": 1001,
|
||||
"name": "26.33"
|
||||
"id": 2168,
|
||||
"name": "26.40"
|
||||
}
|
||||
},
|
||||
"java": {
|
||||
|
||||
@@ -18,12 +18,11 @@ for the pre-registered custom skulls.
|
||||
To the client, these skulls are blocks. Therefore, they can be held in player inventories.
|
||||
In addition, attachables are defined for each skull block, so that it is displayed correctly when worn and held by entities.
|
||||
|
||||
To set up custom skulls in geyser, you have to choose how you are going to register them.
|
||||
The easiest is using custom JSON mappings, but you can also use the Geyser API, for example using a Geyser extension.
|
||||
To set up custom skulls in Geyser, you have to choose how you are going to register them.
|
||||
The easiest is using custom mappings via JSON files. Alternatively, you can also use the Geyser API, for example using a Geyser extension or a plugin.
|
||||
|
||||
:::warning
|
||||
Whilst Geyser tries its best to convert custom skulls automatically, it does not generate custom skull mappings.
|
||||
However, you can use automatic tools such as [Rainbow](/wiki/other/rainbow/) to make converting content simpler.
|
||||
:::info
|
||||
You can use tools such as [Rainbow](/wiki/other/rainbow/) to automatically generate custom JSON mappings for skulls.
|
||||
:::
|
||||
|
||||
:::info
|
||||
|
||||
Reference in new issue
Block a user