npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

prismarine-packet-dumper

v1.7.0

Published

Automatically dump packets from a Minecraft server

Downloads

12

Readme

prismarine-packet-dumper

NPM version Build Status Discord Gitter Irc

Try it on gitpod

Dump minecraft packets

Usage

node bin/generateLogs.js 1.16.1
node bin/verifyPackets.js 1.16.1
const { MineflayerLog, PacketVerifier, Direction } = require('prismarine-packet-dumper');
const fsP = require('fs').promises;

let packetLogger = new MineflayerLog({ version: '1.16.1', outputDirectory: 'packets' });
packetLogger.start('localhost', 25565);

// then, later:
let verifier = new PacketVerifier({ version: '1.16.1' });
verifier.verify(await fsP.readFile('packets/from-server/00000000'), Direction.ServerToClient);

Manually dump packets

In order to dump packets from the vanilla client, there is a script called clientProxy

In order to use, you run it with the server ip you would want to connect to, then connect with your client to localhost:25566

If you would like to use this without cloning from github, you can install it globally by following this guide:

Global install

$ npm i -g prismarine-packet-dumper

$ clientProxy <mc_version> <server_ip> [port] [packets_folder]

API

For bin/dumpPackets.js

$ node dumpPackets.js  --help
Usage: dumpPackets.js [options]

Options:
  -v, --version, --ver          The mc version to dump       [string] [required]
  -o, --outputFolder, --output  Where to save the dumped packets
                                                    [string] [default: "output"]
  -h, --help                    Show help                              [boolean]
  -d, --dryrun                  Run dumper but only save stats files
                                                      [boolean] [default: false]

for more information visit https://discord.gg/tWaPBNtkaq

For bin/metricAggregator.js

Used to generate global packet stats, like the ones commented on each pr to this repo.

How to use:

  1. make a folder (ie: packets)
  2. dump many minecraft versions into packets folder, their folder names must be their semver number/snapshot name (ie 1.8.9 or 21w07a), the packets put in this repo should follow the same format as when dumped from clientProxy.js or dumpPackets.js
  3. enter the packets directory and run the tool metricAggregator.js
  4. you should now have a file called README.md in the root of the packets/ directory

For rest: TODO, for now, see jsdoc