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
+9-4Lines changed: 9 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -194,17 +194,22 @@ There are various tools to look XUIDs up online and they are also printed to the
194
194
195
195
## Variables
196
196
197
-
Custom server variables are passed in just like the allowlist or as a full JSON string.
197
+
Custom server variables are supported by Bedrock. Details and usage instructions can be found on the official bedrock documentation, located here:
198
198
199
-
Server variables are parsed into their most likely type (number-like turn into numbers, all other inputs are treated as string) using jq's `fromjson` command. In the example below, `var1` is a string, `var2` is a number, and `var3` is a string.
Custom server variables are passed in as comma-separated simple key-value pairs or as a full JSON string.
203
+
204
+
Server variables are parsed into their most likely type (number-like turn into numbers, all other inputs are treated as string) using [jq's `fromjson` command](https://jqlang.github.io/jq/manual/#convert-to-from-json). In the example below, `var1` is a string, `var2` is a number, and `var3` is a string.
200
205
201
206
For greater control on types, users can provide a full string JSON representation that is used as-is.
202
207
203
-
All variables are written to the config/default/variables.json. There is no support for Module-specific variable handling at this time.
208
+
All variables are written to the variables file located at `config/default/variables.json`. There is no support for Module-specific variable handling at this time.
0 commit comments