forked from Clones/Controlify
1.3 changelog
This commit is contained in:
4
.github/README.md
vendored
4
.github/README.md
vendored
@ -69,7 +69,7 @@ have not yet memorised the controls.
|
||||
|
||||
Also, some GUIs display controller buttons on elements that have a controller shortcut, to easily navigate with a controller like you should be able to.
|
||||
|
||||

|
||||

|
||||
|
||||
### Containerised Controllers
|
||||
|
||||
@ -90,7 +90,7 @@ without convoluted support throughout the whole mod's codebase, making it diffic
|
||||
The deadzone values of your controller are automatically calibrated,
|
||||
meaning you don't have to worry about it.
|
||||
|
||||

|
||||

|
||||
|
||||
## What is to come?
|
||||
|
||||
|
@ -16,7 +16,7 @@ plugins {
|
||||
}
|
||||
|
||||
group = "dev.isxander"
|
||||
version = "1.3.0-beta.2+1.20"
|
||||
version = "1.3.0+1.20"
|
||||
val isBeta = "beta" in version.toString()
|
||||
if (isBeta) println("Beta version detected.")
|
||||
|
||||
@ -184,7 +184,7 @@ if (modrinthId.isNotEmpty()) {
|
||||
versionNumber.set("${project.version}")
|
||||
versionType.set(if (isBeta) "beta" else "release")
|
||||
uploadFile.set(tasks["remapJar"])
|
||||
gameVersions.set(listOf("1.20-pre2"))
|
||||
gameVersions.set(listOf("1.20"))
|
||||
loaders.set(listOf("fabric", "quilt"))
|
||||
changelog.set(changelogText)
|
||||
syncBodyFrom.set(file(".github/README.md").readText())
|
||||
@ -208,7 +208,7 @@ if (hasProperty("curseforge.token") && curseforgeId.isNotEmpty()) {
|
||||
|
||||
id = curseforgeId
|
||||
releaseType = if (isBeta) "beta" else "release"
|
||||
addGameVersion("1.20-Snapshot")
|
||||
addGameVersion("1.20")
|
||||
addGameVersion("Fabric")
|
||||
addGameVersion("Java 17")
|
||||
|
||||
|
36
changelogs/1.3.0+1.20.md
Normal file
36
changelogs/1.3.0+1.20.md
Normal file
@ -0,0 +1,36 @@
|
||||
# Controlify 1.3 for 1.20
|
||||
|
||||
## New Features
|
||||
|
||||
### Server-side support
|
||||
|
||||
Controlify now has server-side support, meaning it is now recommended to install Controlify on your server.
|
||||
|
||||
### `/vibratecontroller` command
|
||||
|
||||
This command allows you to make players' controllers vibrate. You can specify the intensity of both the
|
||||
low frequency and high frequency motors, and the duration of the vibration.
|
||||
|
||||
You can select to either do a simple vibration, or place the vibration in world-space (either bound to an entity or position)
|
||||
with a range to have the vibration intensity decrease with distance.
|
||||
|
||||
```
|
||||
/vibratecontroller <receivers> <low_freq_intensity> <high_freq_intensity> <duration_ticks> <(static|positioned)> [<range>] [<(position|entity>]
|
||||
|
||||
/vibratecontroller @a 0 0.25 200 positioned 10 ~ ~ ~
|
||||
/vibratecontroller @a 0.75 1 50 static
|
||||
/vibratecontroller @a 0.75 1 20 positioned 10 @e[type=minecraft:warden,sort=nearest,limit=1]
|
||||
/execute as @e[type=!minecraft:player] run vibratecontroller @a 1 0 5 positioned 20 @s
|
||||
```
|
||||
|
||||
This comes with a client option in global settings to ignore these server requests to vibrate.
|
||||
|
||||
### Reach-around policy
|
||||
|
||||
When Controlify is stored in the server, by default, the reach-around policy is set to `disallow`. You can
|
||||
allow reach-around placement on your server by setting the `reach_around_policy` config option to `true`.
|
||||
|
||||
## Bug Fixes
|
||||
|
||||
- Fixed hotplugging not working when no controllers were connected at launch
|
||||
- Fixed natives not working on Apple Silicon
|
Reference in New Issue
Block a user