Begin port to 26.3: movement
This commit is contained in:
@@ -18,7 +18,7 @@ install the connection-mode dependencies:
|
||||
```
|
||||
$ python3 -m venv .venv
|
||||
$ source .venv/bin/activate
|
||||
$ python -m pip install flask flask-cors munch watchdog -e ../pyCraft
|
||||
$ python -m pip install astar flask flask-cors munch watchdog -e ../pyCraft
|
||||
```
|
||||
|
||||
## Running
|
||||
@@ -26,15 +26,20 @@ $ python -m pip install flask flask-cors munch watchdog -e ../pyCraft
|
||||
Run the bot directly with Python. For the Protospace offline-mode server:
|
||||
|
||||
```
|
||||
$ SERVER=games.protospace.ca python mosfet.py
|
||||
$ SERVER=127.0.0.1 python mosfet.py
|
||||
```
|
||||
|
||||
`mosfet.py` defaults to that server, player name `mosfet1`, and the current
|
||||
AuthMe password. Override `SERVER`, `PORT`, `PLAYER_NAME`, or `GAME_PASSWORD`
|
||||
through environment variables as needed. Microsoft authentication is not used.
|
||||
|
||||
The current entry point connects and handles AuthMe, but world automation is
|
||||
not enabled yet: those modules still depend on 1.16-era packet and world data.
|
||||
The 26.3 client now handles AuthMe, chat commands, chunk/world-state caching,
|
||||
modern block/item/entity data, basic entity tracking, and path-following movement
|
||||
(`1goto x y z`).
|
||||
Inventory, entity tracking, block breaking/placing, and the farming/trading jobs
|
||||
remain disabled until their 26.3 packets are migrated. The default server is
|
||||
`127.0.0.1`; set `SERVER` explicitly only when you intentionally want another
|
||||
server.
|
||||
|
||||
## Usage
|
||||
|
||||
@@ -54,11 +59,11 @@ would be ran like `1farm wood` or `1pos`.
|
||||
The exception are the below public commands, they can optionally be prefixed with `!`
|
||||
and all bots will run the command.
|
||||
|
||||
Commands can be issued in public chat or private message like `/msg mosfet1
|
||||
1farm wood`. The bot will reply the same way the command was issued.
|
||||
|
||||
Use `echo` to make Mosfet run Minecraft commands. For example, `1echo /sethome
|
||||
home` will cause him to issue the `/sethome` command.
|
||||
The current 26.3 command path handles public chat. Private-message routing is
|
||||
not migrated yet. Verified commands are `!ping`, `!pos`, `!loaded`, `!info x y
|
||||
z`, and addressed path movement such as `1goto x y z`. The command catalog below
|
||||
is retained from the legacy bot; inventory, interaction, and farming/trading
|
||||
commands are not yet available on 26.3.
|
||||
|
||||
### Public Commands
|
||||
|
||||
|
||||
Reference in New Issue
Block a user