Eaglercraft Workspace ^hot^ -

| Issue | Likely Cause | Solution | |-------|--------------|----------| | Black screen after loading | WebGL not supported or GPU blocked | Update browser, enable hardware acceleration, or try Chrome. | | WebSocket connection refused | Server not running or firewall blocking port | Run java -jar EaglercraftServer.jar , check netstat , open port. | | Textures missing / purple/black checkers | Asset build failed or cache corruption | Clear browser IndexedDB, rebuild assets with ./gradlew extractAssets . | | High memory usage | Large world or many players | Reduce render distance in client settings; allocate more RAM to server ( -Xmx2G ). | | "TeaVM failed" compilation error | JDK version mismatch or missing dependencies | Ensure JDK 17 is used; delete .gradle/ and rerun. | An Eaglercraft workspace is far more than a simple game file. It is a complete development and hosting environment that mirrors the complexity of a full-fledged game studio pipeline—yet it is accessible to dedicated hobbyists and small communities. Whether you are a student learning how transpilers work, a server administrator wanting to provide free Minecraft gameplay, or a modder experimenting with Java-to-JavaScript conversion, the workspace gives you full control.

cd server java -jar EaglercraftServer.jar The first run generates configuration files. Edit config.yml or server.properties to set the port (default 8081 for WebSockets), max players, and online mode (true/false). For LAN play, you may need to configure port forwarding or use a tool like ngrok . You cannot simply open the index.html file locally if you want multiplayer (due to WebSocket security restrictions). You must serve it over HTTP. In your workspace, you can use: eaglercraft workspace

git pull origin main ./gradlew clean build Be careful: your custom changes may conflict. Use a version control system (Git) to merge upstream changes. Even a well-organized workspace can encounter problems. | Issue | Likely Cause | Solution |