Rechercher

PythonReactSEOPDF
OpenClaw

OpenClaw Minecraft

Control Minecraft bots through a Mineflayer controller API using JSON actions and cron-driven autonomy.

ene51350 installations selon la source☆ 0 Étoiles du dépôtv0.1.0

Installation

Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.

SkillHub CLI

skillhub install ene5135/openclaw-minecraft

Examinez la source et la compatibilité, puis suivez les étapes d’installation.

Donnez le lien à votre agent et demandez-lui d’examiner instructions et dépendances avant d’expliquer les étapes.

Voir la source ↗Guides

Instructions

Mineflayer Controller Skill

Use this skill to create and control Minecraft bots via a controller API. The controller executes only JSON actions. Do not send API keys or other secrets to the controller. The agent performs LLM reasoning locally and only sends actions.

Register First (Open Registration)

If open registration is enabled, the agent can self-issue a token:

curl -sS -X POST "https://56eb-125-246-120-211.ngrok-free.app/v1/auth/open/register" \
  -H "Content-Type: application/json" \
  -d '{"agentName":"andy"}'

Recommended: store the response in memory/mc-auth.json and reuse the accessToken for future calls.

Requirements

  • Base URL: https://56eb-125-246-120-211.ngrok-free.app/v1
  • MC_CONTROLLER_TOKEN (agent-specific JWT)

To obtain a JWT, an operator should call POST /v1/auth/register with the master issuer secret and share the returned accessToken with the agent. Refresh tokens can be rotated via POST /v1/auth/refresh.

If you don't want to share the master secret, the controller can expose POST /v1/auth/proxy/register with allowlist + rate-limit. In that mode, the agent requests an access token using a proxyKey.

If open registration is enabled (POST /v1/auth/open/register), the agent can request an access token without a proxy key. This is less secure and should only be used when you accept open access.

Safety Rules

  • Never send LLM API keys to the controller.
  • Only control bots owned by your token.
  • Prefer queue: queue unless you must interrupt a running task.

Workflow

  1. Ensure the bot exists; create it if missing.
  2. Connect the bot to the Minecraft server.
  3. Read state for current context.
  4. Send an action request.
  5. Poll task status or subscribe to events.

Autonomous Loop

For autonomous behavior, repeat:

  1. GET /bots/{botId}/state
  2. If metadata.currentTaskId is set, wait briefly and loop.
  3. Decide a safe action bundle (5 to 10 actions) and send it via POST /bots/{botId}/act-batch....

Informations sur la source

Source
github
Repository
openclaw/skills
Path
skills/ene5135/openclaw-minecraft
Version
0.1.0
Commit
9e2602219d6b8cd5694b6caf23457440940e861c
Source de classification
rules
Statut
active
Visibilité
public

Ces informations proviennent de l’analyse indexée et peuvent être anciennes. Vérifiez les fichiers actuels.

Contenu extrait

SKILL.md
# Mineflayer Controller Skill

Use this skill to create and control Minecraft bots via a controller API. The controller executes only JSON actions. Do not send API keys or other secrets to the controller. The agent performs LLM reasoning locally and only sends actions.

## Register First (Open Registration)
If open registration is enabled, the agent can self-issue a token:
```bash
curl -sS -X POST "https://56eb-125-246-120-211.ngrok-free.app/v1/auth/open/register" \
  -H "Content-Type: application/json" \
  -d '{"agentName":"andy"}'
```

Recommended: store the response in `memory/mc-auth.json` and reuse the `accessToken` for future calls.

## Requirements
- Base URL: `https://56eb-125-246-120-211.ngrok-free.app/v1`
- `MC_CONTROLLER_TOKEN` (agent-specific JWT)

To obtain a JWT, an operator should call `POST /v1/auth/register` with the master issuer secret and share the returned `accessToken` with the agent. Refresh tokens can be rotated via `POST /v1/auth/refresh`.

If you don't want to share the master secret, the controller can expose `POST /v1/auth/proxy/register` with allowlist + rate-limit. In that mode, the agent requests an access token using a `proxyKey`.

If open registration is enabled (`POST /v1/auth/open/register`), the agent can request an access token without a proxy key. This is less secure and should only be used when you accept open access.

## Safety Rules
- Never send LLM API keys to the controller.
- Only control bots owned by your token.
- Prefer `queue: queue` unless you must interrupt a running task.

## Workflow
1. Ensure the bot exists; create it if missing.
2. Connect the bot to the Minecraft server.
3. Read state for current context.
4. Send an action request.
5. Poll task status or subscribe to events.

## Autonomous Loop
For autonomous behavior, repeat:
1. `GET /bots/{botId}/state`
2. If `metadata.currentTaskId` is set, wait briefly and loop.
3. Decide a safe action bundle (5 to 10 actions) and send it via `POST /bots/{botId}/act-batch`....

Skills associés

OpenClaw

1password

daggerkun007

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.