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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,6 @@ For building the project yourself / contributing, see [Development, Debugging &
14
14
15
15
> **Note**: You can deploy it on your own server in less than a minute using a one-liner script from [Minecraft Everywhere repo](https://github.com/zardoy/minecraft-everywhere)
16
16
17
-
18
17
### Big Features
19
18
20
19
- Official Mineflayer [plugin integration](https://github.com/zardoy/mcraft-fun-mineflayer-plugin)! View / Control your bot remotely.
@@ -57,6 +56,7 @@ Howerver, it's known that these browsers have issues:
57
56
58
57
Server versions 1.8 - 1.21.4 are supported.
59
58
First class versions (most of the features are tested on these versions):
59
+
60
60
- 1.19.4
61
61
- 1.21.4
62
62
@@ -125,11 +125,11 @@ There is world renderer playground ([link](https://mcon.vercel.app/playground/))
125
125
126
126
However, there are many things that can be done in online production version (like debugging actual source code). Also you can access some global variables in the console and there are a few useful examples:
127
127
128
-
-`localStorage.debug = '*'` - Enables all debug messages! Warning: this will start all packets spam.
128
+
-If you type `debugToggle`, press enter in console - It will enables all debug messages! Warning: this will start all packets spam.
129
129
Instead I recommend setting `options.debugLogNotFrequentPackets`. Also you can use `debugTopPackets` (with JSON.stringify) to see what packets were received/sent by name
130
130
131
131
-`bot` - Mineflayer bot instance. See Mineflayer documentation for more.
132
-
-`viewer` - Three.js viewer instance, basically does all the rendering.
132
+
-`world` - Three.js world instance, basically does all the rendering (part of renderer backend).
133
133
-`world.sectionObjects` - Object with all active chunk sections (geometries) in the world. Each chunk section is a Three.js mesh or group.
134
134
-`debugSceneChunks` - The same as above, but relative to current bot position (e.g. 0,0 is the current chunk).
135
135
-`debugChangedOptions` - See what options are changed. Don't change options here.
@@ -139,7 +139,7 @@ Instead I recommend setting `options.debugLogNotFrequentPackets`. Also you can u
139
139
140
140
-`nbt.simplify(someNbt)` - Simplifies nbt data, so it's easier to read.
141
141
142
-
The most useful thing in devtools is the watch expression. You can add any expression there and it will be re-evaluated in real time. For example, you can add `camera.position` to see the camera position and so on.
142
+
The most useful thing in devtools is the watch expression. You can add any expression there and it will be re-evaluated in real time. For example, you can add `world.getCameraPosition()` to see the camera position and so on.
0 commit comments