Common questions

Eaglercraft is an independent browser adaptation of Minecraft, not a Mojang or Microsoft product. The project FAQ describes open-source code, TeaVM compilation and EaglerXServer connections to Java servers. Start with the how-to-play guide for entry points and controls.

The project play page offers browser access without a purchase. That does not grant ownership of Minecraft or permission to redistribute its assets. The project legal page states its position; our safety and legal guide explains the distinction without calling it a free licensed copy of Minecraft.

No blanket safety guarantee is justified. Use the project's own entry point to establish provenance rather than trusting a similarly named launcher or mirror. This review did not audit client code or run malware tests; a source link is not a security certification. See the risk checklist before using third-party packages.

The project legal statement and Minecraft EULA describe different parties' positions and terms; neither is a court ruling on every build or use. Open-source code alone does not settle asset rights or redistribution. Read the legal context; this site does not provide legal advice.

A browser game or HTML filename does not prove that a file is harmless. The project download catalog lists ZIP packages, not an APK. The download guide records actual byte and hash checks, not malware clearance: the HTML was not executed or scanned, and a matching hash is only an identity check.

This site cannot classify every fork, asset bundle or use as lawful or infringing. The project's legal statement gives its own asset and DMCA position; compare it with the Minecraft EULA. Our safety and legal page separates those statements from a legal verdict rather than treating the project's claims as independent clearance.

No: the project play page is the browser entry point. For a local copy, the download catalog offers ZIPs containing an HTML client. Follow the offline download steps to extract and open it. Local launch does not make multiplayer services available without a network connection.

The checked project catalog lists four offline version families: 1.5.2, 1.8.8, 1.12.2 and 26.2, with six ZIP links. Separately, the Play page lists 26.3 as a browser choice, but the catalog has no 26.3 ZIP. The version index distinguishes browser options, offline files and server labels.

First match the browser version required by your server operator. The project catalog presents 1.8.8 as the established line, 1.12.2 as still in development, 26.2 as zeus and 1.5.2 as legacy. Use the version comparison rather than assuming the largest label is best. This is catalog guidance, not a tested performance ranking.

Yes: the catalog has both JavaScript and WASM-GC packages for 1.8.8. The project FAQ describes WASM-GC/JSPI requirements and estimates roughly 50 percent better performance, with VSync advice. That estimate is not this site's benchmark or a device guarantee. See WASM versus JavaScript for the compatibility trade-off.

Mobile compatibility for 1.12.2 and Tuff remains unverified here. The catalog lists 1.12.2 browser packages, while the project play FAQ documents touch controls generally; those facts are not a 1.12.2 phone test or supported-device matrix. Read the mobile limitations and 1.12.2 status before assuming a particular phone works.

No 1.21 or 1.21.11 client appears in the checked project download catalog. Community experiments remain unverified here; this does not prove that none exists. A repository name, server backend version or video title is not evidence of a supported playable client. The 1.21 status page explains the evidence boundary without offering an unverified download.

Yes: the project catalog lists a 26.2 zeus download with skins. The retrieved ZIP was 58,418,343 bytes and contained one HTML entry of 77,579,383 bytes; the 26.2 page gives the hash and verification context. The client was not executed: its modern-item inventory and equivalence to any Mojang release remain unverified.

The project Play page lists 26.3 and displays a launch control. The separate download catalog has no 26.3 offline ZIP. The HeartSMP wiki still recommends a 26.2 browser client for its 26.3 backend. See the 26.3 status page; the review did not launch a game or test a server connection.

The project's shared-world instructions say the host uses Invite, then a friend opens Multiplayer, Direct Connect and Join Shared World with the code. Relay settings must match. Alternatively, use a server that accepts your client. The world-sharing guide separates live invitations from save-file transfers; these are documented steps, not a session tested by this site.

Open Multiplayer, choose Add Server and enter the operator's full WSS address, including any specified port or path. Confirm its accepted browser versions and whitelist requirements. For an operator-published example, see the HeartSMP instructions. Follow the joining checklist; an address being published does not establish current uptime or a successful connection.

