How do I play Hoplite on Minecraft Bedrock Edition?

Connect to hoplite.gg using port 19132 (the default Bedrock port). Both Java and Bedrock players connect to the same server address. The resource pack will download automatically when you join.

What platforms support Hoplite Bedrock?

Hoplite Bedrock supports all Minecraft Bedrock Edition platforms including mobile (iOS and Android), consoles (Xbox, PlayStation, Nintendo Switch), and Windows 10/11 PC. All platforms connect to the same server and can play together with Java Edition players.

What is included in the Hoplite Bedrock resource pack?

The Bedrock port includes thousands of converted assets: custom 2D and 3D items, animated textures, multi-state items like bows and shields, ModelEngine models, custom armor, Unicode GUI elements, and vanilla texture replacements - all converted to work with Bedrock Edition's format.

Hoplite RP (Bedrock)

Q: Can I link my Java and Bedrock accounts on Hoplite?

Yes, you can link your accounts at link.geysermc.org/start so your progress, cosmetics, and items are shared across platforms. Without linking, your Bedrock account will have a dot prefix and be treated as a separate account. Note that after linking, you cannot play on both platforms simultaneously.

Worked on since: 2025

Hoplite is one of the most-played Minecraft servers globally, known for its intense battle-royale and duels, proximity voice chat, and high-quality custom visuals. The server was launched by YouTuber SpeedSilver, who has around 4 million subscribers. In 2025, I led the effort to bring the Hoplite experience to Minecraft Bedrock Edition players.

Scale

As of late 2025, the Hoplite resource pack comprises thousands of assets - and continues to grow. Converting this volume required handling a wide variety of content types:

2D items requiring Bedrock-specific attachable definitions
3D items with display property mirroring to match Java rendering, including per-state differences (e.g., bow, crossbow, shields)
Animated textures with multiple animation layers working correctly
Multi-state items like bows, crossbows, shields, and fishing rods with dynamic visual changes
ModelEngine models - converting complex entity models and their associated textures
Custom armor - porting armor visuals to Bedrock's attachable system
Unicode elements and GUI components - converting all assets and providing documentation, specifications, and implementation guidance to the JSON UI developer for buttons, progress bars, and other interactive elements
Vanilla texture replacements - ensuring all modified default textures carried over correctly to Bedrock's format and file structure

The Challenge

Porting a resource pack of this scale to Bedrock is not a simple file conversion. Bedrock Edition uses an entirely different resource pack format, different JSON schemas, different rendering behavior, and different client-side requirements. Achieving visual parity while maintaining performance across mobile, console, and PC clients required deep knowledge of both editions.

My Role: Bedrock Port Lead & Infrastructure Architect

I was responsible for the complete Bedrock port - not only the pack itself, but also the deployment pipeline and delivery infrastructure needed to serve it to players.

Resource Pack Conversion

Developed custom conversion scripts to transform Java assets into Bedrock-compatible formats
Ensured visual parity across hundreds of custom items, weapons, and UI elements
Adapted textures and models to work within Bedrock's rendering constraints

Infrastructure & Deployment

Designed CDN-based distribution to handle pack delivery at scale - serving thousands of players daily from around the world, with primary focus on USA and Europe
Identified and configured the specific HTTP headers required for Minecraft Bedrock clients to accept externally hosted packs
Built automated deployment pipelines mirroring our Java pack workflow, enabling rapid iteration and updates with no manual downloads required
Advised on server-side setup and integration

Plugin & Extension Development

Forked and modified multiple Java plugins and Geyser Extensions to support our Bedrock implementation
Contributed improvements back to upstream open-source repositories where possible, reducing long-term maintenance burden

Team Coordination

Sourced and onboarded a specialist for complex Bedrock JSON UI work after evaluating dozens of candidates
Managed cross-team communication within my scope - resource pack, deployment pipeline, and plugin modifications - to ensure visual parity with the Java version

Long-Term Planning Pays Off

When I started working on the Java resource pack in 2023, I made deliberate design choices with a potential Bedrock port in mind. File structures, naming conventions, and asset organization were all built to allow for easier cross-platform conversion. When the time came to execute the Bedrock port, that foresight made a multi-month development venture achievable within a tight timeline.

Ongoing Maintenance

I continue to maintain the Bedrock pack - keeping it compatible with new Minecraft versions and in sync with the Java pack as new content is added.

Account Linking

If you play on both Java and Bedrock, you can link your accounts so your progress, cosmetics, and items are shared across platforms.

Link your accounts: link.geysermc.org/start
Unlink if needed: geysermc.org/wiki/floodgate/linking

Without linking, your Bedrock account will have a . prefix and be treated as a separate account. Note that after linking, you cannot play on both platforms simultaneously, but you can always unlink later if needed.