This commit is contained in:
onebeastchris committed 2024-12-04 00:26:20 +08:00
1 parent 5641161aa8
commit 06f12d2248
5 files changed
+8 -33

No files matched your search

+1 -2
View File
@@ -8,7 +8,6 @@ import { useEffect, useState } from 'react'
import { StepData } from './StepProps'
import MarkDownStep from './steps/MarkDownStep'
import Test from './steps/md/Test.mdx'
// React components for each step
const stepComponents = [
@@ -26,7 +25,7 @@ let steps = Object.fromEntries(stepComponents.map((Component) => [formatStepName
// Add the markdown steps
steps = {
test: MarkDownStep(Test),
//test: MarkDownStep(Test),
...steps
}
@@ -1,2 +0,0 @@
I am step test<br />
<button onClick={() => props.destinations.error({...props.data, path: [...props.data.path, props.step]})}>Go to error</button>
+2 -2
View File
@@ -99,9 +99,9 @@ It has other benefits too. Here's a plugin that can just do that:
[CommandWhitelist](https://www.spigotmc.org/resources/81326/). Alternatively, use the [HideCommands](https://github.com/Redned235/HideCommands) Geyser extension to hide commands just for Bedrock players.
# Failed to load locale asset cache: Unrecognized token 'Cannot'
This or anything else related to failing to download a locale file on startup is usually caused by java trying to connect using IPv6 and Mojang only use IPv4, so start Geyser or the server up with this flag `-Djava.net.preferIPv4Stack=true`, EG: `java -Xms1024M -Djava.net.preferIPv4Stack=true -jar Geyser.jar`
This or anything else related to failing to download a locale file on startup is usually caused by java trying to connect using IPv6 and Mojadng only use IPv4, so start Geyser or the server up with this flag `-Djava.net.preferIPv4Stack=true`, EG: `java -Xms1024M -Djava.net.preferIPv4Stack=true -jar Geyser.jar`
# Outdated client! Please use 1.x.x
# Outdated client! Please use 1.x.x
The server is too new or Geyser is outdated. Make sure you're on the latest Geyser.
-27
View File
@@ -1,27 +0,0 @@
---
title: Geyser and Secure Chat
description: Information about disabling secure chat to allow Bedrock players to chat on Java servers.
---
In the 1.19 Java Edition updates, a mechanism for reporting player chat messages to Mojang was implemented.
Bedrock Edition does not support this reporting mechanism.
If your server or proxy settings require that every player joining supports this mechanism (which may be enabled by default),
Bedrock players will be unable to chat.
Server administrators can disable this setting, but please note that Java players can join with certain mods that make their messages unreportable.
For a technical explanation of Java's chat signing system, see this [article](https://gist.github.com/kennytv/ed783dd244ca0321bbd882c347892874).
# Disabling
*Vanilla, Spigot/Paper/forks, Fabric, NeoForge*
Set `enforce-secure-profile: false` in [server.properties](https://minecraft.fandom.com/wiki/Server.properties)
*BungeeCord and forks*
Set `enforce_secure_profile: false` in [config.yml](https://www.spigotmc.org/wiki/bungeecord-configuration-guide/)
*Velocity*
Set `force-key-authentication = false` in [velocity.toml](https://github.com/PaperMC/Velocity/blob/dev/3.0.0/proxy/src/main/resources/default-velocity.toml#L19)
+5
View File
@@ -8547,6 +8547,11 @@ rc@1.2.8:
minimist "^1.2.0"
strip-json-comments "~2.0.1"
react-decision-tree-flow@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/react-decision-tree-flow/-/react-decision-tree-flow-2.1.0.tgz#c8b114212b420316f83bfa62a42c49c1a82131a5"
integrity sha512-LuMj5/O1vKxfpbRcw5mI1iSL4eIxxxJf1eDa4ZJbjkduiLGYqaM5KB0r8zNQ8uZl8DA1MtXj9RDT2gXtn5w61A==
react-dev-utils@^12.0.1:
version "12.0.1"
resolved "https://registry.yarnpkg.com/react-dev-utils/-/react-dev-utils-12.0.1.tgz#ba92edb4a1f379bd46ccd6bcd4e7bc398df33e73"