mc-pvp-bots by FatihBastan: Claude Code mod code and design

What it does

Draws the status line, toasts
Watches tool calls
Hooks classic.ElicitationResult, classic.Notification, classic.PermissionRequest, session.end and 3 more
Keeps its own state between turns
Calls the network

Good points

Written in TypeScript
Handles errors
Writes no files

Code to start from

Two kinds: a starter modscode writes from the design above, and the lines of the mod's own code that draw it.

Starter (register.tsx)

import type { Register } from 'claude-code'

// Drawn like mc-pvp-bots by Fatih Baştan (status, toast), as modscode read it from the mod's code:
// https://modscode.com/gallery/fatihbastan-mc-pvp-bots/
// Written by modscode from that reading, not copied from the mod: use it as you like.
// Each value below stands for one the mod works out at run time; put in your own.
export const register: Register = on => {
  on('session.start', async ($, e, next) => {
    const scoreText = '…'
    const why = '…'
    await $.ui.status(`⚔ in the arena`)
    await $.ui.toast(`Claude needs you · ⚔ ${scoreText}`)
    await $.ui.toast(`⚔ Setup failed: ${why}`)
    return next(e)
  })
}

The mod's own code

Its licence text was not found at the commit read, so only the places in the source are linked.

FatihBastan/mc-pvp-bots

What its code calls

networkruns programsenv varstool callsremembers

The design, read from code

Claude — Code

Claude needs you · ⚔ 3

⚔ Setup failed:

Ask Claude…

⚔ in the arena

Drawn from the mod's source at the commit read, not from a run: a list is drawn three times, a condition takes its first branch that draws in the desktop app, and a value only the run time knows is shown as a made-up sample (dotted underline) or left out. Colours and type are this site's.

What its code shows

Read from the source at commit 460fd8efa05d on 2026-10-06. The first group decides whether a mod is listed; the rest is for you to weigh. A later commit is not read until the next crawl.

Decides the listing: code you can check
Entry read	Every module hooks/hooks.json names was read.hooks/register.ts
Parses	Every file parses as TypeScript or JavaScript.1 files parsed
All its code is in the mod	Every import is a file of the mod or the engine's own module; no packages, no require.all its code is in the mod
Readable	No minified lines, no eval or new Function, no import of a computed path, no encoded blobs.no minified code, no eval, no encoded blobs
Calls in the open	Network and programs are reached as $.http.fetch and $.process.run in place, never passed around.every call outside goes through $ in the open
For you to weigh before installing
Where it draws	The terminal, the desktop app, both, or nothing (hooks only: a guard or a prompt rewriter), as its code says. Shown, never a reason to leave a mod out.draws in the terminal and the desktop app, the same in both
Install line	Whether its repository's own .claude-plugin/marketplace.json lists it, so it installs from that marketplace with the lines on its page.listed in its repository's .claude-plugin/marketplace.json: installs from there
Programs on Windows	Whether every program it starts through $.process exists on Windows (tail, date, open, osascript, /usr/… do not).runs no program a Windows PC lacks
Network	Whether every fetch names its https host in the code.hooks/register.ts:165 fetch(`http://127.0.0.1:${conn!.port}${path}`)
Programs	Whether every program it starts is named in the code and is not a shell, an interpreter or a network tool.hooks/register.ts:141 node (a shell or interpreter); hooks/register.ts:302 node (a shell or interpreter); hooks/register.ts:318 node (a shell or interpreter); hooks/register.ts:401 node (a shell or interpreter)
Reads and sends	Whether it both reads files or environment variables and reaches the network.reads environment variables and reaches the network
Keys in the source	Whether the source holds what looks like an API key or a private key.no keys in the source
Licence	An open licence (MIT, Apache-2.0, BSD, ISC, Unlicense, 0BSD, CC0) with its text lets modscode show its code; otherwise the code is linked.MIT

This is a reading of the code text, not a security review: it does not run the mod, and it cannot see what a program the mod starts does. The check before installing is yours. How mods are chosen

Install it

Check it yourself before you install it. Mods run unsandboxed, with your permissions, and modscode does not vouch for what this code does. Read the code below (or run claude plugin validate . in its folder), weigh what it reaches, and install the commit you read.

Its repository is its marketplace. Add that marketplace (in the terminal with these commands, or in the desktop app's plugin settings) and install the mod from it:

/plugin marketplace add FatihBastan/mc-pvp-bots

/plugin install mc-pvp-bots@mc-pvp-bots

This installs the marketplace's latest commit, which may not be the one read here (460fd8efa05d). Compare them before you install.

Ask Claude about it

With the modscode connector added, Claude can read this design, what its code reaches and its code, and build on them. Ask it like this:

Read the modscode design "fatihbastan-mc-pvp-bots" with its code and make me a pane like it

Search them from Claude: the MCP connector