Follow the EaglerXServer README for Java 17+, the appropriate Spigot/BungeeCord/Velocity component and any required version translation. Generate configuration, check inject_address, then configure a reachable WSS listener with valid TLS and inspect proxy/backend logs. The server setup guide links the configuration details. This review did not deploy a server or verify a connection.

The project FAQ describes Chromebook support, and the u53 notes document Intel Chromebook and WebGL stability work. Neither establishes performance on every model or permission to bypass managed-device restrictions. See the Chromebook guide for browser and policy checks; this site did not benchmark a Chromebook.

The project FAQ documents automatic touch controls and iOS OGG audio handling, but this review did not test an iPhone or certify a particular iOS/browser combination. The download catalog does not list an IPA app. Use the mobile guide for browser limitations rather than treating general documentation as device-specific compatibility proof.

The checked project download catalog has no APK or IPA; it offers browser HTML packages. This is a statement about that catalog, not proof that no third-party wrapper exists. Similarly named Eaglecraft products are not automatically this project. The APK status guide explains the distinction without recommending an unverified installer.

Controller support is unverified here, including Xbox and DualSense bindings. The MDN Gamepad API documentation establishes that browsers can expose gamepad input; it does not establish that Eaglercraft reads it or supplies working mappings. See the controller status page. No controller was paired or tested, so this is not a verified setup tutorial.

For the community EaglerForge 1.8 line, its installation guide documents Mods, Add New by URL, or Upload. This does not make arbitrary Java Forge JARs compatible or establish support on 1.12.2/26.2. Read the EaglerForge guide and review the JavaScript source before loading it; this review did not execute mods.

The project resource-pack catalog is explicitly for the 1.8 line: use Add to game, then enable the pack under Options, Resource Packs. A compatible ZIP can also be imported through the client. The resource-pack guide covers version checks; this catalog is not proof that those packs work on 1.12.2 or 26.2.

Prepare a standard 64x64 or legacy 64x32 PNG using the Minecraft skin layouts, then check your client's actual skin controls; see the skin guide. The public account login does not establish an upload or deletion workflow. Account deletion has no verified public instructions in this review, and no signed-in flow was tested; see the account-status guide.

The project FAQ documents built-in PBR shaders for the 1.8 line under Options, Shaders, requiring WebGL 2 and floating-point render targets. That is not support for arbitrary Java shader ZIPs, nor certification for 1.12.2 or 26.2. The shader guide explains these boundaries; visual quality and FPS were not tested here.

Not in the vanilla 1.8.8 or 1.12.2 feature set: the mace was introduced in Minecraft Java 1.21. The presence or behavior of a mace in 26.2 remains unverified; its label is not a Mojang-version mapping. Servers and forks may add custom items. See the mace guide before applying a modern recipe.

Not in vanilla 1.8.8 or 1.12.2: Netherite belongs to the later 1.16 era. Its availability in the 26.2 client remains unverified, and a server's custom item may not follow vanilla behavior. The Netherite guide separates those cases and explains why modern upgrade instructions cannot simply be applied to old clients.

First distinguish low local FPS from network or server delay. Reduce render distance and disable PBR before comparing changes; the project FAQ also discusses WASM and VSync. Its performance estimate is not a promise of 60 FPS on your device. Follow the lag and FPS checklist and record one change at a time; no benchmark was run here.

Check the WSS address, TLS certificate, listener, proxy/backend logs and inject_address against the EaglerXServer configuration; its documented login timeout is 10,000 ms, not a universal fix. Issue 183 reports a 26.2 Paper backend, not a known browser-client version, and was still open at review. Use the handshake checklist rather than treating the report as an official solution.

No. The Eaglercraft project describes an independent browser adaptation, while Minecraft Java and Bedrock are Mojang/Microsoft products. A bridge to a Java server does not imply identical features, ownership or support. The Eaglercraft versus Minecraft comparison explains the product and version distinctions without claiming feature parity.