Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is matdoes.dev?
matdoes.dev is the personal site of a developer named Mat, who describes it as "my blog and portfolio website." It is a working portfolio rather than a product page: the headline projects are listed with short one-line descriptions and start dates, spanning 2018 to the present.
What the site covers
The project list shows a consistent focus on Minecraft tooling and small internet utilities. Representative entries:
- Azalea — Rust crates for building Minecraft bots, clients and tools.
- matscan — an internet-scale Minecraft server scanner with automated warnings for admins.
- simdnbt — a highly optimized Rust implementation of Minecraft's NBT data format.
- mat's packet debugger — a tool for inspecting Minecraft protocol packets.
- SkyBlock Stats — a web interface for the Hypixel SkyBlock API, listed as running 2019–2024.
- metasearch2 — a small metasearch engine.
- seized.fyi — an archive of government website seizure banners.
- matdoesdev-protocols — the same site mirrored over SSH, Telnet, Gemini and Gopher.
The page also has sections for Links, Contact, Blog and 88x31-style buttons, which fits the personal-homepage style the welcome message signals.
Who it's for
Readers arrive for two different reasons. If you are a Minecraft developer, the Rust libraries and protocol tools are the practical draw; the project names tell you what exists, but you will need to follow each project's own link for installation and API details. If you are curious about small, self-directed web projects, the list works as a sample of one person's interests over several years, including retired projects such as an image host and a Discord bot.
A sensible next step
Pick the project closest to your task and open its own page before committing: a one-line description is enough to shortlist, not to evaluate maturity, licensing or maintenance. For comparison, the Rust Minecraft ecosystem is also represented by docs.rs for crate documentation and Modrinth for Minecraft-adjacent projects.
Who is mat and what kinds of projects does he build?
Mat is an independent developer who describes himself simply as someone who "makes things on the internet" and runs this site as his personal home on the web, combining a portfolio with a blog. His project list shows a clear center of gravity: Minecraft tooling and protocol work, plus a long-running interest in search, archiving and small developer utilities.
What he actually builds
- Minecraft infrastructure and tooling. Azalea is a set of Rust crates for building Minecraft bots, clients and tools; simdnbt is a highly optimized Rust implementation of Minecraft's NBT data format; msdsmchr renders Minecraft player heads quickly through an API; and his packet debugger lets developers inspect Minecraft protocol packets. Azalea Burger, a fork of another project, automates reverse-engineering of modern Minecraft versions.
- Data collection and archiving. matscan scans Minecraft servers across the internet and warns admins automatically; the Minecraft UUID archives preserve player identifiers and metadata; seized.fyi collects government website seizure banners; and x227f crawls 88x31 web buttons.
- Search. He has built metasearch engines twice — an earlier simple version and the current "cute and efficient" metasearch2 — which suggests sustained interest in aggregating results rather than accepting one index.
- Web experiments and protocol play. Internet Roadtrip Pathfinder reverse-engineers a web game and Google Street View for route finding, and matdoesdev-protocols mirrors his site over SSH, Telnet, Gemini, Gopher and similar protocols.
- Developer conveniences. Web Utils bundles small tools for software developers.
- Community and Discord work, mostly earlier. SkyBlock Stats offered a feature-rich interface to the Hypixel SkyBlock API, with a separate API wrapper alongside it; Forum Sweats and 4bit were Discord bots; Variance is an opinionated Cinny fork aimed at feeling more like Discord.
How to read the list
The dates matter as much as the names. Several projects have run for years — Azalea, matscan, metasearch2 and the UUID archives are all marked as ongoing — while others, such as SkyBlock Stats, Minecraft Assets and the image hosts, have ended. That pattern points to someone who prototypes widely, keeps what proves useful and retires the rest. The language choice is telling too: Rust appears repeatedly where performance matters, while web interfaces and bots cover the user-facing side.
If you are a Minecraft developer, start with Azalea or simdnbt for building on top of the game, and the packet debugger when something behaves unexpectedly on the wire. If you are curious about the person rather than the code, his blog is the better entry point. Related community tooling lives at Modrinth and GitHub, where projects of this kind are usually published and discussed.
Which of mat's Minecraft tools could I use to build a bot or client?
Use Azalea, mat's collection of Rust crates for building Minecraft bots, clients and tools. It is the project on the site explicitly described for that purpose, and its "2021 – now" span suggests it has been maintained over time.
What else on the site is relevant
- simdnbt — a highly optimized Rust implementation of Minecraft's NBT data format. Useful if your bot or client needs to read or write NBT (for example, handling item or entity data) and you want a Rust-native parser.
- mat's packet debugger — a tool for conveniently inspecting Minecraft protocol packets. Handy while developing a client to see what the server is actually sending and compare it with what your code expects.
- Azalea Burger (fork) — described as automated reverse-engineering of modern Minecraft versions. This is relevant when protocol or data formats change and you need to understand the new version, rather than as a library you would call directly.
- Minecraft UUID archives — archives of nearly every Minecraft player UUID and metadata. This can help with player lookups, but it is an archive, not a bot-building component.
How to decide
Start with Azalea if you are writing a bot or client in Rust. Add simdnbt if NBT handling is part of your work, and use the packet debugger during development when traffic does not match expectations. The other projects support the ecosystem around bot development rather than replacing Azalea itself.
A practical next step is to open mat does dev and read the Azalea project entry, then check whether your target Minecraft version is covered before committing to it.
How can I contact mat or find his blog and social links?
Use the Contact section on the site, and the Blog and Links sections for the blog and social profiles. These are listed as separate sections on mat does dev, but the supplied page content does not include the actual contact address or profile URLs.
Where to look
- Contact: For direct messages or inquiries, this is the section intended for reaching Mat.
- Blog: For written posts and project updates.
- Links: For social profiles and other places Mat appears online.
- Projects: If your question is about a specific tool, such as Azalea, matscan or the packet debugger, its project entry may point to the most relevant contact or discussion channel.
A practical next step
Open the site and check Contact first for a direct route. If you want to follow Mat's work rather than send a message, use Blog for updates and Links for social accounts. For a project-specific question, mention the project name and include a reproducible example or clear description; that is generally more useful than a bare "hello" message.
What does the Azalea Rust crate collection let me do with Minecraft?
Azalea is a collection of Rust crates for building Minecraft bots, clients and tools. It is aimed at developers who want to write Minecraft-facing software in Rust rather than at players looking for a ready-made client: you would use it as a library to connect to servers, handle the protocol, and automate or observe gameplay from your own code.
Practical uses
- Writing bots that join a server and perform scripted actions.
- Building custom clients or tooling that need to speak Minecraft's protocol.
- Prototyping experiments such as pathfinding, packet inspection or automated testing against a server.
The trade-off is that it is a developer library, not an application: you supply the logic, and you should expect to work within Rust and keep up with Minecraft protocol changes. If your goal is simply to inspect packets or analyse worlds, related projects on the same site—such as the packet debugger or the NBT implementation—may be a lighter starting point.
As a first step, decide whether you need a full client connection or only a narrow task like reading packets; that choice tells you whether Azalea is the right layer or whether a smaller utility fits better.
How does matscan find Minecraft servers and warn their admins?
The site describes matscan as a "sophisticated internet-scale Minecraft server scanner with an automated warning system for admins," but that is the full extent of what it says. It does not explain the scanning method, the ports or protocols involved, how admins are identified, or what a warning contains. So the honest answer is: the site names the two capabilities and stops there.
What the description does tell you
- Scanning is internet-scale. The tool is framed as sweeping across the public internet rather than querying a single host, which is the usual approach for finding Minecraft servers: probe address ranges for the ports the game listens on and read the response a server sends back.
- Warnings are automated. Admins are notified without a human in the loop, which implies the scanner maps each discovered server to a contact channel and sends a message.
- It is an active, maintained project listed from 2022 onward, alongside the author's other Minecraft-focused work such as Azalea (Rust crates for bots and clients) and simdnbt (an NBT implementation).
A concrete scenario
Suppose you run a small survival server on a default port with online-mode off. A scanner of this kind would likely find it, record the address and version, and then attempt to reach whoever is listed as the owner. If that contact route is a public Discord or a server-list profile, the warning arrives there. If it is an email scraped from a website, it may never arrive.
What to check before relying on it
- How the scan is scoped. Whether it targets the full IPv4 space, specific ranges, or a list of known hosts determines how likely your server is to appear.
- How admins are matched. Server metadata, MOTD text, player lists, and public listings are all plausible sources; the reliability of the warning depends entirely on which one is used.
- What the warning asks for. A useful notice tells you the exposure and how to close it; a vague one just creates alarm.
If you operate a server, treat discovery as expected rather than exceptional and make sure the contact details attached to it are ones you actually read. For the specifics of matscan itself, the project's own page on mat does dev is the place to look.
User reviews (0)