- Rust 92.8%
- RenderScript 3.6%
- TypeScript 1.7%
- Java 1.1%
- Nix 0.6%
- Other 0.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
57a77b1c99
`minecraft:block` is mapped as a mandatory registry from 26.2 onwards so
that block tags can be sent. It has no entry directory in the generated
data, and `Registry::load` falls back to an empty entry map instead of
failing, so the registry still ends up in the RegistryManager.
As a result an empty Registry Data packet is emitted for
`minecraft:block` during configuration. It carries no information, and
clients that do not expect that registry to be synced can fail hard on
it: Geyser (and therefore every Bedrock player behind it) dies with
IllegalStateException: Expected reader for registry
Java registry: minecraft:block
Vanilla clients silently ignore the packet, which is why this went
unnoticed.
Skip registries without entries when building the Registry Data
packets. Tags are unaffected: `get_tagged_registries()` keeps its own
list and still emits block tags.
|
||
| .github | ||
| crates | ||
| data | ||
| docker | ||
| docs | ||
| java_wrapper | ||
| nix | ||
| pico_libraries | ||
| pico_limbo | ||
| pterodactyl/eggs | ||
| .dockerignore | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| docker-compose.yml | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| rust-toolchain.toml | ||
PicoLimbo
An ultra-lightweight, multi-version Minecraft limbo server written in Rust
Supporting all Minecraft versions from 1.7.2 through 26.2
⭐ Star this repo • 💬 Join Discord • 📖 Read Docs
Schematic from LOOHP/Limbo
Community & Support
If you have any questions, suggestions or simply want to stay updated, please join the Discord server!
Introduction
PicoLimbo is a lightweight limbo server written in Rust, designed primarily as an AFK or waiting server. Its core focus is on efficiency by implementing only essential packets required for client login and maintaining connection (keep-alive) without unnecessary overhead.
While not aiming to replicate every Minecraft server feature, PicoLimbo supports all Minecraft versions from 1.7.2 through 26.2, excluding snapshots.
Features
🎮 Wide Version Compatibility
Supports all Minecraft versions from 1.7.2 to 26.2 natively, no need for ViaVersion or additional compatibility layers.
⚡ Ultra-Lightweight & Highly Scalable
Uses 0% CPU while idle and handles hundreds of players under 10 MB RAM. View benchmarks.
👤 Skin Support
Player skins are supported. What else to say about that?
🔀 Built-in Proxy Support
Integrates with all major Minecraft proxies:
- Velocity (Modern Forwarding)
- BungeeCord (Legacy Forwarding)
- BungeeGuard & BungeeGuardPlus authentication
⚙️ Highly Configurable
Customize your server using a simple TOML configuration file, including welcome message, spawn dimension, server list MOTD, and more. View configuration docs.
🌍 Schematic World (Experimental)
Load a custom world from a schematic file and customize spawn location (1.16+ only).
The screenshot shows just a few of the supported Minecraft versions.
Quick Start
Pterodactyl
Official eggs for Pterodactyl are provided in the pterodactyl directory. More information about PicoLimbo's Pterodactyl eggs.
Docker
docker run --rm -p "25565:25565" ghcr.io/quozul/picolimbo:latest
Java Wrapper
For user wishing to run PicoLimbo inside your Velocity, BungeeCord proxy as a plugin or as a standalone jar file, you can download the Java Wrapper from Modrinth.
Binary / Standalone
Download from GitHub Releases
For more detailed installation and configuration instructions, please refer to the documentation website.
Documentation
Complete documentation is available at https://picolimbo.quozul.dev/
For detailed installation instructions, configuration options, and usage examples, please visit the documentation website.
Similar Projects
- Limbo: Supports only one Minecraft version at a time
- NanoLimbo: Actively maintained (see BoomEaro's fork)
Contributing
Contributions are welcome! If you encounter any issues or have suggestions for improvement, please submit an issue or pull request on GitHub. Make sure to follow the existing code style and include relevant tests.
- Fork the repository.
- Create a new branch
git checkout -b <branch-name>. - Make changes and commit
git commit -m 'Add some feature'. - Push to your fork
git push origin <branch-name>. - Submit a pull request.