Releases: mocsarcade/minecraft-worldstream
Release 1.0_64
Official release!
Changes since RC 1:
- Fixed block "de-culling" treating certain blocks as solids that aren't.
- Fixed the "user started/stopped streaming" message not appearing.
- Enabled culling by default in the config file.
- Changed chunk x and z to cx and cz.
0.9.62 Release Candidate 1
Ready for user acceptance testing.
This build contains the new WebSockets command API.
Deculling has been implemented and tested for basic functionality.
Beta 0.5.56
This build is our first Beta release, for acceptance testing of the full system.
Target release date is April 19.
This release contains:
- Full HTTP and WebSockets services
- All block metadata that is possible for us to obtain
- Two entities: Item frames and paintings
- Redesigned in-game commands
Alpha - 0.4.46
We're finally in Beta! In this build you'll find:
- Full HTTP functionality.
- Full WebSockets functionality.
- Support for numerical block IDs in JSON, with subtype/variant included.
- The ingame command /ws export has been temporarily removed, and will be reworked in the future.
Still to go:
- Entity support - Paintings, Item Frames, and Armor Stands.
- Culling of covered blocks.
- Block rotation, and additional data.
- Some minor touch-ups to the JSON logic.
Prototype Build 0.3.36
This BETA build is meant for user acceptance testing of the rudimentary WebSockets functionality. This build is UNTESTED beyond that it compiles and claims a successful WebSocket server startup on the specified port.
Currently, there is no specified API, but this will change. Any open connection to the endpoint should be sent a message containing JSON whenever any player in any world changes any block. This too will be refined after we confirm that the basic functionality works.
Refactored Prototype - 0.3.28
- HTTP server using API v1 successfully tested to download a chunk. Headers and footers still need to be added to world/chunk JSON.
- Block metadata library has been defined and will be implemented fully in the next release using JSON API v1.
- The plugin Configuration file now works correctly.
First Prototype
This is a very basic implementation of the file writing functionality and plugin interface. In the coming week, we'll be writing JSON files using an API and updating them as blocks are changed. This will be a significant refactoring that will also include metadata support for additional blocks.